forked from fog/fog-digitalocean
-
Notifications
You must be signed in to change notification settings - Fork 1
/
history (6).atom digitalOceon
211 lines (211 loc) · 50 KB
/
history (6).atom digitalOceon
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
<id>tag:status.digitalocean.com,2005:/history</id>
<link rel="alternate" type="text/html" href="https://status.digitalocean.com"/>
<link rel="self" type="application/atom+xml" href="https://status.digitalocean.com/history.atom"/>
<title>DigitalOcean Status - Incident History</title>
<updated>2020-01-23T12:23:40Z</updated>
<author>
<name>DigitalOcean</name>
</author>
<entry>
<id>tag:status.digitalocean.com,2005:Incident/3461649</id>
<published>2020-01-23T11:28:22Z</published>
<updated>2020-01-23T11:28:22Z</updated>
<link rel="alternate" type="text/html" href="https://status.digitalocean.com/incidents/lvyhmpwhvdt4"/>
<title>Droplet Connectivity issues in NYC1 region</title>
<content type="html"><p><small>Jan <var data-var='date'>23</var>, <var data-var='time'>11:28</var> UTC</small><br><strong>Investigating</strong> - Our Engineering team is investigating an issue with accessing Droplets in our NYC1 region. During this time you may also experience issues with performing operations on your Droplets. We apologize for the inconvenience and will share an update once we have more information.</p></content>
</entry>
<entry>
<id>tag:status.digitalocean.com,2005:Incident/3459299</id>
<published>2020-01-23T02:00:38Z</published>
<updated>2020-01-23T02:00:40Z</updated>
<link rel="alternate" type="text/html" href="https://status.digitalocean.com/incidents/2wlj58j7f1m9"/>
<title>LON1 Region Network Maintenance</title>
<content type="html"><p><small>Jan <var data-var='date'>23</var>, <var data-var='time'>02:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Jan <var data-var='date'>22</var>, <var data-var='time'>22:01</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jan <var data-var='date'>22</var>, <var data-var='time'>21:05</var> UTC</small><br><strong>Scheduled</strong> - The Networking team will be making changes to our core networking equipment to improve performance and reliability for our LON1 location.<br /><br />Expected Impact:<br /><br />There will be several minutes of packet loss while we shift traffic between redundant devices. There may be additional event processing delays, as well as Cloud Panel and API interruptions during this period. We will endeavor to keep this to a minimum for the duration of the change.<br /><br />If you have any questions or concerns, please create a support ticket.</p></content>
</entry>
<entry>
<id>tag:status.digitalocean.com,2005:Incident/3457253</id>
<published>2020-01-22T19:07:49Z</published>
<updated>2020-01-22T19:07:50Z</updated>
<link rel="alternate" type="text/html" href="https://status.digitalocean.com/incidents/d4tsv8cq6sjq"/>
<title>Event Processing issues with Managed Kubernetes clusters</title>
<content type="html"><p><small>Jan <var data-var='date'>22</var>, <var data-var='time'>19:07</var> UTC</small><br><strong>Resolved</strong> - Our engineering team has resolved the issue with event processing with regards to Managed Kubernetes clusters across all regions. All systems should now be operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.</p><p><small>Jan <var data-var='date'>22</var>, <var data-var='time'>15:19</var> UTC</small><br><strong>Monitoring</strong> - Our engineering team has implemented a fix to resolve the issue with event processing with regards to Managed Kubernetes clusters across all regions and is monitoring the situation. We will post an update as soon as the issue is fully resolved.</p><p><small>Jan <var data-var='date'>22</var>, <var data-var='time'>12:20</var> UTC</small><br><strong>Identified</strong> - Our Engineering team has identified the cause of the issue with impacting interactions and event processing with regards to Managed Kubernetes clusters across all regions. We will post an update as soon as additional information is available.</p><p><small>Jan <var data-var='date'>22</var>, <var data-var='time'>11:26</var> UTC</small><br><strong>Investigating</strong> - Our Engineering team is currently investigating an issue impacting interactions and event processing with regards to Managed Kubernetes clusters across all regions. During this time, users may experience issues with creating clusters or making changes to existing clusters in all regions. We apologize for the inconvenience and will share an update once we have more information.</p></content>
</entry>
<entry>
<id>tag:status.digitalocean.com,2005:Incident/3455608</id>
<published>2020-01-22T00:49:09Z</published>
<updated>2020-01-22T00:49:09Z</updated>
<link rel="alternate" type="text/html" href="https://status.digitalocean.com/incidents/fftythk8wws3"/>
<title>AMS3 Spaces Temporarily Inaccessible</title>
<content type="html"><p><small>Jan <var data-var='date'>22</var>, <var data-var='time'>00:49</var> UTC</small><br><strong>Resolved</strong> - Our engineering team has resolved the issue with AMS3 Spaces accessibility. Spaces in this region should now be operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.</p><p><small>Jan <var data-var='date'>22</var>, <var data-var='time'>00:06</var> UTC</small><br><strong>Monitoring</strong> - Our engineering team has implemented a fix to resolve an issue with AMS3 Spaces being inaccessible, and are monitoring the situation. We will post an update as soon as the issue is fully resolved.</p></content>
</entry>
<entry>
<id>tag:status.digitalocean.com,2005:Incident/3455002</id>
<published>2020-01-21T23:00:38Z</published>
<updated>2020-01-21T23:12:05Z</updated>
<link rel="alternate" type="text/html" href="https://status.digitalocean.com/incidents/x0xytvsvky35"/>
<title>AMS3 Region Network Maintenance</title>
<content type="html"><p><small>Jan <var data-var='date'>21</var>, <var data-var='time'>23:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Jan <var data-var='date'>21</var>, <var data-var='time'>21:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jan <var data-var='date'>21</var>, <var data-var='time'>20:59</var> UTC</small><br><strong>Scheduled</strong> - The Networking team will be making changes to our core networking equipment to improve performance and reliability for our AMS3 location.<br /><br />Expected Impact:<br /><br />There will be several minutes of packet loss while we shift traffic between redundant devices. There may be additional event processing delays, as well as Cloud Panel and API interruptions during this period. We will endeavor to keep this to a minimum for the duration of the change.<br /><br />If you have any questions or concerns, please create a support ticket.</p></content>
</entry>
<entry>
<id>tag:status.digitalocean.com,2005:Incident/3443124</id>
<published>2020-01-18T10:13:50Z</published>
<updated>2020-01-18T10:15:56Z</updated>
<link rel="alternate" type="text/html" href="https://status.digitalocean.com/incidents/3vhcly1y2kgz"/>
<title>Issue with restoring Backups on Managed Databases in our SFO2 region</title>
<content type="html"><p><small>Jan <var data-var='date'>18</var>, <var data-var='time'>10:13</var> UTC</small><br><strong>Resolved</strong> - The issue with restoring Backups on Managed Databases in our SFO2 region is resolved. Backups on Managed Databases should now be operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.</p><p><small>Jan <var data-var='date'>18</var>, <var data-var='time'>07:59</var> UTC</small><br><strong>Monitoring</strong> - Our engineering team is monitoring the issue with Backups on Managed Databases. We will post an update as soon as the issue is fully resolved.</p><p><small>Jan <var data-var='date'>18</var>, <var data-var='time'>07:29</var> UTC</small><br><strong>Investigating</strong> - Our engineering team is investigating an issue with Backups on Managed Databases in our SFO2 Region. During this time, you may experience issues in restoring databases. We apologize for the inconvenience and will share an update once we have more information.</p></content>
</entry>
<entry>
<id>tag:status.digitalocean.com,2005:Incident/3438562</id>
<published>2020-01-17T06:03:47Z</published>
<updated>2020-01-17T06:03:48Z</updated>
<link rel="alternate" type="text/html" href="https://status.digitalocean.com/incidents/ch277cwcm5sm"/>
<title>Degraded Network Connectivity in AMS3</title>
<content type="html"><p><small>Jan <var data-var='date'>17</var>, <var data-var='time'>06:03</var> UTC</small><br><strong>Resolved</strong> - All systems should now be operating normally in our AMS3 region. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.</p><p><small>Jan <var data-var='date'>17</var>, <var data-var='time'>05:07</var> UTC</small><br><strong>Monitoring</strong> - Our Network team has identified and applied a fix for a subset of users who were experiencing network connectivity issues to their Droplets or managed services in our AMS3 region. We are monitoring closely and will update as soon as the issue is fully resolved.</p></content>
</entry>
<entry>
<id>tag:status.digitalocean.com,2005:Incident/3401387</id>
<published>2020-01-14T22:20:16Z</published>
<updated>2020-01-14T22:20:16Z</updated>
<link rel="alternate" type="text/html" href="https://status.digitalocean.com/incidents/qz40dp1qcs1d"/>
<title>Block Storage Maintenance</title>
<content type="html"><p><small>Jan <var data-var='date'>14</var>, <var data-var='time'>22:20</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has now been completed. Users who wish to perform an online resize of their Block Storage Volumes and are currently unable to, will first need to power off and then on Droplets with Block Storage attachments, via the control panel or API.<br /><br />After this action has been completed, users may resize their Block Storage Volumes normally, and will not need to power off and then on Droplets in order to complete resizes. <br /><br />We appreciate your patience during this maintenance. If you have any questions or questions, please open a ticket with our support team.</p><p><small>Jan <var data-var='date'> 8</var>, <var data-var='time'>00:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jan <var data-var='date'> 7</var>, <var data-var='time'>23:59</var> UTC</small><br><strong>Scheduled</strong> - During the next 5 business days, our team will be deploying a fix for some users who are unable to perform an online resize of their Block Storage Volumes. During this time, users can still resize their Volumes by taking the following steps:<br /><br />1) Unmount your filesystem within the Droplet<br />2) Detach the Volume from your Droplet<br />3) Resize the Volume<br />4) Attach the Volume to the Droplet<br />5) Perform any required post-attachment work (such as resize2fs)<br /><br />Upon completion of this deployment, users wishing to perform online resizing of their Block Storage Volumes will be prompted to first power cycle (power off and power on through the control panel or API) their Droplets.<br /><br />If you have any questions or concerns, please open a ticket with our support team.</p></content>
</entry>
<entry>
<id>tag:status.digitalocean.com,2005:Incident/3408516</id>
<published>2020-01-11T11:57:19Z</published>
<updated>2020-01-11T11:57:20Z</updated>
<link rel="alternate" type="text/html" href="https://status.digitalocean.com/incidents/2yyk6j58xcxh"/>
<title>Disruption of DigitalOcean Email Notifications</title>
<content type="html"><p><small>Jan <var data-var='date'>11</var>, <var data-var='time'>11:57</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Jan <var data-var='date'>11</var>, <var data-var='time'>10:56</var> UTC</small><br><strong>Verifying</strong> - Verification is currently underway for the maintenance items.</p><p><small>Jan <var data-var='date'>11</var>, <var data-var='time'>06:01</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jan <var data-var='date'> 9</var>, <var data-var='time'>14:27</var> UTC</small><br><strong>Scheduled</strong> - A planned maintenance will be occurring with one of DigitalOcean’s Email Service Providers on Saturday, January 11th from 1 - 7 am EST (0600 - 1200 UTC). <br /><br />This will delay the sending of certain DigitalOcean emails to our customers until after the maintenance window closes. More details on the specific emails impacted can be found below along with proposed mitigations. <br /><br />The maintenance should not disrupt any inbound emails to DigitalOcean teams such as our Support Team or your ability to send or receive email via your Droplets.<br /><br />The following outbound emails will be impacted:<br /><br />DigitalOcean Monitoring Emails:<br />Customers needing access during this time are advised to enable a second notification method. Monitor emails will deliver after a delay.<br /><br />Droplet Creations Without SSH Keys:<br />Customers needing access during this time are advised to use SSH keys to allow login during the maintenance.<br /><br />New Login on an Untrusted Device (e.g. a fresh browser):<br />Customers needing access during this time are advised to enable two-factor authentication or enable Google/GitHub authentication to allow login during the maintenance.<br /><br />DigitalOcean Team and User Email Updates:<br />Advise customers defer Team and User Email updates until after outage. These update emails will deliver after a delay. <br /><br />Droplet Password Reset Emails:<br />Advise customers defer on Droplet password resets until after outage. Droplet password reset emails will deliver after a delay.<br /><br />User Password Reset Emails:<br />Advise customers defer on user password resets until after outage. User password reset emails will deliver after a delay.<br /><br />New User Signups:<br />‘Confirm Your Account’ emails will deliver after a delay.<br /><br />We recognize the disruptive nature of this maintenance and are making every effort to help reduce the impact for our customers.If you need assistance planning for this maintenance, or have any other questions, please reach out by opening up a support ticket.</p></content>
</entry>
<entry>
<id>tag:status.digitalocean.com,2005:Incident/3401940</id>
<published>2020-01-08T06:00:35Z</published>
<updated>2020-01-08T06:00:36Z</updated>
<link rel="alternate" type="text/html" href="https://status.digitalocean.com/incidents/yp7b8jv4wbjg"/>
<title>Latency Observed with SGP1 Spaces</title>
<content type="html"><p><small>Jan <var data-var='date'> 8</var>, <var data-var='time'>06:00</var> UTC</small><br><strong>Resolved</strong> - Our Engineering team has resolved the issue with increased error rates and latency with Spaces in the SGP1 region. Spaces should now be operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.</p><p><small>Jan <var data-var='date'> 8</var>, <var data-var='time'>05:30</var> UTC</small><br><strong>Monitoring</strong> - Our Engineering team has implemented a fix to resolve the issue with increased error rates and latency with Spaces in the SGP1 region and is monitoring the situation. We will post an update as soon as the issue is fully resolved.</p><p><small>Jan <var data-var='date'> 8</var>, <var data-var='time'>04:48</var> UTC</small><br><strong>Identified</strong> - Our engineering team has identified the cause of the latency with Spaces in the SGP1 region, and is actively working on a fix. We will post an update as soon as additional information is available.</p><p><small>Jan <var data-var='date'> 8</var>, <var data-var='time'>04:06</var> UTC</small><br><strong>Investigating</strong> - Our engineering team is investigating an issue with increased error rates and latency with Spaces in the SGP1 region. We apologize for the inconvenience and will share an update once we have more information.</p></content>
</entry>
<entry>
<id>tag:status.digitalocean.com,2005:Incident/3400279</id>
<published>2020-01-08T00:00:25Z</published>
<updated>2020-01-08T00:00:27Z</updated>
<link rel="alternate" type="text/html" href="https://status.digitalocean.com/incidents/3hb5bwdtxbcc"/>
<title>Block Storage Volume Resizing Temporarily Disabled</title>
<content type="html"><p><small>Jan <var data-var='date'> 8</var>, <var data-var='time'>00:00</var> UTC</small><br><strong>Resolved</strong> - Our engineering team has implemented a fix which will allow live Block Storage Volume Resizes for most Droplets. Deployment of the fix will take place over the next 5 business days. During this time, some users may experience errors when resizing Block Storage Volumes. Upon completion of this deployment, users still impacted will receive a new error requesting they power cycle (power off and power on) their Droplet(s). We’re marking the issue as resolved and moving to a maintenance update status with additional details.</p><p><small>Jan <var data-var='date'> 7</var>, <var data-var='time'>18:21</var> UTC</small><br><strong>Identified</strong> - We have identified a bug with the potential to impact our Block Storage service. While we investigate the issue and work to remediate, we are putting a temporary pause on Block Storage resizes globally to prevent our users from being impacted. We expect to be able to share an update here by 8pm ET, or sooner if we have more information.</p></content>
</entry>
<entry>
<id>tag:status.digitalocean.com,2005:Incident/3400826</id>
<published>2020-01-07T23:08:47Z</published>
<updated>2020-01-07T23:08:48Z</updated>
<link rel="alternate" type="text/html" href="https://status.digitalocean.com/incidents/sjgrc3h2ktx7"/>
<title>FRA1 Region Network Maintenance</title>
<content type="html"><p><small>Jan <var data-var='date'> 7</var>, <var data-var='time'>23:08</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed. If you have any questions or concerns, please create a support ticket.</p><p><small>Jan <var data-var='date'> 7</var>, <var data-var='time'>21:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jan <var data-var='date'> 7</var>, <var data-var='time'>20:49</var> UTC</small><br><strong>Scheduled</strong> - The Networking team will be making changes to our core networking equipment to improve performance and reliability for our FRA1 location.<br /><br />Expected Impact:<br /><br />There may be a few minutes of increased latency as well as small amounts of packet loss while we shift traffic to redundant devices. We will endeavor to keep this to a minimum for the duration of the change.<br /><br />If you have any questions or concerns, please create a support ticket.</p></content>
</entry>
<entry>
<id>tag:status.digitalocean.com,2005:Incident/3390604</id>
<published>2020-01-05T03:38:39Z</published>
<updated>2020-01-05T03:38:40Z</updated>
<link rel="alternate" type="text/html" href="https://status.digitalocean.com/incidents/tp6yg4h8bfp5"/>
<title>Issues with NYC3 Spaces.</title>
<content type="html"><p><small>Jan <var data-var='date'> 5</var>, <var data-var='time'>03:38</var> UTC</small><br><strong>Resolved</strong> - Our engineering team has resolved the issue with Spaces in our NYC3 region. All systems should now be operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.</p><p><small>Jan <var data-var='date'> 5</var>, <var data-var='time'>02:53</var> UTC</small><br><strong>Monitoring</strong> - Our engineering team has implemented a fix to resolve the issues with Spaces in our NYC3 region and is monitoring the situation. We will post an update as soon as the issue is fully resolved.</p><p><small>Jan <var data-var='date'> 5</var>, <var data-var='time'>01:29</var> UTC</small><br><strong>Identified</strong> - Our engineering team has identified the cause of the issue with increased error rates and latency with Spaces in the NYC3 region and is actively working on a fix. We will post an update as soon as additional information is available.</p><p><small>Jan <var data-var='date'> 5</var>, <var data-var='time'>00:36</var> UTC</small><br><strong>Investigating</strong> - Our engineering team is investigating an issue with increased error rates and latency with Spaces in the NYC3 region. We apologize for the inconvenience and will share an update once we have more information.</p></content>
</entry>
<entry>
<id>tag:status.digitalocean.com,2005:Incident/3380805</id>
<published>2020-01-02T12:35:12Z</published>
<updated>2020-01-02T12:35:13Z</updated>
<link rel="alternate" type="text/html" href="https://status.digitalocean.com/incidents/z8q9mhry7lb4"/>
<title>Spaces Issue in NYC3</title>
<content type="html"><p><small>Jan <var data-var='date'> 2</var>, <var data-var='time'>12:35</var> UTC</small><br><strong>Resolved</strong> - Our Engineering team has resolved the issue with Spaces in our NYC3 region. Accessing Spaces should now be operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.</p><p><small>Jan <var data-var='date'> 2</var>, <var data-var='time'>12:11</var> UTC</small><br><strong>Monitoring</strong> - Our Engineering team has implemented a fix to resolve the issue with Spaces in our NYC3 region and is monitoring the situation. We will post an update as soon as the issue is fully resolved.</p><p><small>Jan <var data-var='date'> 2</var>, <var data-var='time'>09:41</var> UTC</small><br><strong>Update</strong> - Our Engineering team continues to investigate the issue with Spaces in our NYC3 region that is currently impacting accessing Spaces or inaccessibility with our Spaces. We appreciate your patience and will post an update as soon as additional information is available.</p><p><small>Jan <var data-var='date'> 2</var>, <var data-var='time'>06:37</var> UTC</small><br><strong>Investigating</strong> - Our Engineering team is investigating an issue with Spaces in our NYC3 region. During this time you may experience errors accessing Spaces or inaccessibility with our Spaces. We apologize for the inconvenience and will share an update once we have more information.</p></content>
</entry>
<entry>
<id>tag:status.digitalocean.com,2005:Incident/3362887</id>
<published>2019-12-27T01:20:54Z</published>
<updated>2019-12-27T01:20:55Z</updated>
<link rel="alternate" type="text/html" href="https://status.digitalocean.com/incidents/t9w8x953n4sd"/>
<title>Network Connectivity Issues in AMS2 Region</title>
<content type="html"><p><small>Dec <var data-var='date'>27</var>, <var data-var='time'>01:20</var> UTC</small><br><strong>Resolved</strong> - Our Engineering team has resolved the issue with public networking in the AMS2 region. Public network connectivity should be operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.</p><p><small>Dec <var data-var='date'>27</var>, <var data-var='time'>00:33</var> UTC</small><br><strong>Monitoring</strong> - Our Engineering team has implemented a fix to resolve the issue with public networking in the AMS2 region and is monitoring the situation. We will post an update as soon as the issue is fully resolved.</p><p><small>Dec <var data-var='date'>26</var>, <var data-var='time'>23:02</var> UTC</small><br><strong>Identified</strong> - Our Engineering team has identified the cause of the issue impacting public networking in the AMS2 region, and is actively working on a fix. We will post an update as soon as additional information is available.</p><p><small>Dec <var data-var='date'>26</var>, <var data-var='time'>21:32</var> UTC</small><br><strong>Investigating</strong> - Our Engineering team is investigating an issue with public networking in the AMS2 region. During this time, some users may experience public network connectivity issues. We apologize for the inconvenience and will share an update once we have more information.</p></content>
</entry>
<entry>
<id>tag:status.digitalocean.com,2005:Incident/3348512</id>
<published>2019-12-21T20:39:31Z</published>
<updated>2019-12-21T20:39:31Z</updated>
<link rel="alternate" type="text/html" href="https://status.digitalocean.com/incidents/byv1hqyr2pb0"/>
<title>Issues with event processing across all regions</title>
<content type="html"><p><small>Dec <var data-var='date'>21</var>, <var data-var='time'>20:39</var> UTC</small><br><strong>Resolved</strong> - Our Engineering team has confirmed resolution of the issue affecting Droplet creates and event processing across all regions. All systems should be operating normally. If you continue to experience any problems, please open a ticket with our support team. We apologize for any inconvenience, and we appreciate your patience throughout this process.</p><p><small>Dec <var data-var='date'>21</var>, <var data-var='time'>19:52</var> UTC</small><br><strong>Monitoring</strong> - Our Engineering team has identified the cause of issues affecting Droplet creates and event processing, and functionality should be fully restored at this time. Our team is now monitoring the situation for any further issues. We apologize for the inconvenience and will share an update once we have confirmed that the issue is resolved.</p><p><small>Dec <var data-var='date'>21</var>, <var data-var='time'>19:04</var> UTC</small><br><strong>Identified</strong> - Our Engineering team has identified an issue affecting Droplet creates and event processing across all regions. During this time, users may experience intermittent errors or delays while working with resources, such as creating or destroying Droplets. We apologize for the inconvenience and will share an update once we have more information.</p></content>
</entry>
<entry>
<id>tag:status.digitalocean.com,2005:Incident/3347596</id>
<published>2019-12-21T12:31:48Z</published>
<updated>2019-12-21T12:31:49Z</updated>
<link rel="alternate" type="text/html" href="https://status.digitalocean.com/incidents/d0glfj89j57y"/>
<title>Spaces issue in SGP1 region</title>
<content type="html"><p><small>Dec <var data-var='date'>21</var>, <var data-var='time'>12:31</var> UTC</small><br><strong>Resolved</strong> - Our Engineering team has resolved the slowness or inaccessibility issues with Spaces in our SGP1 region. Accessing Spaces should now be operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.</p><p><small>Dec <var data-var='date'>21</var>, <var data-var='time'>12:01</var> UTC</small><br><strong>Monitoring</strong> - Our Engineering team has resolved the slowness or inaccessibility issues with Spaces in our SGP1 region and is monitoring the situation. We will post an update as soon as the issue is fully resolved.</p><p><small>Dec <var data-var='date'>21</var>, <var data-var='time'>11:17</var> UTC</small><br><strong>Identified</strong> - Our Engineering team has identified the cause of the slowness or inaccessibility issue with Spaces in our SGP1 region. We will post an update as soon as additional information is available.</p><p><small>Dec <var data-var='date'>21</var>, <var data-var='time'>10:23</var> UTC</small><br><strong>Investigating</strong> - Our engineering team is investigating an issue with Spaces in our SGP1 region. During this time you may experience slowness or inaccessibility with our Spaces. We apologize for the inconvenience and will share an update once we have more information.</p></content>
</entry>
<entry>
<id>tag:status.digitalocean.com,2005:Incident/3342542</id>
<published>2019-12-20T00:12:05Z</published>
<updated>2019-12-20T00:12:06Z</updated>
<link rel="alternate" type="text/html" href="https://status.digitalocean.com/incidents/z8tp0f9sq047"/>
<title>Droplet Connectivity Impacted During LON1 Network Maintenance</title>
<content type="html"><p><small>Dec <var data-var='date'>20</var>, <var data-var='time'>00:12</var> UTC</small><br><strong>Resolved</strong> - The connectivity issues on Droplet public and private networking have been resolved. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.</p><p><small>Dec <var data-var='date'>19</var>, <var data-var='time'>23:24</var> UTC</small><br><strong>Monitoring</strong> - We encountered a hardware issue during the scheduled LON1 Network Maintenance, during which users may have experienced connectivity issues on Droplet public and private networking. Our Network team has reverted the maintenance changes in order to restore connectivity and is monitoring closely. If you still experience problems, please open a ticket for our support team.</p></content>
</entry>
<entry>
<id>tag:status.digitalocean.com,2005:Incident/3342287</id>
<published>2019-12-19T23:27:20Z</published>
<updated>2019-12-19T23:27:21Z</updated>
<link rel="alternate" type="text/html" href="https://status.digitalocean.com/incidents/qv291p2grwc3"/>
<title>LON1 Region Network Maintenance</title>
<content type="html"><p><small>Dec <var data-var='date'>19</var>, <var data-var='time'>23:27</var> UTC</small><br><strong>Completed</strong> - We are currently investigating a hardware issue which has impacted this maintenance. Our Networking team has reverted the maintenance changes in order to restore connectivity and is monitoring closely. We will reschedule this maintenance for a future date.</p><p><small>Dec <var data-var='date'>19</var>, <var data-var='time'>22:07</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Dec <var data-var='date'>19</var>, <var data-var='time'>22:06</var> UTC</small><br><strong>Scheduled</strong> - The Networking team will be making changes to our core networking equipment to improve performance and reliability for our LON1 location<br /><br />Expected Impact:<br /><br />There may be a few minutes of increased latency as well as small amounts of packet loss while we shift traffic to redundant devices. We will endeavor to keep this to a minimum for the duration of the change.<br /><br />If you have any questions or concerns, please create a support ticket.</p></content>
</entry>
<entry>
<id>tag:status.digitalocean.com,2005:Incident/3342196</id>
<published>2019-12-19T23:18:57Z</published>
<updated>2019-12-19T23:18:57Z</updated>
<link rel="alternate" type="text/html" href="https://status.digitalocean.com/incidents/qmfcw6b0wpx3"/>
<title>Event Processing Delays</title>
<content type="html"><p><small>Dec <var data-var='date'>19</var>, <var data-var='time'>23:18</var> UTC</small><br><strong>Resolved</strong> - Our Engineering team has resolved the issue with event processing delays. Users should no longer see delays while working with resources. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.</p><p><small>Dec <var data-var='date'>19</var>, <var data-var='time'>22:44</var> UTC</small><br><strong>Monitoring</strong> - Our Engineering team has not observed any further delays for event processing, and will continue to monitor the situation. We will post an update as soon as the issue is fully resolved.</p><p><small>Dec <var data-var='date'>19</var>, <var data-var='time'>21:33</var> UTC</small><br><strong>Investigating</strong> - Our Engineering team is investigating an issue with event processing delays. During this time, users may observe a delay while working with resources, such as creating or destroying Droplets. We apologize for the inconvenience and will share an update once we have more information.</p></content>
</entry>
<entry>
<id>tag:status.digitalocean.com,2005:Incident/3311835</id>
<published>2019-12-17T23:41:57Z</published>
<updated>2019-12-17T23:41:58Z</updated>
<link rel="alternate" type="text/html" href="https://status.digitalocean.com/incidents/b939ctcc4yh2"/>
<title>Delayed Processing for Changes to Load Balancer Settings</title>
<content type="html"><p><small>Dec <var data-var='date'>17</var>, <var data-var='time'>23:41</var> UTC</small><br><strong>Resolved</strong> - Our Engineering team has resolved the issue regarding delayed processing for changes made to Load Balancer settings. Configuration changes for Load Balancers should be processing normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience and thank you for your patience throughout this incident.</p><p><small>Dec <var data-var='date'>16</var>, <var data-var='time'>21:19</var> UTC</small><br><strong>Update</strong> - Our Engineering team continues to roll out the fix for the issue with delayed processing for changes made to Load Balancer settings. At this time, the rollout is approximately 85% complete. Until the remaining 15% of Load Balancers have had the fix applied, users may continue to see delays in changes to those Load Balancers. In most cases, any changes applied to the remaining 15% of Load Balancers should take effect within a period of thirty minutes. We thank you again for your patience and will share another update once the rollout is complete.</p><p><small>Dec <var data-var='date'>14</var>, <var data-var='time'>20:20</var> UTC</small><br><strong>Update</strong> - Deployment of a fix by our Engineering team is still ongoing at this time, and we continue to monitor the progress closely. Until this rollout is complete, some users may continue to experience delays in configuration changes such as adding or removing Droplets within their Load Balancers. We apologize for the lengthy process, and we appreciate your patience throughout this incident. We will share more information as soon as it is available.</p><p><small>Dec <var data-var='date'>13</var>, <var data-var='time'>16:37</var> UTC</small><br><strong>Update</strong> - Our Engineering team continues to roll out a fix for the root cause of this incident. Until this fix is fully deployed, some users may continue to experience delays in configuration changes such as adding or removing Droplets within their Load Balancers. We apologize for the lengthy process, and we appreciate your patience throughout this incident. We will share more information as soon as it is available.</p><p><small>Dec <var data-var='date'>13</var>, <var data-var='time'>03:37</var> UTC</small><br><strong>Update</strong> - Our Engineering team is rolling out a fix for the root cause of this incident. Until this is fully rolled out, some users may continue experiencing delays in configuration changes such as adding or removing Droplets within their Load Balancers. We estimate this roll out will finish by 13/Dec/2019 14:00 UTC, and will provide another update by that time at the latest.</p><p><small>Dec <var data-var='date'>12</var>, <var data-var='time'>18:40</var> UTC</small><br><strong>Update</strong> - Our Engineering team is now deploying a fix for the root cause of the issue. While this fix is deploying, users may experience a very brief period of packet loss as their Load Balancers are updated. We will share an update once the deployment is complete, and we appreciate your patience.</p><p><small>Dec <var data-var='date'>12</var>, <var data-var='time'>17:03</var> UTC</small><br><strong>Update</strong> - Our Engineering team continues to work on a fix for the issue with delays in processing changes for Load Balancer settings. At this time, a new agent version is being pushed out in order to help resolve these issues. Users may still be experiencing delays in configuration changes, such as adding or removing Droplets within Load Balancers. We will post an update as soon as additional information is available.</p><p><small>Dec <var data-var='date'>12</var>, <var data-var='time'>06:31</var> UTC</small><br><strong>Identified</strong> - Our Engineering team has identified the cause of the issue regarding delayed processing for changes made to load balancer settings and is working on a fix. During this time, you may observe that load balancers take longer than expected to successfully accept new configuration changes, such as adding or removing Droplets. We will post an update as soon as additional information is available.</p><p><small>Dec <var data-var='date'>11</var>, <var data-var='time'>23:04</var> UTC</small><br><strong>Investigating</strong> - Our Engineering team is investigating an issue regarding delayed processing for changes made to load balancer settings. During this time, you may observe that load balancers take longer than expected to successfully accept new configuration changes, such as adding or removing Droplets. We apologize for the inconvenience and will share an update once we have more information.</p></content>
</entry>
<entry>
<id>tag:status.digitalocean.com,2005:Incident/3327545</id>
<published>2019-12-16T17:32:02Z</published>
<updated>2019-12-16T17:32:03Z</updated>
<link rel="alternate" type="text/html" href="https://status.digitalocean.com/incidents/1gvtdg42r9g4"/>
<title>Global Droplet Creation Issues</title>
<content type="html"><p><small>Dec <var data-var='date'>16</var>, <var data-var='time'>17:32</var> UTC</small><br><strong>Resolved</strong> - Our engineering team has confirmed resolution of the issues with creation failures. All systems should be operating normally. If you continue to experience any problems, please open a ticket with our support team. We apologize for any inconvenience.</p><p><small>Dec <var data-var='date'>16</var>, <var data-var='time'>15:25</var> UTC</small><br><strong>Monitoring</strong> - Our Engineering team has identified the issue with creation failures, and users should no longer be experiencing issues at this time. Our team is now monitoring the situation for any further issues. We apologize for the inconvenience and will share an update once we have confirmed that the issue is resolved.</p><p><small>Dec <var data-var='date'>16</var>, <var data-var='time'>14:58</var> UTC</small><br><strong>Investigating</strong> - Our Engineering team is investigating an issues with creation failures in our regions. During this time, users may experience issues or errors while attempting to create Droplets. We apologize for the inconvenience and will share an update once we have more information.</p></content>
</entry>
<entry>
<id>tag:status.digitalocean.com,2005:Incident/3324046</id>
<published>2019-12-15T21:17:30Z</published>
<updated>2019-12-15T21:17:31Z</updated>
<link rel="alternate" type="text/html" href="https://status.digitalocean.com/incidents/2c4jf9nzhxf5"/>
<title>Volume Performance Issues in NYC3</title>
<content type="html"><p><small>Dec <var data-var='date'>15</var>, <var data-var='time'>21:17</var> UTC</small><br><strong>Resolved</strong> - Our engineering team has resolved the issue with Volumes being slow in our NYC3 region. Volumes should now be operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.</p><p><small>Dec <var data-var='date'>15</var>, <var data-var='time'>20:48</var> UTC</small><br><strong>Monitoring</strong> - Our Engineering team has completed the maintenance, and the issue with latency for Volumes in our NYC3 region should now be resolved. Our team in monitoring the situation, and we will post an update as soon as we confirm the issue is fully resolved.</p><p><small>Dec <var data-var='date'>15</var>, <var data-var='time'>20:11</var> UTC</small><br><strong>Update</strong> - Our Engineering team is now performing emergency maintenance to help ensure that performance continues to be stable. During this time, there is a small chance that users may experience latency for Volumes in the NYC3 region, but we do not expect to see this impact. Once the maintenance has been completed, we will post another update. Thank you for your patience!</p><p><small>Dec <var data-var='date'>15</var>, <var data-var='time'>18:57</var> UTC</small><br><strong>Update</strong> - Our Engineering team continues to investigate the issue with Volume latency in our NYC3 region. At this time, users should no longer be experiencing any impact, and requests should be performing as normal. Our team is still looking to identify the root cause for the incident, and we will post an update as soon as we have further information.</p><p><small>Dec <var data-var='date'>15</var>, <var data-var='time'>16:04</var> UTC</small><br><strong>Update</strong> - Our Engineering team continues to investigate the issue with Volume latency in our NYC3 Region. At this time, users may experience some latency for requests to impacted Volumes. As soon as we have further information, we will share another update.</p><p><small>Dec <var data-var='date'>15</var>, <var data-var='time'>12:42</var> UTC</small><br><strong>Investigating</strong> - Our Engineering team is investigating an issue with Volumes being slow in our NYC3 region. During this time you may experience slowness in accessing Volumes. We apologize for the inconvenience and will share an update once we have more information.</p></content>
</entry>
<entry>
<id>tag:status.digitalocean.com,2005:Incident/3314479</id>
<published>2019-12-12T23:30:00Z</published>
<updated>2019-12-12T16:20:47Z</updated>
<link rel="alternate" type="text/html" href="https://status.digitalocean.com/incidents/m6hgmpr20lb0"/>
<title>Floating IP Issues in BLR1</title>
<content type="html"><p><small>Dec <var data-var='date'>12</var>, <var data-var='time'>23:30</var> UTC</small><br><strong>Resolved</strong> - Our engineering team identified an issue that resulted in errors with Floating IP connectivity in our BLR1 region. This impacted a subset of Floating IP addresses, totaling about 2500 IPs. This resulted in issues with network connectivity for the impacted IP addresses, leading to users being unable to reach sites pointed to the IP addresses, or otherwise connect to them. The impact lasted for a period of about five hours. Our engineering team was able to implement a fix to resolve the issue and restore connectivity to the Floating IP addresses.</p></content>
</entry>
<entry>
<id>tag:status.digitalocean.com,2005:Incident/3314808</id>
<published>2019-12-12T20:04:23Z</published>
<updated>2019-12-12T20:04:24Z</updated>
<link rel="alternate" type="text/html" href="https://status.digitalocean.com/incidents/4pb1zr8rbpv5"/>
<title>Issues with Multiple Services</title>
<content type="html"><p><small>Dec <var data-var='date'>12</var>, <var data-var='time'>20:04</var> UTC</small><br><strong>Resolved</strong> - Our Engineering team has resolved the issue with multiple services, and all systems should now be operating normally. If you continue to experience issues, please open a ticket with our support team. We apologize for any inconvenience.</p><p><small>Dec <var data-var='date'>12</var>, <var data-var='time'>19:27</var> UTC</small><br><strong>Monitoring</strong> - Our Engineering team has identified the issue and implemented a fix to resolve the issues with multiple services, and is monitoring the situation. We will post an update as soon as the issue is fully resolved.</p><p><small>Dec <var data-var='date'>12</var>, <var data-var='time'>18:01</var> UTC</small><br><strong>Investigating</strong> - Our Engineering team is investigating an issue with multiple services, including our Cloud Control Panel and API. During this time, users may experience issues accessing and using the Cloud Control Panel and API, or managing/accessing services and resources within their account. We apologize for the inconvenience and will share an update once we have more information.</p></content>
</entry>
</feed>