All Systems Operational
Cloud Control Panel Operational
Cloud Firewall Operational
Support Center Operational
GenAI Platform Operational
App Platform Operational
Global Operational
Amsterdam Operational
Atlanta 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
ATL1 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
ATL1 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
ATL1 Operational
NYC2 Operational
TOR1 Operational
Managed Databases Operational
Global Operational
AMS3 Operational
ATL1 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
ATL1 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
ATL1 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
Network File Storage Operational
Kubernetes Operational
Global Operational
AMS3 Operational
ATL1 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
ATL1 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
ATL1 Operational
BLR1 Operational
FRA1 Operational
NYC3 Operational
SFO2 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
LON1 Operational
Spaces CDN Operational
Global Operational
AMS3 Operational
ATL1 Operational
FRA1 Operational
NYC3 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
LON1 Operational
VPC Operational
Global Operational
AMS2 Operational
AMS3 Operational
ATL1 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
ATL1 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
Past Incidents
Feb 3, 2026
No incidents reported today.
Feb 2, 2026
No incidents reported.
Feb 1, 2026
No incidents reported.
Jan 31, 2026
No incidents reported.
Jan 30, 2026
No incidents reported.
Jan 29, 2026
No incidents reported.
Jan 28, 2026
Resolved -
Our Engineering team has resolved the issue affecting Kubernetes clusters and Droplet events in the FRA1 region. Between approximately 00:17 UTC and 14:30 UTC, customers may have experienced issues provisioning Kubernetes clusters and mounting volumes. All services should now be functioning normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Jan 28, 17:37 UTC
Monitoring -
Our Engineering team has implemented a fix to address the issue affecting Kubernetes clusters and Droplet events in the FRA1 region and is actively monitoring the situation. Customers should no longer experience issues provisioning Kubernetes clusters or mounting volumes. We will provide an update as soon as the issue is fully resolved.
Jan 28, 14:47 UTC
Identified -
Our Engineering team has identified the root cause of the issue impacting Kubernetes clusters and Droplet events in the FRA1 region and is actively working on a fix. In the meantime, users may continue to experience issues. We appreciate your patience and will share updates as more information becomes available.
Jan 28, 13:30 UTC
Investigating -
Our Engineering team is investigating an issue with Kubernetes clusters in the FRA1 region. During this time, subset of users may experience an issue while provisioning Kubernetes clusters and mounting volumes. Additionally, users may also notice the droplet events appearing to be stuck or delayed in this region. We apologize for the inconvenience and will share an update once we have more information.
Jan 28, 11:27 UTC
Resolved -
Our Engineering team has confirmed that the issue impacting our Droplet-based products in the FRA1 region has been completely mitigated. Users should no longer see issues with their Droplets and Droplet-related services. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Jan 28, 04:27 UTC
Monitoring -
Our Engineering team has identified the cause of the issue impacting our Droplet-based products in the FRA1 region and applied a fix. The impact has started to mitigate and users should be able to connect to their Droplets and also start to see events getting processed successfully. We're now monitoring the fix for stability and will post an update once we are confident it is successful.
Jan 28, 04:11 UTC
Investigating -
Our Engineering team is currently investigating an issue affecting events in FRA1. During this time, customers may experience delays or errors when creating or deleting Droplets, as well as when using Droplet-based products such as Load Balancers, Kubernetes Clusters, or Databases. Our teams are actively working to identify the root cause and restore full service as quickly as possible. We apologize for the inconvenience and will provide updates as more information becomes available.
Jan 28, 00:45 UTC
Jan 27, 2026
Completed -
The scheduled maintenance has been completed.
Jan 27, 13:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 27, 09:00 UTC
Scheduled -
Start: 2026-01-27 09: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 NYC3 region. Expected impact: We do not anticipate any downtime for Droplets or Droplet-related services, including Managed Databases, Load Balancers, App Platform, and Managed Kubernetes, as this maintenance has been carefully designed and tested to be seamless. In the unlikely event that an undetected misconfiguration occurs, a subset of customers could experience temporary network disruption. We will endeavor to keep this to a minimum for the duration of the change. 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
End: 2026-01-27 12:00 UTC
Jan 25, 09:28 UTC
Jan 26, 2026
Resolved -
From 20:45 UTC to 21:06 UTC, users may have experienced issue affecting the Cloud Control Panel, API, and related services. Our Engineering team has confirmed that the issue is fully resolved, and all systems are now operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Jan 26, 22:44 UTC
Monitoring -
Our Engineering team has implemented a fix for the issue affecting the Cloud Control Panel, API, and related services. We are observing recovery, and users should now be able to access their accounts and use the API without errors. We are continuing to monitor the situation closely and will provide an update once full resolution is confirmed.
Jan 26, 21:27 UTC
Investigating -
Our Engineering team is investigating an issue impacting multiple services including the Cloud Control Panel and API. Users may encounter errors when accessing their accounts or using the API. We are actively working to resolve this issue and will provide updates as soon as more information becomes available.
Jan 26, 21:06 UTC
Jan 25, 2026
No incidents reported.
Jan 24, 2026
No incidents reported.
Jan 23, 2026
No incidents reported.
Jan 22, 2026
No incidents reported.
Jan 21, 2026
No incidents reported.
Jan 20, 2026
Resolved -
The issue impacting App Platform deployments has been successfully resolved. Users should no longer encounter delays during the build phase or have deployments getting stuck. All services are now confirmed to be stable and operating normally. We appreciate your patience throughout this but if you continue to experience any issues, please create a support ticket for further analysis.
Jan 20, 18:25 UTC
Monitoring -
Our Engineering team has implemented necessary changes to address the issue impacting both new and in-progress App Platform Deployments. Our team is currently monitoring the situation. Users should now notice improvements in deployment performance. We appreciate your patience. We'll update once the issue is confirmed to be resolved.
Jan 20, 18:05 UTC