DigitalOcean Outage History

DigitalOcean is up right now

There were 30 DigitalOcean outages since February 3, 2026 totaling 15h 16m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.digitalocean.com

Notice February 16, 2026

Spaces Availability in NYC3

Detected by Pingoru
Feb 16, 2026, 07:36 AM UTC
Resolved
Feb 16, 2026, 10:58 AM UTC
Duration
3h 21m
Affected: NYC3NYC3
Timeline · 2 updates
  1. monitoring Feb 16, 2026, 07:36 AM UTC

    Between 5:34 and 6:32 UTC, our Engineering team identified the issue that was impacting the availability of Spaces and the Container Registry in the NYC3 region. A fix has been implemented to resolve the issue. During this time users may have experienced errors while interacting with Spaces. Additionally, CRUD operations (create, read, update, delete) within the Container Registry may have failed or returned errors during this time. We are now monitoring the platform to ensure services remain stable and operating as expected. We will provide a final update once the issue is fully resolved. If you continue to experience any issues, please contact our Support team.

  2. resolved Feb 16, 2026, 10:58 AM UTC

    Our Engineering team has confirmed that the issue impacting the availability of Spaces and the Container Registry in the NYC3 region has been fully resolved. A fix was implemented, and services have been restored. All operations are now succeeding normally. If you experience any further issues, please contact Support by creating a Support ticket from within your account. Thank you for your patience while we worked to resolve this issue.

Read the full incident report →

Notice February 16, 2026

Droplet Limit Increase Feature

Detected by Pingoru
Feb 16, 2026, 06:38 AM UTC
Resolved
Feb 16, 2026, 09:24 AM UTC
Duration
2h 46m
Timeline · 3 updates
  1. investigating Feb 16, 2026, 06:38 AM UTC

    Our Engineering team is currently investigating an issue affecting the Droplet limit increase feature within the Cloud Control Panel. At this time requests to increase Droplet limits submitted through the Control Panel are not being processed. Customer submissions to increase limits are not generating support tickets as expected. We are actively working to identify the root cause and restore normal functionality as quickly as possible. If you urgently require a Droplet limit increase, please contact Support directly by creating a Support ticket from within your account.

  2. monitoring Feb 16, 2026, 08:37 AM UTC

    The issue affecting the Droplet limit increase feature within the Cloud Control Panel has been identified and a fix has been implemented. Requests submitted through the Control Panel are now generating Support tickets as expected. Our team is continuing to monitor the system to ensure full functionality and stability. If you experience any further issues with Droplet limit increase requests, please contact Support directly by creating a Support ticket from within your account.

  3. resolved Feb 16, 2026, 09:24 AM UTC

    Our Engineering team has confirmed that the issue affecting the Droplet limit increase feature within the Cloud Control Panel has been fully resolved. Requests to increase Droplet limits submitted through the Control Panel are now being processed correctly, and Support tickets are being generated as expected. If you experience any further issues, please contact Support by creating a Support ticket from within your account. Thank you for your patience while we worked to resolve this issue.

Read the full incident report →

Minor February 12, 2026

MongoDB Cluster Creation

Detected by Pingoru
Feb 12, 2026, 05:42 AM UTC
Resolved
Feb 12, 2026, 12:06 PM UTC
Duration
6h 24m
Affected: Global
Timeline · 5 updates
  1. investigating Feb 12, 2026, 05:42 AM UTC

    Our Engineering team is investigating an issue with all events for MongoDB clusters in all of our regions. During this time, users may face issues with creation, fork and resize operations in the MongoDB clusters. We apologize for the inconvenience and will share an update once we have more information.

  2. investigating Feb 12, 2026, 07:34 AM UTC

    Our engineering team continues to investigate the issue with create, fork and resize events failure for MongoDB clusters in all of our regions. We appreciate your patience and will post an update as soon as additional information is available.

  3. identified Feb 12, 2026, 09:04 AM UTC

    Our engineering team has identified the cause of the issue with create, fork and resize events failure for MongoDB clusters in all of our regions and is actively working on a fix. We will post an update as soon as additional information is available.

  4. monitoring Feb 12, 2026, 09:50 AM UTC

    Our Engineering team has implemented a fix to resolve the issue with MongoDB clusters 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.

  5. resolved Feb 12, 2026, 12:06 PM UTC

    Our Engineering team has confirmed the full resolution of the issue with MongoDB Clusters. Thank you for your patience, and we apologize for any inconvenience. If you continue to experience any issues, please open a Support ticket right away.

Read the full incident report →

Minor February 11, 2026

App platform seeing delays in deployments across all regions.

Detected by Pingoru
Feb 11, 2026, 11:50 AM UTC
Resolved
Feb 11, 2026, 01:08 PM UTC
Duration
1h 18m
Affected: Global
Timeline · 3 updates
  1. investigating Feb 11, 2026, 11:50 AM UTC

    Our engineers are currently investigating an issue impacting new App Platform deployments. During this time, some users may experience delay when creating new App Platform apps. Existing apps are not affected and should continue to function normally. We apologize for any inconvenience, and we'll share more information as it becomes available.

  2. monitoring Feb 11, 2026, 12:03 PM UTC

    Our team has implemented a fix to address the issue causing delays in App Platform deployments. We are actively monitoring the situation to ensure overall stability. Users may already notice improvements while deploying apps. We appreciate your patience throughout the process and will provide a further update once the issue is fully confirmed to be resolved.

  3. resolved Feb 11, 2026, 01:08 PM UTC

    The issue impacting delays in App Platform deployments has been confirmed to be resolved. Between approximately 08:52 UTC & 13:01 UTC, users may have noticed delays while creating or updating apps, or may have encountered failed deployments. For failed deployments, please trigger a redeploy, which should successfully resolve the issue. We confirmed that the service is functioning as expected. Once again, we sincerely apologize for the inconvenience caused and appreciate your understanding. However, if you continue to experience any issues, please don't hesitate to raise a support ticket for further investigation. We’ll be happy to assist you.

Read the full incident report →

Minor February 3, 2026

Cloud Control Panel

Detected by Pingoru
Feb 03, 2026, 05:27 PM UTC
Resolved
Feb 03, 2026, 06:53 PM UTC
Duration
1h 26m
Affected: APICloud Control Panel
Timeline · 5 updates
  1. investigating Feb 03, 2026, 05:27 PM UTC

    Our Engineering team is investigating an issue impacting our Cloud Control Panel and API. Users attempting to make API requests could see 5xx errors and users attempting to access the Cloud Control Panel may see gateway timeouts or page timeouts. We apologize for the inconvenience and will share an update once we have more information.

  2. investigating Feb 03, 2026, 05:32 PM UTC

    Our Engineering team is investigating an issue impacting our Cloud Control Panel and API. Users attempting to make API requests could see 5xx errors and users attempting to access the Cloud Control Panel may see gateway timeouts or page timeouts. We apologize for the inconvenience and will share an update once we have more information.

  3. identified Feb 03, 2026, 05:51 PM UTC

    Our Engineering team has identified the cause of the issue impacting the Cloud Control Panel and API and is actively working on deploying a fix. At this time, users will continue to see timeouts/5xx errors, but may intermittently see requests succeeding. We will post further updates as soon as the fix is deployed or there is more information to share.

  4. monitoring Feb 03, 2026, 06:03 PM UTC

    Our Engineering team has implemented a fix for the timeouts affecting the Cloud Control Panel and API, and is currently monitoring the situation. Services have recovered, and users should no longer experience 5xx errors when using the API or gateway timeouts when accessing the Cloud Control Panel. We will continue to monitor the situation to ensure that all services are stable and functioning as expected. We will post an update as soon as the issue is fully resolved.

  5. resolved Feb 03, 2026, 06:53 PM UTC

    As of 17:55 UTC, our Engineering team has resolved the timeouts affecting the Cloud Control Panel and API. The issue was caused by a temporary overload on our infrastructure, resulting in 5xx errors for API requests and gateway timeouts for Cloud Control Panel users. If you continue to experience any problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused and appreciate your patience and understanding.

Read the full incident report →

Looking to track DigitalOcean downtime and outages?

Pingoru polls DigitalOcean's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when DigitalOcean reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track DigitalOcean alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring DigitalOcean for free

5 free monitors · No credit card required