Normal view

Received — 9 May 2026 DigitalOcean Status - Incident History

Control Panel Errors - Unable to Enable 2FA and Google/GitHub

May 9, 14:42 UTC
Resolved - Between 5:35 and 14:25 UTC today, our Engineering team identified an issue that prevents enabling Two-Factor Authentication (2FA) and Google/GitHub authentication through the Control Panel. During this period, users might have encountered issues while enabling authentication methods and accessing teams with secure sign-in enabled.

Our team has taken appropriate measures to address the issue. We can confirm that service has been restored and is now functioning normally.

We regret the inconvenience caused. However, if you continue to experience any issues, please create a support ticket for further analysis.

May 9, 13:51 UTC
Monitoring - Our Engineering team has implemented necessary changes to address the issue affecting the ability to enable Two-Factor Authentication (2FA) and Google/GitHub authentication through the Control Panel. Our team is currently monitoring the situation to ensure stability.

We appreciate your patience and will provide an update once the issue is fully confirmed as resolved.

May 9, 11:15 UTC
Investigating - Our Engineering team is investigating an issue affecting the ability to enable Two-Factor Authentication (2FA) and Google/GitHub authentication through the Control Panel. During this time, users may encounter errors while enabling these authentication methods and could also experience issues accessing teams with secure sign-in enabled.

We apologize for the inconvenience and will provide an update as soon as more information becomes available.

Received — 8 May 2026 DigitalOcean Status - Incident History

Let's Encrypt Outage Affecting Certificate Issuance and Managed Databases Operations

May 8, 21:54 UTC
Resolved - The upstream outage with Let's Encrypt has been resolved. Customers should now be able to issue Let's Encrypt certificates for Spaces, Load Balancers, and App Platform Custom Domains. Our Engineering team has also confirmed that stuck or delayed actions with Mongo, Advanced PG, and Advanced MySQL databases should complete normally now.

We appreciate your patience. If you continue to experience any issues, please open a support ticket from within your account.

May 8, 20:46 UTC
Identified - Our Engineering team is aware of an upstream outage with Let's Encrypt (see https://letsencrypt.status.io/) which impacts the following services:

- Inability to create new Let's Encrypt certificates for Spaces, Load Balancers, and App Platform Custom Domains
- Stuck or delayed creates/forks/restores on Mongo, PG, and MySQL databases.

Please note that operations related to Managed Databases and App Platform Custom Domains will automatically retry and should complete successfully once the upstream outage is resolved.

We'll continue to monitor this situation and provide updates. We apologize for the inconvenience.

Multiple Services in NYC2

May 8, 19:59 UTC
Resolved - Our engineering team has resolved the issue with multiple services in NYC2 region, and all services should now be operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience and thank you for your patience.

May 8, 19:53 UTC
Update - We are continuing to monitor for any further issues.

May 8, 19:21 UTC
Monitoring - Our Engineering team has identified the issue and implemented a fix to resolve the issues with multiple services, and is monitoring the situation. We will post an update as soon as the issue is fully resolved.

May 8, 18:01 UTC
Investigating - We are currently investigating an issue affecting multiple services in our NYC2 region. Our engineering team is aware of the situation and is working to identify the root cause and restore full connectivity as quickly as possible.

Users with resources in the NYC2 region may experience issues with Droplet connectivity, API requests, or other services.

We will provide additional updates as more information becomes available. We apologize for any inconvenience this may cause.

Received — 7 May 2026 DigitalOcean Status - Incident History

Core Infrastructure Maintenance May 7, 2026, 15:00 UTC

May 7, 21:00 UTC
Completed - The scheduled maintenance has been completed.

May 7, 15:20 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

May 7, 15:13 UTC
Scheduled - Start: 2026-05-07 15:00 UTC
End: 2026-05-07 21:00 UTC

Our Engineering team is 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 brief periods of increased latency 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

Received — 2 May 2026 DigitalOcean Status - Incident History

Core Infrastructure Maintenance May 4th, 2026, 13:00 UTC

May 4, 21:01 UTC
Completed - The scheduled maintenance has been completed.

May 4, 13:01 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

May 2, 13:25 UTC
Scheduled - Start: 2026-05-04 13:00 UTC
End: 2026-05-04 21:00 UTC

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 brief periods of increased latency 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

SFO2 Network Maintenance

May 4, 15:00 UTC
Completed - The scheduled maintenance has been completed.

May 4, 13:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

May 2, 12:39 UTC
Scheduled - Start: 2026-05-04 13:00 UTC
End: 2026-05-04 15: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 SFO2 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 issue, please send us a ticket from your cloud support page. https://cloudsupport.digitalocean.com/s/createticket

Core Infrastructure Maintenance May 4, 2026, 13:00 UTC

May 4, 21:00 UTC
Completed - The scheduled maintenance has been completed.

May 4, 13:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

May 2, 09:15 UTC
Scheduled - Start: 2026-05-04 13:00 UTC
End: 2025-05-04 21:00 UTC

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 brief periods of increased latency 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

Received — 28 April 2026 DigitalOcean Status - Incident History

FRA1 Network Maintenance

Apr 30, 19:00 UTC
Completed - The scheduled maintenance has been completed.

Apr 30, 16:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Apr 28, 16:19 UTC
Scheduled - Start: Apr 30, 2026, 16:00 UTC to
End: Apr 30, 2026, 19: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 FRA1 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 issue, please send us a ticket from your cloud support page. https://cloudsupport.digitalocean.com/s/createticket

Elevated 5xx “context canceled” errors impacting serverless inference

Apr 28, 19:33 UTC
Resolved - All services are operating normally. We will continue to monitor the system to ensure ongoing reliability.

Thank you for your patience while we worked to resolve this issue.

Apr 28, 19:00 UTC
Monitoring - Service for Serverless Inference has been restored.
We’ve implemented tighter rate limits to help prevent recurrence and are closely monitoring system performance. Some users may still experience intermittent latency as we complete final stabilization efforts.
Our team remains actively engaged to ensure full recovery. We appreciate your patience and will provide further updates as needed.

Apr 28, 15:59 UTC
Identified - We have identified an issue affecting our service and are currently working to implement a fix. Our team is actively investigating and taking the necessary steps to restore normal operations as quickly as possible.

We appreciate your patience and will provide updates as soon as more information becomes available.

Apr 28, 13:45 UTC
Investigating - Serverless inference customers are experiencing elevated 5xx errors, including “context canceled” responses. This may result in intermittent request failures. Our team is actively investigating and will provide updates as more information becomes available.

SFO2 Network Maintenance

Apr 30, 06:43 UTC
Completed - During the dry-run for the scheduled SFO2 Network Maintenance , our team identified some potential risks that need to be addressed to ensure a smoother and safer implementation. As a result, we are cancelling the current maintenance window and will be rescheduling it to 2026-05-04 13:00-15:00 UTC.

Thank you for your understanding and patience as we work to improve performance and scalability.

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

Apr 28, 13:16 UTC
Scheduled - Start: Apr 30, 2026, 13:00 UTC
End: Apr 30, 2026, 15: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 SFO2 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 issue, please send us a ticket from your cloud support page. https://cloudsupport.digitalocean.com/s/createticket

NYC1 Network Maintenance

Apr 30, 12:00 UTC
Completed - The scheduled maintenance has been completed.

Apr 30, 10:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Apr 28, 10:14 UTC
Scheduled - Start: Apr 30, 2026, 10:00 UTC
End: Apr 30, 2026, 12:00 UTC

Hello,

During the above window, our Networking team will be making changes to the core networking infrastructure to improve performance and scalability in the NYC1 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 issue, please send us a ticket from your cloud support page. https://cloudsupport.digitalocean.com/s/createticket

Thank you,
Team DigitalOcean

Received — 27 April 2026 DigitalOcean Status - Incident History

Serverless Inference - Intermittent Rate Limiting Affecting Some Customers Using Anthropic Models

Apr 27, 11:37 UTC
Resolved - The issue is resolved, and service is operating normally.

Apr 27, 11:07 UTC
Monitoring - We identified the cause of intermittent HTTP 429 responses affecting some customers using Anthropic models on DigitalOcean Serverless Inference and applied a mitigation. Service has recovered, and we are monitoring stability.

Apr 27, 10:38 UTC
Investigating - We are investigating an issue affecting some customers using DigitalOcean Serverless Inference with Anthropic models. Over the last two hours, impacted customers may have experienced intermittent request failures, including HTTP 429 responses, on some Anthropic model requests. Our engineering team is actively investigating the issue. We apologize for the inconvenience and will share another update as soon as more information is available.

Core Infrastructure Maintenance Apr 29, 2026, 13:00 UTC

Apr 29, 15:29 UTC
Completed - During the dry-run for the scheduled Core Infrastructure Maintenance, our team identified some potential risks that need to be addressed to ensure a smoother and safer implementation. As a result, we are cancelling the current maintenance window and will be rescheduling it to 2026-05-04 13:00-21:00 UTC.

Thank you for your understanding and patience as we work to improve performance and scalability.

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

Apr 29, 13:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Apr 27, 09:35 UTC
Scheduled - Start: 2026-04-29 13:00 UTC
End: 2026-04-29 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 brief periods of increased latency 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

Received — 23 April 2026 DigitalOcean Status - Incident History

Intermittent errors impacting some Serverless Inference models in ATL1

Apr 23, 23:51 UTC
Resolved - This incident has been resolved.

Apr 23, 22:26 UTC
Investigating - As of 21:53 UTC, our Engineering team is investigating reports of increased internal errors for models Llama 3.3 70B, GPT OSS 120B, GPT OSS 20B, Qwen3 32B and Deepseek R1 70B hosted in the ATL1 region, impacting Serverless Inference. At this point, users with models hosted in ATL1 may experience intermittent errors when using Serverless Inference. We apologize for the inconvenience and will share an update once we have more information.

App Platform Deployments

Apr 23, 10:09 UTC
Resolved - Our Engineering team has confirmed that the issue impacting App Platform deployments and Kubernetes (DOKS) nodes has been fully resolved at 09:22 UTC. Users may already notice improvements while deploying apps and DOKS nodes.

All App Platform deployments are now succeeding as expected. Customers who previously encountered build failures should now be able to deploy their applications 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.

Apr 23, 09:52 UTC
Monitoring - Our Engineering team has implemented a fix to address the issue causing in App Platform deployments and Kubernetes (DOKS) nodes. We are actively monitoring the situation to ensure overall stability.
Users may already notice improvements while deploying apps and DOKS nodes. We appreciate your patience throughout the process and will provide a further update once the issue is fully confirmed to be resolved.

Apr 23, 08:31 UTC
Update - Our Engineering team is currently investigating reports of build failures on App Platform. During this time, some users may encounter errors while building their applications, which may result in failed deployments.
In addition, we are observing an issue where Kubernetes (DOKS) nodes are being marked as unhealthy by load balancers, which may impact traffic routing for affected services.
Our Engineering team is actively working to resolve these issues and will share an update as soon as more information becomes available.
We apologize for the inconvenience this may be causing and appreciate your patience.

Apr 23, 08:08 UTC
Investigating - Our Engineering team is currently investigating reports of build failures on App Platform. Users may experience errors when attempting to build their applications, resulting in failed deployments.

Our Engineering team is working to fix the issue and will share an update once we have more information.

We apologize for the inconvenience this issue may be causing and appreciate your patience as we work to resolve it.

Cloud UI for Managed Kubernetes

Apr 23, 08:46 UTC
Resolved - Our Engineering team has confirmed full resolution of the issue with Cloud UI for Managed Kubernetes at 09:19 UTC.

All the services should be functioning as expected.

If you continue to experience problems, please open a ticket with our support team. Thank you for your patience throughout this incident!

Apr 23, 07:52 UTC
Update - Our Engineering team is currently investigating an issue impacting the Managed Kubernetes UI across all regions. During this time, users with a Member role may experience the Kubernetes UI page not loading in the cloud console.
As a workaround, the DigitalOcean API and doctl (CLI) continue to function normally, and you can use them to manage your Kubernetes resources in the meantime.
We apologize for the inconvenience and will share more information as soon as it becomes available

Apr 23, 07:14 UTC
Update - Our Engineering team is currently investigating an issue impacting the Create Managed Kubernetes UI across all regions. During this time, users with a Member role may experience the Kubernetes UI page not loading in the cloud console.
As a workaround, the DigitalOcean API and doctl (CLI) continue to function normally, and you can use them to manage your Kubernetes resources in the meantime.
We apologize for the inconvenience and will share more information as soon as it becomes available.

Apr 23, 07:01 UTC
Investigating - Our Engineering team is currently investigating an issue impacting Managed Kubernetes UI across all regions. During this time, some users may experience the Kubernetes UI page not loading in DigitalOcean Onboarding.

We apologize for the inconvenience and will share more information as soon as it's available.

Received — 22 April 2026 DigitalOcean Status - Incident History

Cloud Control Panel and API

Apr 22, 11:47 UTC
Resolved - Our Engineering team has resolved the issue that was impacting the DigitalOcean API and the Cloud Control Panel. The system is now operating normally.

During the incident, users may have experienced difficulties accessing droplets, viewing the Droplets page, or performing CRUD (Create, Read, Update, Delete) operations via the API. We have verified that the issue has been fully resolved.

We apologize for the inconvenience this may have caused. If you continue to experience any issues, please submit a support ticket through the Cloud Control Panel so our team can assist you further.

Apr 22, 11:25 UTC
Monitoring - Our Engineering team has implemented a fix for the issue affecting the DigitalOcean API and the Cloud Control Panel. We are now actively monitoring the system to ensure full stability and will provide a final update once the issue is completely resolved.

We sincerely appreciate your patience and understanding as we work to restore normal service.

Apr 22, 11:06 UTC
Investigating - Our Engineering team is currently investigating an issue affecting the Cloud Control Panel and API. During this time, API requests to create, destroy, or trigger events on droplets may not succeed. Additionally, the Droplets page in the Cloud Control Panel may not load properly, and users could experience issues while reviewing the droplet listing.

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

We apologize for the inconvenience and appreciate your patience.

Received — 17 April 2026 DigitalOcean Status - Incident History

DNS Resolution for .co TLD

Apr 18, 14:10 UTC
Resolved - Our Engineering team has confirmed that the issue affecting the DNS resolution of .co top-level domain (TLD) has been resolved. The DNS resolution for .co domains is now working as expected.

We apologize for the inconvenience. If you continue to face any issues, please open a support ticket from within your account.

Apr 17, 22:53 UTC
Monitoring - Our Engineering team has implemented a fix to resolve the issue that was affecting the DNS resolution of .co top-level domain (TLD).

During this time, users who are using DigitalOcean DNS resolvers in their resources should no longer experience issues related to the DNS resolution.

Our Engineers are currently monitoring the situation. We will post an update as soon as the issue is fully resolved.

Apr 17, 21:22 UTC
Identified - Our Engineering team is aware of a widespread, external issue affecting .co top-level domain (TLD). While this incident originates outside of DigitalOcean's infrastructure, you may experience errors when querying a .co domain, regardless of the DNS resolver being used.

Our Engineers are actively deploying temporary backend mitigations to help minimize the impact on our customers. We will continue to monitor the situation closely and post updates as more information becomes available.

Spaces availability in NYC3

Apr 17, 18:27 UTC
Resolved - From 17:22 to 17:46 UTC, our Engineering team observed an issue impacting Spaces availability in the NYC3 region. During this time, customers may have encountered 500 errors and degraded performance while accessing Spaces buckets. The issue has now been fully resolved. 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.

Received — 14 April 2026 DigitalOcean Status - Incident History

Serverless Inference

Apr 15, 02:56 UTC
Resolved - From 23:20 UTC to 02:00 UTC, users may have experienced elevated error rates due to service instability, which resulted in intermittent HTTP 500 errors and terminated connections.

Our Engineering team has confirmed full resolution of the issue, and all systems are now operating normally.

If you continue to experience any issues, please open a ticket with our support team. We apologize for any inconvenience caused.

Apr 15, 02:24 UTC
Monitoring - Our Engineering team has implemented a fix for the issue causing elevated error rates due to service instability. We are currently monitoring the situation to ensure stability and confirm that error rates, including HTTP 500 responses, have returned to normal levels.

We will provide a further update once we confirm the issue is fully resolved.

Apr 15, 01:07 UTC
Investigating - Our Engineering team is investigating an issue causing elevated error rates due to service instability and terminating open connections which causes some 500s. Some requests may fail while we work to resolve it.

We apologize for the inconvenience and will share an update once we have more information.

❌