DigitalOcean Services Status

All Systems Operational

API Operational
Billing Operational
BYOIP Operational
Cloud Control Panel Operational
Cloud Firewall Operational
Community Operational
DNS Operational
Support Center Operational
Reserved IP Operational
WWW Operational
Agentic Inference Cloud Operational
Agent Runtime Operational
Inference Operational
ADK Operational
Knowledge Bases Operational
Guardrails Operational
Model Services Operational
App Platform Operational
Global Operational
Amsterdam Operational
Atlanta Operational
Bangalore Operational
Frankfurt Operational
Kansas Operational
London Operational
New York Operational
Richmond 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
MKC1 Operational
NYC1 Operational
NYC2 Operational
NYC3 Operational
RIC1 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
MKC1 Operational
NYC1 Operational
NYC2 Operational
NYC3 Operational
RIC1 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
MKC1 Operational
NYC1 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
TOR1 Operational
GPU Droplets Operational
Global Operational
ATL1 Operational
MKC1 Operational
NYC2 Operational
RIC1 Operational
TOR1 Operational
Managed Databases Operational
Global Operational
AMS3 Operational
ATL1 Operational
BLR1 Operational
FRA1 Operational
LON1 Operational
MKC1 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
MKC1 Operational
NYC1 Operational
NYC2 Operational
NYC3 Operational
RIC1 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
MKC1 Operational
NYC1 Operational
NYC2 Operational
NYC3 Operational
RIC1 Operational
SFO1 Operational
SFO2 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
TOR1 Operational
Network File Storage Operational
ATL1 Operational
MKC1 Operational
RIC1 Operational
Kubernetes Operational
Global Operational
AMS3 Operational
ATL1 Operational
BLR1 Operational
FRA1 Operational
LON1 Operational
MKC1 Operational
NYC1 Operational
NYC3 Operational
RIC1 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
MKC1 Operational
NYC1 Operational
NYC2 Operational
NYC3 Operational
RIC1 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
MKC1 Operational
NYC3 Operational
RIC1 Operational
SFO2 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
LON1 Operational
Spaces CDN Operational
Global Operational
AMS3 Operational
ATL1 Operational
FRA1 Operational
LON1 Operational
MKC1 Operational
NYC3 Operational
RIC1 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
VPC Operational
Global Operational
AMS2 Operational
AMS3 Operational
ATL1 Operational
BLR1 Operational
FRA1 Operational
LON1 Operational
MKC1 Operational
NYC1 Operational
NYC2 Operational
NYC3 Operational
RIC1 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
MKC1 Operational
NYC1 Operational
NYC2 Operational
NYC3 Operational
RIC1 Operational
SFO1 Operational
SFO2 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
TOR1 Operational
CSPM Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Aug 27, 2026
Rescheduled: Spaces Maintenance in BLR1
Completed - The scheduled maintenance has been completed.
Aug 27, 17:40 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 27, 16:00 UTC
Scheduled - Start: 2026-08-27 16:00 UTC
End: 2026-08-27 18:00 UTC

Hello,

During the above window, our Storage Engineering team will be performing maintenance on the Spaces service in the BLR1 region in order to improve performance and reliability. This is a rescheduled maintenance event previously scheduled for 2026-08-26.

Expected Impact:

This maintenance is designed to be low-impact. As infrastructure components are updated, you may experience brief network interruptions or momentary delays accessing your spaces. Service will resume normal operation automatically, and no action is required on your part.

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
Aug 26, 18:36 UTC
Rescheduled: Spaces Maintenance in NYC3, SFO2 and SFO3
Completed - The scheduled maintenance has been completed.
Aug 27, 08:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 27, 05:30 UTC
Scheduled - Start: 2026-08-27 05:30 UTC
End: 2026-08-27 08:30 UTC

Hello,

During the above window, our Storage Engineering team will be performing maintenance on the Spaces service in the NYC3, SFO2, and SFO3 regions in order to improve performance and reliability. This is a rescheduled maintenance event previously scheduled for 2026-08-26.

Expected Impact:

This maintenance is designed to be low-impact. As infrastructure components are updated, you may experience brief network interruptions or momentary delays accessing your spaces. Service will resume normal operation automatically, and no action is required on your part.

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

Thank you,
Team DigitalOcean
Aug 26, 05:56 UTC
Aug 26, 2026
Rescheduled: Spaces Maintenance in BLR1
Completed - The ongoing maintenance for Spaces has been cancelled and will be rescheduled for tomorrow. We apologize for any inconvenience and appreciate your understanding.
Aug 26, 16:28 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 26, 16:00 UTC
Scheduled - Start: 2026-08-26 16:00 UTC
End: 2026-08-26 18:00 UTC

Hello,

During the above window, our Storage Engineering team will be performing maintenance on the Spaces service in the BLR1 region in order to improve performance and reliability. This is a rescheduled maintenance event previously scheduled for 2026-08-25.

Expected Impact:

This maintenance is designed to be low-impact. As infrastructure components are updated, you may experience brief network interruptions or momentary delays accessing your spaces. Service will resume normal operation automatically, and no action is required on your part.

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

Thank you,
Team DigitalOcean
Aug 26, 05:42 UTC
Rescheduled: Spaces Maintenance in AMS3, FRA1 and TOR1
Completed - The scheduled maintenance has been completed.
Aug 26, 09:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 26, 06:00 UTC
Scheduled - Start: 2026-08-26 06:00 UTC
End: 2026-08-26 09:00 UTC

Hello,

During the above window, our Storage Engineering team will be performing maintenance on the Spaces service in the AMS3, FRA1 and TOR1 regions in order to improve performance and reliability. This is a rescheduled maintenance event previously scheduled for 2026-08-25.

Expected Impact:

This maintenance is designed to be low-impact. As infrastructure components are updated, you may experience brief network interruptions or momentary delays accessing your spaces. Service will resume normal operation automatically, and no action is required on your part.

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

Thank you,
Team DigitalOcean
Aug 26, 05:43 UTC
Aug 25, 2026
Cloud Control Panel and API
Resolved - Our Engineering team has confirmed all services remain stable and we will now resolve this incident. Further details on root cause and mitigation will be provided in a postmortem via this status page for users interested in learning more.

Thank you for your patience throughout this incident. If you continue to experience any issues, please reach out to Support from within your account
Aug 25, 19:04 UTC
Update - Our Engineering team has continued to monitor the health of all services and has observed no recurrence of impact over the past 12+ hours. We will continue to monitor services for a short period to confirm stability before we mark this incident resolved. We understand the impact this incident had for DigitalOcean users and we will publish a postmortem on the status page to provide further details on root cause and mitigation.
Aug 25, 16:30 UTC
Monitoring - Our Engineering team has implemented mitigation measures to address the issue impacting the DigitalOcean public API and Cloud Control Panel. We are seeing improvements, and users should now be able to access the Cloud Control Panel and use the public API normally.

We are continuing to monitor the service to ensure it remains stable and will provide further updates as more information becomes available. We appreciate your patience and understanding.
Aug 25, 00:54 UTC
Investigating - Our Engineering team is investigating a recurrence of the issue impacting the DigitalOcean public API and Cloud Control Panel. This issue does not impact our data plane (i.e. running droplets).

Users may experience difficulties accessing the Cloud Control Panel, along with elevated latency and intermittent errors when accessing the public API or Cloud Control Plane.

We are actively investigating the issue and working to restore normal service. We will continue to provide updates as more information becomes available. We apologize for the inconvenience and appreciate your patience.
Aug 24, 22:27 UTC
Monitoring - Our Engineering team has implemented mitigation measures to address the issue affecting the DigitalOcean public API and Cloud Control Panel. We are seeing requests succeed, and users should now be able to access the Cloud Control Panel and issue/receive API requests normally.

We are currently monitoring the situation to ensure that the service has returned to normal operation and remains stable. We appreciate your patience and will provide an update once the issue is fully confirmed as resolved.
Aug 24, 19:14 UTC
Update - We are continuing to investigate the issue impacting the DigitalOcean public API and Cloud Control Panel. At this time, we are seeing some improvement in latency/error rates and some users may now be able to access the Cloud Control Panel.

Serverless Inference users may currently experience 403 and 503 errors when making API requests or accessing affected services.

We will continue to provide updates as more information becomes available. We apologize for the inconvenience and appreciate your patience.
Aug 24, 18:33 UTC
Investigating - Our Engineering team is investigating an issue impacting the DigitalOcean public API and Cloud Control Panel. At this time, users will see elevated 5xx errors for all API requests, including things like creates for various products. Users may also be unable to access cloud.digitalocean.com.

We are actively investigating the root cause and will provide updates as soon as more information becomes available.

We apologize for the inconvenience and appreciate your patience.
Aug 24, 17:14 UTC
Spaces Maintenance in NYC3, SFO2 and SFO3
Completed - We are reaching out to inform you that the Spaces maintenance previously scheduled for 2026-08-26 05:30 UTC to 07:30 UTC in the NYC3, SFO2, and SFO3 regions has been cancelled.

We do not have a rescheduled date at this time. Once a new maintenance window is confirmed, we will send a follow-up notice to let you know. We apologize for any inconvenience this may cause and thank you for your patience.

If you have any questions or concerns, please reach out to us by opening a support ticket from your cloud support page: https://cloudsupport.digitalocean.com/s/createticket
Aug 25, 06:57 UTC
Scheduled - Start: 2026-08-26 05:30 UTC
End: 2026-08-26 07:30 UTC

During the above window, our Storage Engineering team will be performing maintenance on the Spaces service in the NYC3, SFO2, and SFO3 regions in order to improve performance and reliability.

Expected Impact:

This maintenance is designed to be low-impact. As infrastructure components are updated, you may experience brief network interruptions or momentary delays accessing your storage. Service will resume normal operation automatically, and no action is required on your part.

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
Aug 24, 19:16 UTC
Spaces Maintenance in AMS3, BLR1, FRA1 and TOR1
Completed - We are reaching out to inform you that the Spaces maintenance previously scheduled for 2026-08-25 05:30 UTC to 07:30 UTC in the AMS3, BLR1, FRA1 and TOR1 regions has been cancelled.

We do not have a rescheduled date at this time. Once a new maintenance window is confirmed, we will send a notice to let you know. We apologize for any inconvenience this may cause and thank you for your patience.

If you have any questions or concerns, please reach out to us by opening a support ticket from your cloud support page: https://cloudsupport.digitalocean.com/s/createticket
Aug 25, 06:32 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 25, 05:30 UTC
Scheduled - Start: 2026-08-25 05:30 UTC
End: 2026-08-25 07:30 UTC

During the above window, our Storage Engineering team will be performing maintenance on the Spaces service in the AMS3, BLR1, FRA1 and TOR1 regions in order to improve performance and reliability.

Expected Impact:

This maintenance is designed to be low-impact. As infrastructure components are updated, you may experience brief network interruptions or momentary delays accessing your spaces. Service will resume normal operation automatically, and no action is required on your part.

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
Aug 23, 18:05 UTC
Aug 24, 2026
Maintenance Window Extended in LON1, SGP1, SYD1.
Completed - The scheduled maintenance has been completed.
Aug 24, 12:00 UTC
Update - Started: 2026-08-24 05:30 UTC
End time: 2026-08-24 12:00 UTC (extended from 11:00 UTC)

The scheduled maintenance being performed by our Storage Engineering team on the Spaces service is progressing as planned.

The maintenance in the SGP1 region has been completed successfully. Work and post-upgrade validation are still in progress in the LON1 and SYD1 regions, and approximately one additional hour is required to complete the remaining work.

We are therefore extending the maintenance window from 11:00 UTC to 12:00 UTC.

Expected Impact:

The maintenance remains low-impact. Customers may continue to experience brief network interruptions or momentary delays when accessing Spaces in the affected regions while the remaining work is completed. Service will resume normal operation automatically once the maintenance concludes, and no action is required.

We will provide another update once the maintenance is fully completed.
Aug 24, 10:41 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 24, 08:30 UTC
Scheduled - Started: 2026-08-24 05:30 UTC
End time: 2026-08-24 11:00 UTC (extended from 07:30 UTC)

The maintenance our Storage Engineering team is performing on the Spaces service in the LON1, SGP1 and SYD1 regions is currently in progress and we are extending the window to complete the planned work and post-upgrade validation. The window will now run until 11:00 UTC instead of 07:30 UTC.

Expected Impact:

This maintenance is designed to be low-impact. As infrastructure components are updated, you may experience brief network interruptions or momentary delays accessing your spaces. This may continue until the maintenance concludes at 11:00 UTC. Service will resume normal operation automatically, and no action is required on your part.

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.
Aug 24, 08:27 UTC
Spaces Maintenance in LON1, SGP1 and SYD1
Completed - The scheduled maintenance has been completed.
Aug 24, 07:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 24, 05:30 UTC
Scheduled - Start: 2026-08-24 05:30 UTC
End: 2026-08-24 07:30 UTC

During the above window, our Storage Engineering team will be performing maintenance on the Spaces service in the LON1, SGP1 and SYD1 regions in order to improve performance and reliability.

Expected Impact:

This maintenance is designed to be low-impact. As infrastructure components are updated, you may experience brief network interruptions or momentary delays accessing your Spaces. Service will resume normal operation automatically, and no action is required on your part.

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
Aug 22, 05:43 UTC
Aug 23, 2026
Managed Databases Creation
Resolved - Our Engineering team has resolved the issue preventing cluster creation on Managed Databases in the NYC3 and NYC1 regions. Customers can now create new Managed Databases Clusters normally.

Our Engineering team has monitored the environment to ensure stability. We sincerely apologize for any inconvenience this disruption may have caused to your operations. If you continue to experience issues, please open a ticket with our Support team: https://cloudsupport.digitalocean.com/s/
Aug 23, 14:33 UTC
Monitoring - Our Engineering team has implemented the necessary fixes affecting Managed Database cluster creation in the NYC3 and NYC1 regions. Users should now be able to create new Managed Database clusters.  

We are currently monitoring the situation to ensure that the service has returned to normal operation and remains stable. We appreciate your patience and will provide an update once the issue is fully confirmed as resolved.
Aug 23, 11:30 UTC
Update - We continue to investigate an issue affecting DigitalOcean Managed Databases cluster creation across multiple regions.

During this time, users may experience errors when creating Managed Database clusters via the Cloud Control Panel or API.

Our engineering team is implementing a mitigation and working to restore normal provisioning. We will provide another update as soon as more information is available.
Aug 23, 07:06 UTC
Investigating - Our Engineering team is investigating an issue with our Managed Database product. At this time, users may experience errors while creating clusters, both via Cloud Control Panel and API requests.

We apologize for the inconvenience and will share an update once we have more information.
Aug 23, 05:11 UTC
Aug 22, 2026

No incidents reported.

Aug 21, 2026
Container Registry and Spaces Accessibility
Resolved - Our Engineering team has confirmed that the issue impacting Container Registry and Spaces accessibility has been resolved.

Spaces accessibility via the Cloud Control Panel is now restored, and pushing and pulling container images is succeeding as expected. Customers who previously encountered these issues should now be able to access Spaces and deploy their container images without further issues.

If you continue to experience any problems, please open a ticket with our support team. Thank you for your patience, and we apologize for any inconvenience.
Aug 21, 14:52 UTC
Monitoring - Our Engineering team has identified the issue affecting Container Registry and Spaces buckets, and a fix has been applied.

Spaces accessibility via the Cloud Control Panel should now be restored, and pushing and pulling container images should be back to normal.

We are continuing to monitor the results to ensure the issue has been fully resolved and will provide another update once we've confirmed normal service has been restored.
Aug 21, 13:06 UTC
Investigating - Our Engineering team is currently investigating reports of an issue affecting Container Registry and Spaces buckets in some regions.

During this time, customers may experience failures when pushing or pulling container images. Additionally, customers may experience issues accessing Spaces via the Cloud Control Panel, where the page may display "Looks like something went wrong…"

Our Engineering team is actively investigating the issue and treating it with priority. We will provide another update as soon as more information becomes available.
Aug 21, 12:59 UTC
Aug 20, 2026

No incidents reported.

Aug 19, 2026
Major Service Interruption in MKC1
Resolved - Our Engineering team has confirmed the regional control plane is healthy and CPU Droplets, Managed databases, Load balancers, Block storage, Kubernetes (DOKS) and Spaces are operating normally.

GPU Droplets continue to be impacted and our teams are working to restore all nodes. We will communicate with GPU Droplet customers separately via Slack and email with more information and regular updates.

Thank you for your patience throughout this incident. If you continue to experience any issues, please open a support ticket from within your account.
Aug 19, 19:34 UTC
Monitoring - At this time, the regional control plane is fully healthy. CPU Droplets, Managed databases, Load balancers, Block storage and Spaces are operating normally. Droplet create, resize and other management operations are working. Kubernetes (DOKS) control planes are reachable.

Our teams are continuing to work with the facility to restore all equipment. GPU Droplets in MKC1 remain offline or unreachable. DOKS GPU worker nodes may remain NotReady, and GPU-backed inference endpoints in this region may be unavailable.

We will monitor the regional control plane for a short time and then resolve this incident. GPU customers will receive personalized updates with more information in lieu of this status page.

If you have questions about your affected resources, contact support and reference this incident.
Aug 19, 18:59 UTC
Update - Our Engineering team continues to work on the issue affecting the MKC1 region. We are actively working to restore connectivity and bring the impacted nodes back online.
We will provide another update as soon as we have more information.
Aug 19, 15:28 UTC
Identified - We have identified the root cause of the issue in the MKC1 region affecting multiple racks and nodes. Our Engineering team is actively implementing remediation steps to restore connectivity and bring the impacted nodes back online.
During this time, customers may continue to experience disruptions to GPU workloads and Serverless Inference. Kubernetes (DOKS) worker nodes may also remain in a NotReady state, and customers may be unable to reach Kubernetes API endpoints or perform cluster-management operations in affected clusters. We will provide another update as soon as we have more information.
Aug 19, 12:22 UTC
Investigating - Our Engineering team is currently investigating an issue in the MKC1 region affecting multiple racks and nodes.

During this time, customers may experience disruptions to GPU workloads, and Kubernetes (DOKS) worker nodes may enter a NotReady state.

Our team is actively working to restore connectivity and bring impacted nodes back online. If you continue to experience issues, please open a support ticket from within your account.
Aug 19, 11:10 UTC
Aug 18, 2026

No incidents reported.

Aug 17, 2026

No incidents reported.

Aug 16, 2026

No incidents reported.

Aug 15, 2026

No incidents reported.

Aug 14, 2026

No incidents reported.

Aug 13, 2026
Volume Attach/Detach events in FRA1
Resolved - Between Aug 13, 09:50 UTC and 14:30 UTC, customers in the FRA1 region experienced an issue affecting Block Storage Volumes attachment and detachment operations on Droplets and Managed Kubernetes clusters.

During this window, customers may have encountered delays or been unable to attach and detach Block Storage Volumes from their resources.

Block Storage Volumes attachment and detachment operations now appear to be functioning normally, and customers should no longer experience issues with these operations. For Managed Kubernetes clusters specifically, some residual cleanup of affected volume attachments may still be needed, and our team is actively working through this.

We apologize for any inconvenience this may have caused. If you continue to experience issues with Block Storage Volumes operations, please don't hesitate to open a support ticket for further investigation. Our team will be happy to assist you.
Aug 13, 14:59 UTC
← Incident History Powered by Atlassian Statuspage
DigitalOcean Home API Docs Community