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
Billing   Operational
Block Storage   Operational
Cloud Control Panel   Operational
Cloud Firewall   Operational
Community   Operational
DNS   Operational
Droplets   Operational
Event Processing   Operational
Load Balancers   Operational
Managed Databases   Operational
Monitoring   Operational
Networking   Operational
Spaces   Operational
Support Center   Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Feb 19, 2019

No incidents reported today.

Feb 18, 2019
Resolved - Our engineering team has resolved the issue with Block Storage in our SGP1 region and should now be operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Feb 18, 06:59 UTC
Monitoring - Our engineering team has implemented a fix to resolve the issue with Block Storage in our SGP1 region and is monitoring the situation. We will post an update as soon as the issue is fully resolved.
Feb 18, 06:24 UTC
Identified - Our engineering team has identified the cause of the issue with Block Storage in our SGP1 region and is actively working on a fix. We will post an update as soon as additional information is available.
Feb 18, 05:31 UTC
Investigating - Our engineering team is investigating an issue with Block Storage in our SGP1 region. During this time you may experience issues connecting to Block Storage Volumes. We apologize for the inconvenience and will share an update once we have more information.
Feb 18, 04:31 UTC
Feb 17, 2019

No incidents reported.

Feb 16, 2019

No incidents reported.

Feb 15, 2019

No incidents reported.

Feb 14, 2019

No incidents reported.

Feb 13, 2019
Completed - The scheduled maintenance has been completed.
Feb 13, 23:50 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 13, 17:50 UTC
Scheduled - During this time, our colocation provider will be performing maintenance in our NYC3 location in preparation for expansion. Due to this, the NYC3 location will lose power redundancy during this time. No impact is expected from this, however, if something does go awry, there could be service disruptions due to the lack of power redundancy.
Feb 13, 17:45 UTC
Feb 12, 2019

No incidents reported.

Feb 11, 2019

No incidents reported.

Feb 10, 2019

No incidents reported.

Feb 9, 2019
Resolved - Our engineering team has resolved the issue with event processing in our NYC3 region. Attempting to power cycle, resize, create and delete Droplets should now be operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Feb 9, 18:42 UTC
Monitoring - Our engineering team has implemented a fix to resolve the issue with event processing in our NYC3 region and is monitoring the situation. We will post an update as soon as the issue is fully resolved.
Feb 9, 17:27 UTC
Investigating - Our engineering team is investigating issues affecting event processing in our NYC3 region. At this time, you may experience delays when attempting to power cycle, resize, create, and delete Droplets in this region. We apologize for the inconvenience this may cause and will post an update as soon as we have more information.
Feb 9, 17:06 UTC
Resolved - Our engineering team has resolved the issue with Kubernetes cluster operations. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Feb 9, 11:29 UTC
Monitoring - Our engineering team has implemented a fix to resolve the issue with Kubernetes cluster operations and is monitoring the situation. We will post an update as soon as the issue is fully resolved.
Feb 9, 10:49 UTC
Identified - Our engineering team has identified the cause of the issue with Kubernetes cluster operations and is actively working on a fix. We will post an update as soon as additional information is available.
Feb 9, 01:52 UTC
Investigating - Our engineering team is investigating an issue with Kubernetes cluster operations. During this time, you may experience delayed processing of any cluster operations and unavailability of the Cloud panel or the API. Existing, running clusters should not be affected. We apologize for the inconvenience and will share an update once we have more information.
Feb 9, 00:56 UTC
Feb 8, 2019

No incidents reported.

Feb 7, 2019
Resolved - Our engineering team has resolved the issue with networking. If you continue to experience problems, please open a ticket with our support team through the cloud portal. We apologize for any inconvenience.
Feb 7, 17:07 UTC
Monitoring - Our engineering team is monitoring an issue that occurred which impacted networking. Impact to services has now subsided, but users may have experienced delays while processing actions within their account, and seen issues with reaching the DigitalOcean control panel and API . We apologize for the inconvenience and will share an update as soon as the issue is fully resolved.
Feb 7, 16:35 UTC
Feb 6, 2019
Resolved - Our email vendor has resolved the issue that impacted inbound emails to our support team. Tickets sent to support@digitalocean.com are now being added to our queues. We apologize for any inconvenience caused and thank you for your patience while we worked through this.
Feb 6, 15:41 UTC
Monitoring - Our email vendor has resolved the issue on their side, and mail has begun arriving to our systems again. Emailed tickets sent to support@digitalocean.com are now properly being added to our queues. Mail messages that were sent to us while the issue was ongoing have been received, and our support team are working through the backlog. We apologize for the inconvenience and appreciate your patience thus far.
Feb 5, 23:21 UTC
Update - Our email vendor is currently experiencing issues with incoming messages, and as a result tickets submitted to us via email are not being added to our queue. According to the vendor, this issue may last several days or longer. While we await a resolution, we ask that you please open a ticket from your account via: https://cloudsupport.digitalocean.com/s/createticket. We apologize for the inconvenience and any extended wait time you may have experienced awaiting a response from our support team.
Feb 5, 16:23 UTC
Identified - Our engineering team has identified the cause of the issue with opening support tickets via support@digitalocean.com and is actively working on a fix. We will post an update as soon as additional information is available.

In the meantime, we request you to create tickets from your account via:
https://cloudsupport.digitalocean.com/s/createticket
Feb 4, 10:52 UTC
Investigating - Our engineering team is investigating issues with opening support tickets via support@digitalocean.com. In the meantime, we request you to create tickets from your account via:
https://cloudsupport.digitalocean.com/s/createticket
We apologize for the inconvenience and will share an update once we have more information. During this time, tickets can still be created via customer portal.
Feb 4, 08:32 UTC
Feb 5, 2019
Resolved - Our engineering team has resolved the issue with Droplet creation delays. If you continue to experience problems, please open a ticket with our support team through the cloud portal. We apologize for any inconvenience.
Feb 5, 16:17 UTC
Monitoring - Our engineering team has implemented a fix to resolve the issue with Droplet creations and is monitoring the situation. We will post an update as soon as the issue is fully resolved.
Feb 5, 15:38 UTC
Investigating - Our engineering team is investigating an issue with creating Droplets. During this time, you may experience delays while creating a new Droplet. We apologize for the inconvenience and will share an update once we have more information.
Feb 5, 14:36 UTC