DigitalOcean Services Status

All Systems Operational

API Operational
Billing Operational
Cloud Control Panel Operational
Cloud Firewall Operational
Community Operational
DNS Operational
Support Center Operational
Reserved IP Operational
WWW Operational
GenAI Platform Operational
App Platform Operational
Global Operational
Amsterdam Operational
Bangalore Operational
Frankfurt Operational
London Operational
New York Operational
San Francisco Operational
Singapore Operational
Sydney Operational
Toronto Operational
Container Registry Operational
Global Operational
AMS3 Operational
BLR1 Operational
FRA1 Operational
NYC3 Operational
SFO2 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
Droplets Operational
Global Operational
AMS2 Operational
AMS3 Operational
BLR1 Operational
FRA1 Operational
LON1 Operational
NYC1 Operational
NYC2 Operational
NYC3 Operational
SFO1 Operational
SFO2 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
TOR1 Operational
Event Processing Operational
Global Operational
AMS2 Operational
AMS3 Operational
BLR1 Operational
FRA1 Operational
LON1 Operational
NYC1 Operational
NYC2 Operational
NYC3 Operational
SFO1 Operational
SFO2 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
TOR1 Operational
Functions Operational
Global Operational
AMS3 Operational
BLR1 Operational
FRA1 Operational
LON1 Operational
NYC1 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
TOR1 Operational
GPU Droplets Operational
Global Operational
NYC2 Operational
TOR1 Operational
Managed Databases Operational
Global Operational
AMS3 Operational
BLR1 Operational
FRA1 Operational
LON1 Operational
NYC1 Operational
NYC2 Operational
NYC3 Operational
SFO2 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
TOR1 Operational
Monitoring Operational
Global Operational
AMS2 Operational
AMS3 Operational
BLR1 Operational
FRA1 Operational
LON1 Operational
NYC1 Operational
NYC2 Operational
NYC3 Operational
SGP1 Operational
SFO1 Operational
SFO2 Operational
SFO3 Operational
SYD1 Operational
TOR1 Operational
Networking Operational
Global Operational
AMS2 Operational
AMS3 Operational
BLR1 Operational
FRA1 Operational
LON1 Operational
NYC1 Operational
NYC2 Operational
NYC3 Operational
SFO1 Operational
SFO2 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
TOR1 Operational
Kubernetes Operational
Global Operational
AMS3 Operational
BLR1 Operational
FRA1 Operational
LON1 Operational
NYC1 Operational
NYC3 Operational
SFO2 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
TOR1 Operational
Load Balancers Operational
Global Operational
AMS2 Operational
AMS3 Operational
BLR1 Operational
FRA1 Operational
LON1 Operational
NYC1 Operational
NYC2 Operational
NYC3 Operational
SFO1 Operational
SFO2 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
TOR1 Operational
Spaces Operational
Global Operational
AMS3 Operational
FRA1 Operational
NYC3 Operational
SFO2 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
BLR1 Operational
Spaces CDN Operational
Global Operational
AMS3 Operational
FRA1 Operational
NYC3 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
VPC Operational
Global Operational
AMS2 Operational
AMS3 Operational
BLR1 Operational
FRA1 Operational
LON1 Operational
NYC1 Operational
NYC2 Operational
NYC3 Operational
SFO1 Operational
SFO2 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
TOR1 Operational
Volumes Operational
Global Operational
AMS2 Operational
AMS3 Operational
BLR1 Operational
FRA1 Operational
LON1 Operational
NYC1 Operational
NYC2 Operational
NYC3 Operational
SFO1 Operational
SFO2 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
TOR1 Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
May 9, 2025

No incidents reported today.

May 8, 2025
Droplet Metrics in BLR1
Resolved - Our Engineering team has confirmed the resolution of the issue affecting certain Droplet metrics in the BLR1 region. Users should no longer see intermittent gaps in monitoring graphs for Droplets in the BLR1 region.

We appreciate your patience and apologize for any inconvenience this may have caused.
May 8, 13:01 UTC
Monitoring - Our Engineering team has implemented a fix to address the intermittent unavailability of Droplet metrics and delayed Resource Alerts in the BLR1 region.

Our team is now and monitoring the results and will continue to do so for an extended period to ensure this sporadic issue is addressed by the implemented fix.

At this time, we expect users not to experience further metrics gaps or delays in alerts.

We will post an update as soon as we confirm this incident is fully resolved or once we have further information. Thank you for your patience.
May 8, 01:26 UTC
Update - Our Engineering team is continuing to investigate the root cause of the issue with intermittent unavailability of Droplet metrics in the BLR1 region. Multiple reproduction efforts and testing against potential root causes are underway. Due to the sporadic nature of the issue, we anticipate incident updates for this issue to be less frequent, but we will share new information as soon as it is available.

At this time, users impacted by this incident will experience intermittent gaps in monitoring graphs for Droplets in BLR1, as well as delayed notifications for Resource Alerts (for any resources in BLR1).

We apologize for the inconvenience, and we'll share an update once we have more information.
May 7, 22:04 UTC
Update - Our Engineering team continues to investigate the intermittent unavailability of certain Droplet metrics in the BLR1 region. Due to the sporadic nature of this issue, our analysis requires additional time to correlate patterns and isolate the root cause.

We apologize for the inconvenience, and we'll share an update once we have more information.
May 7, 09:41 UTC
Investigating - Our Engineering team is currently investigating issues with certain Droplet metrics that are missing for the BLR1 region. Users may experience issues when accessing certain metrics on Droplets.

We apologize for the inconvenience, and we'll share an update once we have more information.
May 6, 13:00 UTC
May 7, 2025
LON1 Network Maintenance 2025-05-07 20:00 UTC
Completed - The scheduled maintenance has been completed.
May 7, 23:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 7, 20:00 UTC
Scheduled - Start: 2025-05-07 20:00 UTC
End: 2025-05-07 23:00 UTC

During the above window, our Networking team will be making changes to the core networking infrastructure to improve performance and scalability in the LON1 region.

Expected impact:

During the maintenance window, users may experience delays or failures with event processing for a brief duration on Droplets and Droplet-based services, including Droplets, Managed Kubernetes, Load Balancers, Container Registry, and App Platform. We will endeavor to keep this to a minimum for the duration of the change.

If you have any questions related to this issue, please send us a ticket from your cloud support page. https://cloudsupport.digitalocean.com/s/createticket
May 4, 20:10 UTC
May 6, 2025
May 5, 2025
Droplet Creation in NYC1
Resolved - Our Engineering team has confirmed the complete resolution of the issue that was affecting Droplet creation and console access in the NYC1 region. Users should now be able to deploy new droplets and access them normally in the NYC1 region.

All systems are now operating normally. We appreciate your patience and apologize for any inconvenience this may have caused.
May 5, 15:46 UTC
Monitoring - Our Engineering team has implemented a fix for the issue affecting Droplet creation and console access in the NYC1 region. Impacted users may have seen 504 Gateway Timeout errors during Droplet creation or when accessing the Droplet console.

Our team is currently monitoring the situation to ensure stability. We will provide a final update once we confirm the issue is fully resolved.
May 5, 15:18 UTC
Investigating - Our Engineering team is currently investigating an issue with creating Droplets in NYC1 region. During this time, users may see 504 Gateway Timeout errors when creating droplets in the NYC1 region.

We apologize for the inconvenience and will provide an update as soon as we have more information.
May 5, 14:18 UTC
May 4, 2025

No incidents reported.

May 3, 2025

No incidents reported.

May 2, 2025

No incidents reported.

May 1, 2025

No incidents reported.

Apr 30, 2025
Core Infrastructure Maintenance
Completed - The scheduled maintenance has been completed.
Apr 30, 21:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 30, 13:00 UTC
Scheduled - Start: 2025-04-30 13:00 UTC
End: 2025-04-30 21:00 UTC

Hello,

During the above window, our Engineering team will be performing maintenance on core control plane infrastructure. Please note that the existing infrastructure will continue running without issue. This maintenance may impact create, read, update, and delete (CRUD) operations in all regions.

Expected Impact:

During the maintenance window, users may experience increased latency during two 5 minute windows with the following platform operations:

Cloud Control Panel and API operations
Event processing
Droplet creates, resizes, rebuilds, and power events
Managed Kubernetes reconciliation and scaling
Load Balancer operations
Container Registry operations
App Platform operations
Managed Database creation and scaling

We do not expect any impact to customer traffic due to this maintenance. If an unexpected issue for the control plane arises, we will endeavor to keep any impact to a minimum and may revert if required.

If you have any questions related to this maintenance please send us a ticket from your cloud support page. https://cloudsupport.digitalocean.com/s/createticket

Thank you,
Team DigitalOcean
Apr 28, 13:25 UTC
Spaces Availability in FRA1
Resolved - Our Engineering team has confirmed the complete resolution of the issue that was impacting the availability of Spaces in our FRA1 region. Users should no longer experience elevated error rates when accessing Spaces in the region.

We appreciate your patience and understanding while we worked to restore normal service.

If you continue to experience any issues, please open a support ticket from within the Cloud Control Panel for further review.
Apr 30, 14:57 UTC
Monitoring - Our Engineering team has implemented a fix for the issue affecting the availability of Spaces in our FRA1 region. Users should now see improved performance, and error rates have decreased.

We are continuing to monitor the situation closely to ensure stability. Thank you for your patience during the process and we will provide a final update once we confirm the issue is fully resolved.
Apr 30, 14:14 UTC
Investigating - Our Engineering team is currently investigating an issue affecting the availability of Spaces in our FRA1 region. During this time, users may experience high error rate when attempting to access Spaces in this region.

We are actively working on identifying the root cause and resolving the issue as quickly as possible. We understand the inconvenience this may cause and appreciate your patience.

We will provide further updates in the due course.
Apr 30, 13:06 UTC
Managed Kubernetes Nodes Networking
Resolved - Our Engineering team has confirmed full resolution of the network issue with new DOKS worker nodes in our SFO2 region.

If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Apr 30, 00:11 UTC
Monitoring - Our Engineering team identified the cause of the issue and has rolled out a fix to resolve the network issue with new DOKS worker nodes. At this time, all services should be operating normally.

We are actively monitoring the fix and will post an update as soon as the issue is fully resolved.
Apr 29, 23:49 UTC
Investigating - Our Engineering team is investigating an issue causing new DOKS worker nodes to have network issues in our SFO2 region. Operations such as creating new DOKS nodes, manually or autoscaled, will have network connectivity issues within the clusters they are added to during this time.

Our Engineering team is actively working to identify the root cause and restore service as quickly as possible. We will continue to provide updates here as we make progress.
Apr 29, 22:25 UTC
Apr 29, 2025
Apr 28, 2025
Networking in LON1
Resolved - This incident has been resolved.
Apr 28, 11:17 UTC
Investigating - Between 09:58 UTC and 10:11 UTC, our Engineering team observed issues impacting DNS resolution in our LON1 region. During this time, some users may have experienced errors while trying to resolve domain names from within Digitalocean resources.

Our team was able to take quick action to mitigate the impact and resolve the issue, and all services in the LON1 region are now functioning normally. Thank you for your patience, and we apologize for any inconvenience.

If you are still experiencing issues or have additional questions, please open a Support ticket right away.
Apr 28, 11:14 UTC
Apr 27, 2025

No incidents reported.

Apr 26, 2025

No incidents reported.

Apr 25, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage
DigitalOcean Home API Docs Community