All Systems Operational
Regions Operational
Global Operational
AMS2 Operational
AMS3 Operational
BLR1 Operational
FRA1 Operational
LON1 Operational
NYC1 Operational
NYC2 Operational
NYC3 Operational
SFO1 Operational
SFO2 Operational
SGP1 Operational
TOR1 Operational
Services Operational
API Operational
Block Storage Operational
Cloud Control Panel Operational
Cloud Firewall Operational
Community Operational
DNS Operational
Droplets Operational
Event Processing Operational
Load Balancers Operational
Monitoring Operational
Networking Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Jun 29, 2017

No incidents reported today.

Jun 28, 2017

No incidents reported.

Jun 27, 2017

No incidents reported.

Jun 26, 2017

No incidents reported.

Jun 25, 2017

No incidents reported.

Jun 24, 2017

No incidents reported.

Jun 23, 2017

No incidents reported.

Jun 22, 2017
Resolved - We identified a connectivity issue with one of our providers and have restored connectivity in SGP1. Please open a support ticket if you still see any problems accessing your Droplets there.
Jun 22, 19:00 UTC
Monitoring - Network connectivity in the SGP1 region has stabilized. We're continuing to monitor the issue; if you still experience any problems, please open a ticket for our support team.
Jun 22, 18:45 UTC
Investigating - Our network team are investigating connectivity issues in the SGP1 region. During this time, you may be unable to connect to your Droplets there.
Jun 22, 18:34 UTC
Jun 21, 2017

Every month, as part of our process for handling user suspension for nonpayment, we send up to three notices within a 15 day period to notify users that their account will be suspended if they don’t pay the past due balance. If no action is taken we reserve the right to delete the user’s suspended machines after the final termination notice (see item 5.7 in our Terms of Service Agreement). On 2017-06-21 during a routine update to our account suspension process, an incorrect query caused the deletion of all resources (Droplets, Load Balancers, etc) belonging to 1,913 users. This occurred sooner than we intended for it to happen.

We learned that the root cause was a legacy process that did not correctly delete the suspension time for these users. When we performed a routine update there was an inconsistency between the users’ status and the suspension time, which caused the deletion of the accounts and their data.

We conducted a recovery process for all users who had backups enabled on their Droplets as well as users who had taken existing snapshots. In total we were able to recover backups and snapshots for 522 Droplets for some 315 total users. We were unable to recover the resources of all other affected users. We are sorry for this incident and the impact it has had on you. Below we’ve outlined the measures we’re taking to prevent this in the future.

Future Measures
Now that we have identified the underlying cause of this incident, we have taken steps to ensure that user records will not be able to get into this state going forward. Additionally, we will be adding a ‘buffering’ mechanism between our suspension flow and resource deletion, to ensure that a more thorough recovery is possible in the future.

In Conclusion
We apologize to all of the affected users for this incident, and we are sorry that the result was a loss of your personal data. We take your data and trust very seriously and we are going through the process of crediting users that have reached out to us about the issue. If we are not already in direct contact and you did suffer a loss from this event, please open a ticket with our support team as soon as possible. While we encourage all users to take backups into their own hands, we fully take responsibility for this incident and apologize for the problems it may have caused you.

Jun 20, 2017

No incidents reported.

Jun 19, 2017
Resolved - This incident has been resolved.
Jun 19, 22:48 UTC
Monitoring - At this time, the network engineering team will be performing hardware maintenance on the private network in AMS3. We apologize for the short notice.

We expect there to be no noticeable impact, however; you may experience brief periods of increased latency and a small amount of packet loss lasting up to 2 minutes as traffic is re-routed. This will only affect the private network in AMS3.
Jun 19, 19:52 UTC
Jun 18, 2017

No incidents reported.

Jun 17, 2017

No incidents reported.

Jun 16, 2017

No incidents reported.

Jun 15, 2017

No incidents reported.