DigitalOcean Outage History

DigitalOcean is up right now

DigitalOcean had 60 outages in the last 2 years totaling 47h 24m of downtime — averaging 2.5 incidents per month.

There were 60 DigitalOcean outages since November 8, 2025 totaling 47h 24m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.digitalocean.com

Minor December 5, 2025

Control Panel Access

Detected by Pingoru
Dec 05, 2025, 09:23 AM UTC
Resolved
Dec 05, 2025, 10:06 AM UTC
Duration
43m
Affected: APIGlobalGlobalGlobalCloud Control Panel
Timeline · 4 updates
  1. monitoring Dec 05, 2025, 09:23 AM UTC

    Our Engineering team has been made aware of an issue with an upstream provider that was affecting the Control Panel and API and has deployed a fix to resolve it. Users may have experienced issues signing in or accessing resources through the Control Panel. We are monitoring the situation closely and will share an update once the issue is resolved completely.

  2. monitoring Dec 05, 2025, 09:23 AM UTC

    We are continuing to monitor for any further issues.

  3. monitoring Dec 05, 2025, 09:28 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved Dec 05, 2025, 10:06 AM UTC

    Our Engineering team has confirmed the full resolution of this issue. From approximately 08:51 UTC – 09:12 UTC, users may have experienced difficulties signing in or accessing resources through the Control Panel and API due to an upstream provider issue. The upstream provider has fixed the issue, and all services are now functioning normally. If you continue to experience problems, please open a ticket with our support team. Thank you for your patience and we apologize for any inconvenience.

Read the full incident report →

Minor December 4, 2025

Degradation in Managed Databases

Detected by Pingoru
Dec 04, 2025, 06:03 PM UTC
Resolved
Dec 04, 2025, 10:04 PM UTC
Duration
4h
Affected: Global
Timeline · 3 updates
  1. investigating Dec 04, 2025, 06:03 PM UTC

    As of 16:34 UTC, our Engineering team is investigating reports of errors and timeouts on control plane operations for Managed Databases. The issue is affecting multiple database engines, including PostgreSQL, MySQL, OpenSearch, Redis, and Kafka. Users may experience errors or timeouts when attempting to list backups, through both the API and UI. We want to emphasize that this issue does not currently appear to be impacting the data plane, and databases should continue to be accessible and functional. Our team is working to determine the root cause of the issue and will share an update once we have more information. We apologize for the inconvenience and appreciate your patience as we work to resolve this incident. We will provide further updates as soon as more information is available.

  2. monitoring Dec 04, 2025, 09:22 PM UTC

    As of 19:47 UTC, our Engineering team has implemented a fix for the errors on Managed Database list backup operations, which was related to a dependency issue. The situation is currently improving, and we are seeing a reduction in error rates. The impact was limited to list backup operations for PostgreSQL, MySQL, OpenSearch, Redis, and Kafka engines, where users may have experienced errors when attempting to retrieve a list of backups through both the API and UI. We are now monitoring the situation to ensure that the fix is fully effective and that all operations are functioning normally. Users should no longer experience errors when listing backups, and all other control plane operations, such as creating, updating, or deleting databases, should continue to function normally. We will continue to monitor the situation to ensure that the issue is fully resolved. We apologize for the disruption and appreciate your patience.

  3. resolved Dec 04, 2025, 10:04 PM UTC

    From As of 16:34 to 19:47 UTC, may have encountered errors listing backup operations for their PostgreSQL, MySQL, OpenSearch, Redis and Kafa clusters through the API and UI. Our Engineering team has confirmed full resolution of the issue, users should no longer experience issues with listing backup operations. Thank you for your patience, and we apologize for the inconvenience. If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel.

Read the full incident report →

Notice December 4, 2025

Gradient AI Platform – Service Degradation

Detected by Pingoru
Dec 04, 2025, 02:25 PM UTC
Resolved
Dec 04, 2025, 11:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Dec 04, 2025, 02:25 PM UTC

    During the timeframe 06:24 UTC – 13:45 UTC, the Gradient AI platform experienced a period of degraded functionality affecting a limited set of features. While the platform remained accessible, the below components did not perform as expected. Impacted Areas: - Gradient Agent Evaluations - Agent trace visibility - Access management for traces - Agent deletion for agents with traces enabled Our Engineering team identified the underlying cause and restored full functionality across all affected components. The platform has remained stable since resolution, and monitoring confirms normal performance.

Read the full incident report →

Minor December 2, 2025

Guardrails Service Disruption Impacting Customers

Detected by Pingoru
Dec 02, 2025, 08:55 PM UTC
Resolved
Dec 03, 2025, 03:45 PM UTC
Duration
18h 50m
Affected: Agent Runtime
Timeline · 4 updates
  1. identified Dec 02, 2025, 08:55 PM UTC

    As of 20:07 UTC on December 2, 2025, our Engineering team has detected increased guardrail latency which may produce long response times for agents with attached guardrails. Engineering is working on a fix. We apologize for the inconvenience and will share an update once we have more information. Thank you for your patience and understanding as we work to resolve this issue.

  2. investigating Dec 02, 2025, 09:47 PM UTC

    Our Engineering team is currently investigating increased guardrail latency, which may cause long response times for agents with attached guardrails. We apologize for the inconvenience and will share an update once we have more information. Thank you for your patience and understanding as we work to resolve this issue.

  3. monitoring Dec 02, 2025, 11:21 PM UTC

    Our Engineering team has implemented a fix that has significantly reduced the impact of the issue, largely mitigating the outage. Although the situation has improved, some users may still experience intermittent latency issues. We are closely monitoring the results and will continue to work towards full resolution. We will provide another update once we have confirmed the issue is fully resolved.

  4. resolved Dec 03, 2025, 09:45 PM UTC

    Our Engineering team has fully implemented and confirmed the effectiveness of the fix for the increased guardrail latency. System performance has returned to normal, and all affected services are operating as expected. We have observed stable metrics during extended monitoring and have not detected any further latency or interruptions. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.

Read the full incident report →

Notice November 24, 2025

Managed Databases

Detected by Pingoru
Nov 24, 2025, 08:19 PM UTC
Resolved
Nov 24, 2025, 08:19 PM UTC
Duration
—
Affected: Global
Timeline · 1 update
  1. resolved Nov 24, 2025, 08:19 PM UTC

    From 18:55 to 19:32 UTC, Our Engineering team observed an issue with all control plane operations (Create, Scale, Fork, etc ) for all non-Mongo Managed Database clusters. During this time, users encountered long running requests made either through the Cloud Console UI or API, including provisioning new clusters, listing clusters, etc. Our team has fully resolved the issues as of 19:32 UTC All services for non-Mongo Managed Databases should now be operating normally. If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel. We apologize for any inconvenience caused.

Read the full incident report →

Notice November 17, 2025

Block Storage Volumes in NYC1 and AMS3

Detected by Pingoru
Nov 17, 2025, 07:26 PM UTC
Resolved
Nov 17, 2025, 07:26 PM UTC
Duration
—
Affected: AMS3NYC1
Timeline · 1 update
  1. resolved Nov 17, 2025, 07:26 PM UTC

    From 16:59 to 17:34 UTC, our Engineering team observed an issue with block storage volumes in the NYC1 and AMS3 regions. During this time, users may have experienced failures when attempting create, snapshot, attach, detach, or resize volumes. There was no impact to performance or availability of existing volumes. Our team has fully resolved the issues as of 17:34 UTC and volumes should be operating normally. If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel. We apologize for any inconvenience caused.

Read the full incident report →

Minor November 16, 2025

Creation Events Failing for Spaces, App Platform, DOCR

Detected by Pingoru
Nov 16, 2025, 08:31 AM UTC
Resolved
Nov 16, 2025, 11:05 AM UTC
Duration
2h 34m
Affected: GlobalGlobalGlobalGlobal
Timeline · 3 updates
  1. investigating Nov 16, 2025, 08:31 AM UTC

    Our engineering team is investigating an issue with failed create events with their Spaces, App Platform, and DOCR services. At this time, users may experience errors when creating Spaces, App Platform, DOCR services. We apologize for the inconvenience and will share an update once we have more information.

  2. monitoring Nov 16, 2025, 10:02 AM UTC

    Our Engineering team has implemented a fix to resolve the issue with failed create events with their Spaces, App Platform, and DOCR services and at this time, services should be functioning as expected. We're monitoring the situation and will post a final update once we confirm this is fully resolved.

  3. resolved Nov 16, 2025, 11:05 AM UTC

    Our Engineering team has confirmed full resolution of the issue with failed create events with their Spaces, App Platform, and DOCR services. From 06:15 UTC AM to 09:53 AM UTC, the Spaces, App Platform, and DOCR services were impacted and have since been restored to normal operation. If you continue to experience problems, please open a ticket with our support team. Thank you for your patience throughout this incident!

Read the full incident report →