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
Spaces   Operational
Support Center   Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Sep 24, 2017

No incidents reported today.

Sep 23, 2017

No incidents reported.

Sep 22, 2017

No incidents reported.

Sep 21, 2017
Completed - The scheduled maintenance has been completed.
Sep 21, 12:57 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 21, 12:00 UTC
Scheduled - Start: 2017-09-21 12:00 UTC
End: 2017-09-21 15:00 UTC

During the above window the network engineering team will be performing maintenance on border Internet routers in SFO2. This is pro-active maintenance to ensure optimal performance of the networking infrastructure and enable further capacity expansion.

Expected Impact: 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.

Approximately 30 minutes prior to the maintenance we will post an update on status.digitalocean.com and periodic updates will follow as work progresses.

Do not hesitate to contact support if you have any additional questions or concerns.
Sep 21, 07:48 UTC

A security vulnerability has been identified affecting Ubuntu or Debian-based Droplets with MySQL installed via 1-Click deployments, including:

- PHPMyAdmin
- MySQL
- OwnCloud
- Ghost
- LAMP
- LEMP
- WordPress

During the installation of MySQL, the debian-sys-maint MySQL user was created by the Ubuntu packaging, and our build process did not change debian-sys-maint's default password. Users who did not change the debian-sys-maint password in "/etc/mysql/debian.cnf" and in MySQL for the deployed 1-Click database instances are not secure.

Impact:
- The debian-sys-maint passwords are not unique. If your password remained unchanged after install, your MySQL database is not secure.
- MySQL and PHPMyAdmin 1-Clicks are remotely exploitable unless action has been taken to change the default password.
- LAMP, LEMP, WordPress and OwnCloud 1-Clicks are locally exploitable.
- If you have installed PHPMyAdmin or another program that provides proxy access to MySQL, then your 1-Click is likely remotely exploitable.

We have notified the customers who were most likely impacted by this vulnerability. We have also implemented a patch, so that moving forward, all deployed instances using these 1-Clicks will have custom generated passwords per instance. All 1-Clicks with MySQL created on or after September 18, 2017 now change the debian-sys-maint user during the first-boot process.

As part of our discovery process for this issue, we identified that other Cloud providers and third-party Marketplaces are affected. We strongly advise that users check all pre-installed MySQL instances on Debian/Ubuntu for this issue.

If you have not updated your credentials upon install, we recommend doing so now. To easily change the debian-sys-maint credentials, we have provided a script[1], which will ensure that your MySQL database is not accessible with default credentials. You may also simply redeploy using the newly patched 1-Clicks. If you changed the debian-sys-maint MySQL user credentials upon install, you are not impacted by this vulnerability and no action is required.

[1] https://github.com/digitalocean/debian-sys-maint-roll-passwd

Completed - The scheduled maintenance has been completed.
Sep 21, 10:28 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 21, 09:00 UTC
Scheduled - Start: 2017-09-21 09:00 UTC
End: 2017-09-21 12:00 UTC

During the above window the network engineering team will be performing maintenance on border Internet routers in SFO1. This is pro-active maintenance to ensure optimal performance of the networking infrastructure and enable further capacity expansion.

Expected Impact: 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.

Approximately 30 minutes prior to the maintenance we will post an update on status.digitalocean.com and periodic updates will follow as work progresses.

Do not hesitate to contact support if you have any additional questions or concerns.
Sep 21, 07:47 UTC
Sep 20, 2017

No incidents reported.

Sep 19, 2017

No incidents reported.

Sep 18, 2017

No incidents reported.

Sep 17, 2017

No incidents reported.

Sep 16, 2017

No incidents reported.

Sep 15, 2017

No incidents reported.

Sep 14, 2017
Resolved - This issue affecting Load Balancers graphs has been confirmed to be resolved. If you continue to experience any issues please reach out to our Support team for further assistance.
Sep 14, 22:24 UTC
Update - Our engineering team has identified and resolved the issue with Load Balancers graphs not working. Currently 90% of Load Balancers graphs are functional. All other Load Balancer functionality is unaffected.
Sep 12, 19:53 UTC
Identified - Our engineering team has identified a cause for this issue affecting Load Balancers graphs and is rolling out a fix. Other functionality of the Load Balancer is not affected.
Sep 9, 18:46 UTC
Resolved - We have resolved the issue causing delays for event processing. We apologize for the inconvenience, and ask you to open a support ticket if you still see any problems.
Sep 14, 18:45 UTC
Monitoring - Event processing has been restored and we're monitoring to ensure that new events complete successfully. If you still see any problems using the control panel or API, please open a ticket for our Support team to investigate.
Sep 14, 18:25 UTC
Investigating - Our engineering team are investigating delays with event processing in all regions. During this time, events that are still processing may be delayed or encounter errors, and you may be unable to submit new events via the API or control panel.
Sep 14, 17:56 UTC
Sep 13, 2017
Resolved - The issue impacting the ability to tag Droplets when creating a new support ticket has been fully resolved. If you experience any further issues tagging a Droplet when creating a new support ticket, please reach out to our Support Team.
Sep 13, 04:19 UTC
Monitoring - The issue impacting the ability to tag Droplets when creating a new support ticket has been resolved. Our engineers will continue to monitor the situation. In the mean time, if you experience any issues tagging a Droplet when creating a new support ticket, please reach out to our Support Team.
Sep 12, 22:00 UTC
Investigating - We’ve detected an issue that prevents tagging a Droplet when submitting a new ticket through our Support Center. We will provide additional updates as information becomes available. In the meantime. when opening a new ticket, please do not tag a Droplet — instead, please provide the IP of the Droplet in the ticket body.
Sep 12, 18:24 UTC
Sep 11, 2017

No incidents reported.

Sep 10, 2017

No incidents reported.