Cloud Service Status
Last updated: Jun 20, 2026 14:22:27 UTC
AWS Incidents
2
2 medium
GCP Incidents
1
1 medium
DO Incidents
0
Total Active
3
Recent Incidents
124 incidents| Provider | Service | Title | Status | Severity | Started |
|---|---|---|---|---|---|
|
gcp
|
Multiple Products | Multiple Products - | Active | medium | Jun 9, 18:22 UTC |
DescriptionNetwork traffic to Google Cloud originating from Delhi, Chennai, Mumbai and surrounding areas is experiencing intermittent periods of elevated latency and possible packet loss. DetailsAffected Regions
asia-south2
Delhi (asia-south2)
global
Global
|
|||||
|
aws
|
Service impact: Increased connectivity issues and API Error Rates | Active | medium | Mar 1, 21:56 UTC | |
DescriptionWe are investigating increased API error rates in a single Availability Zone (mes1-az2) in the ME-SOUTH-1 Region. Details |
|||||
|
aws
|
Service impact: Increased Error Rates | Active | medium | Mar 1, 04:51 UTC | |
DescriptionWe are investigating issues with AWS services in the ME-CENTRAL-1 Region. Details |
|||||
|
DO
|
Monitoring Graphs in the Cloud Control Panel | Monitoring Graphs in the Cloud Control Panel | Resolved | low | Jun 19, 14:00 UTC |
Description<p> <small>Jun <var data-var='date'>19</var>, <var data-var='time'>16:37</var> UTC</small><br> <strong>Resolved</strong> - Between 13:22 & 14:26 UTC today, users have experienced missing monitoring graphs for Droplets (with DO agent installed), Load Balancers, Databases, and other services within the Cloud Control Panel.<br /><br />Our engineering team has identified the root cause of the issue and has taken appropriate steps to restore functionality. We can confirm that services have been restored and are functioning as expected.<br /><br />We apologize for any inconvenience this may have caused. If you continue to experience issues viewing monitoring graphs, please create a support ticket for further analysis. Thank you for your patience and understanding </p> <p> <small>Jun <var data-var='date'>19</var>, <var data-var='time'>14:50</var> UTC</small><br> <strong>Monitoring</strong> - Our engineering team has implemented the necessary fixes to address the issue affecting the visibility of monitoring graphs within the Cloud Panel. Users should now be able to view monitoring graphs for their services, including Droplets with DO Agent installed, Load Balancers, Databases, etc.<br /><br />We are currently monitoring the situation to ensure that the service has returned to normal operation and remain stable. We appreciate your patience and will provide an update once the issue is fully confirmed as resolved. </p> <p> <small>Jun <var data-var='date'>19</var>, <var data-var='time'>14:00</var> UTC</small><br> <strong>Investigating</strong> - Our Engineering team is currently investigating an issue affecting the visibility of monitoring graphs within the Cloud Panel. During this period, users may notice missing or unavailable monitoring graphs for services such as Droplets(with DO agent installed), Load Balancers, Databases, etc.<br /><br />We apologize for the inconvenience caused. We'll update once we have more information </p> DetailsStatus Timeline
Resolved
Jun 19, 16:37 UTC
Status changed from Monitoring to Resolved
Monitoring
Jun 19, 14:50 UTC
Status changed from Investigating to Monitoring |
|||||
|
DO
|
SGP1 Network Maintenance | SGP1 Network Maintenance | Resolved | low | Jun 18, 14:30 UTC |
Description<p> <small>Jun <var data-var='date'>18</var>, <var data-var='time'>17:30</var> UTC</small><br> <strong>Completed</strong> - The scheduled maintenance has been completed. </p> <p> <small>Jun <var data-var='date'>18</var>, <var data-var='time'>14:30</var> UTC</small><br> <strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary. </p> <p> <small>Jun <var data-var='date'>16</var>, <var data-var='time'>14:32</var> UTC</small><br> <strong>Scheduled</strong> - Start: 2026-06-18 14:30 UTC<br />End: 2026-06-18 17:30 UTC<br /><br />During the above window, our Networking team will be making changes to the core networking infrastructure to improve performance and scalability in the SGP1 region.<br /><br />Expected impact:<br /><br />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.<br /><br />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 </p> DetailsAffected Regions
sgp1
Singapore 1
Status Timeline
Resolved
Jun 18, 17:30 UTC
Status changed from Scheduled to Resolved |
|||||
|
DO
|
Core Infrastructure Maintenance June 17, 2026, 09:00 UTC | Core Infrastructure Maintenance June 17, 2026, 09:00 UTC | Resolved | low | Jun 17, 09:00 UTC |
Description<p> <small>Jun <var data-var='date'>17</var>, <var data-var='time'>18:00</var> UTC</small><br> <strong>Completed</strong> - The scheduled maintenance has been completed. </p> <p> <small>Jun <var data-var='date'>17</var>, <var data-var='time'>09:00</var> UTC</small><br> <strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary. </p> <p> <small>Jun <var data-var='date'>17</var>, <var data-var='time'>05:53</var> UTC</small><br> <strong>Scheduled</strong> - Core Infrastructure Maintenance<br /><br />Start: 2025-06-17 09:00 UTC<br />End: 2025-06-17 18:00 UTC<br /><br />During the above time, our Engineering Team will be performing maintenance to failover some internal databases from one cluster to another.<br /><br />Existing infrastructure, including Droplets and Droplet-based services, should continue running without issue. There is no network disruption to existing services expected as part of this maintenance. However, there are dependencies on multiple services. During the failover, there may be customer impacts that should be brief and transitory. <br /><br />Multiple teams will be engaged to keep downtime to a minimum and mitigate any impact that does occur. We’ll post updates here for any unexpected changes to this scheduled maintenance, as well as progress updates during the maintenance itself.<br /><br />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<br /><br />Thank you,<br />Team DigitalOcean </p> DetailsStatus Timeline
Resolved
Jun 17, 18:00 UTC
Status changed from Scheduled to Resolved |
|||||
|
DO
|
Intermittent 500 Errors on Serverless/GenAI Inference API | Intermittent 500 Errors on Serverless/GenAI Inference API | Resolved | low | Jun 16, 22:53 UTC |
Description<p> <small>Jun <var data-var='date'>17</var>, <var data-var='time'>00:29</var> UTC</small><br> <strong>Resolved</strong> - The connectivity issues affecting our Serverless/GenAI Inference API have been fully resolved.<br />Our engineering teams successfully completed the connectivity restoration. All systems should be functioning normally, and the endpoint should be fully operational. </p> <p> <small>Jun <var data-var='date'>16</var>, <var data-var='time'>23:29</var> UTC</small><br> <strong>Monitoring</strong> - Our engineering teams have successfully begun implementing mitigation steps to resolve the connectivity issues affecting the inference API. We will provide another update once the API has fully recovered and error rates return to normal. </p> <p> <small>Jun <var data-var='date'>16</var>, <var data-var='time'>22:00</var> UTC</small><br> <strong>Investigating</strong> - We are actively investigating an issue causing elevated HTTP 500 error rates for customers utilizing our Serverless/GenAI Inference API.<br />Customer Impact: Customers making calls to the inference API—specifically targeting /v1/* endpoints—will experience intermittent HTTP 500 errors and failed requests. </p> DetailsStatus Timeline
Resolved
Jun 17, 00:29 UTC
Status changed from Monitoring to Resolved
Monitoring
Jun 16, 23:29 UTC
Status changed from Investigating to Monitoring |
|||||
|
aws
|
Service impact: Fable 5 and Mythos 5 Access | Resolved | medium | Jun 12, 18:26 UTC | |
DescriptionTo support compliance with the US Government export control directive, Anthropic has asked us to revoke access to Claude Fable 5 and Claude Mythos 5 for all users in all regions. All other models, including Opus 4.8, are not affected and you can continue using them in full confidence. Please view the <a href="https://www.anthropic.com/news/fable-mythos-access">Anthropic statement</a> for further details. DetailsStatus Timeline
Resolved
Jun 16, 18:20 UTC
Auto-resolved: no longer in provider status feed |
|||||
|
DO
|
DeepSeek V4 Pro is returning HTTP 429 "Rate limit exceeded" | DeepSeek V4 Pro is returning HTTP 429 "Rate limit exceeded" | Resolved | low | Jun 11, 14:24 UTC |
Description<p> <small>Jun <var data-var='date'>11</var>, <var data-var='time'>17:42</var> UTC</small><br> <strong>Resolved</strong> - This incident has been resolved. </p> <p> <small>Jun <var data-var='date'>11</var>, <var data-var='time'>14:31</var> UTC</small><br> <strong>Identified</strong> - The issue has been identified and a fix is being implemented. </p> <p> <small>Jun <var data-var='date'>11</var>, <var data-var='time'>14:30</var> UTC</small><br> <strong>Update</strong> - We are continuing to investigate this issue. </p> <p> <small>Jun <var data-var='date'>11</var>, <var data-var='time'>14:24</var> UTC</small><br> <strong>Investigating</strong> - We are currently facing issues with Gradient AI DeepSeek V4 Pro is returning HTTP 429 "Rate limit exceeded" </p> DetailsStatus Timeline
Resolved
Jun 11, 17:42 UTC
Status changed from Identified to Resolved
Identified
Jun 11, 14:31 UTC
Status changed from Investigating to Identified |
|||||
|
DO
|
AMS2 Network Maintenance | AMS2 Network Maintenance | Resolved | low | Jun 10, 15:30 UTC |
Description<p> <small>Jun <var data-var='date'>10</var>, <var data-var='time'>18:30</var> UTC</small><br> <strong>Completed</strong> - The scheduled maintenance has been completed. </p> <p> <small>Jun <var data-var='date'>10</var>, <var data-var='time'>15:30</var> UTC</small><br> <strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary. </p> <p> <small>Jun <var data-var='date'> 8</var>, <var data-var='time'>15:41</var> UTC</small><br> <strong>Scheduled</strong> - Start: 2026-06-10 15:30 UTC<br />End: 2026-06-10 18:30 UTC<br /><br />During the above window, our Networking team will be making changes to the core networking infrastructure to improve performance and scalability in the AMS2 region.<br /><br />Expected impact:<br /><br />These changes are designed and tested to be seamless. We do not expect any customer impact during the mentioned timeframe. If an unexpected issue arises, there could be a temporary loss of connectivity for Droplets and its dependent services, such as Managed Databases, Load Balancers, App Platform, and Managed Kubernetes, in the AMS2 region. We will endeavor to minimize any such impact.<br /><br />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 </p> DetailsAffected Regions
ams2
Amsterdam 2
Status Timeline
Resolved
Jun 10, 18:30 UTC
Status changed from Scheduled to Resolved |
|||||
|
DO
|
DNS API Service | DNS API Service | Resolved | low | Jun 4, 10:12 UTC |
Description<p> <small>Jun <var data-var='date'> 4</var>, <var data-var='time'>11:47</var> UTC</small><br> <strong>Resolved</strong> - Between 09:41 and 11:24 UTC, our Engineering team identified an issue impacting the DNS API service. During this period, users may have experienced issues performing domain and DNS record management operations through the Control Panel and API. Services dependent on DNS API operations, including Let's Encrypt certificate provisioning, MongoDB cluster creation, App Platform deployments, and DigitalOcean Kubernetes (DOKS) cluster create and delete operations, were also impacted.<br /><br />Our Engineering team has confirmed that the underlying issue affecting the DNS API service has been fully resolved, and all affected services are now operating normally.<br /><br />If you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused. </p> <p> <small>Jun <var data-var='date'> 4</var>, <var data-var='time'>11:39</var> UTC</small><br> <strong>Monitoring</strong> - Our Engineering team has implemented a fix to resolve the issue impacting our DNS API service. Users should now be able to perform domain and DNS record management operations successfully through the Control Panel and API. Additionally, services affected by this issue, including Let's Encrypt certificate provisioning, MongoDB cluster creation, App Platform deployments, and DigitalOcean Kubernetes (DOKS) cluster create and delete operations, should now be functioning as expected.<br /><br />We are monitoring the situation closely and will share an update once the issue is resolved completely. </p> <p> <small>Jun <var data-var='date'> 4</var>, <var data-var='time'>11:32</var> UTC</small><br> <strong>Identified</strong> - Our Engineering team has identified the cause of the issue impacting our DNS API service and is actively working on a fix. During this time, users may experience errors when attempting to create, update, or delete domains and DNS records through the Control Panel and API. As a result, services that depend on DNS API operations, including Let's Encrypt certificate provisioning, MongoDB cluster creation, App Platform deployments, and DigitalOcean Kubernetes (DOKS) cluster create and delete operations, may also be impacted.<br /><br />We will post an update as soon as additional information is available. </p> <p> <small>Jun <var data-var='date'> 4</var>, <var data-var='time'>10:59</var> UTC</small><br> <strong>Update</strong> - Our Engineering team continues to investigate an issue impacting our DNS API service. During this time, users may experience issues performing domain and DNS record management operations from the Control Panel and API, including creating, updating, or deleting DNS records. As a result, services that depend on DNS API operations, including Let's Encrypt certificate provisioning, MongoDB cluster creation, App Platform deployments, and DigitalOcean Kubernetes (DOKS) cluster create and delete operations, may also be impacted.<br /><br />We apologize for the inconvenience and will share more information as it becomes available. </p> <p> <small>Jun <var data-var='date'> 4</var>, <var data-var='time'>10:12</var> UTC</small><br> <strong>Investigating</strong> - Our Engineering team is investigating an issue impacting our DNS API service. During this time, users may experience issues performing domain and DNS record management operations from the Control Panel and API, including creating, updating, or deleting DNS records. As a result, services that rely on DNS API operations, such as Let's Encrypt certificate provisioning and MongoDB cluster creation, may also be impacted.<br /><br />We apologize for the inconvenience and will share an update once we have more information. </p> DetailsStatus Timeline
Resolved
Jun 4, 11:47 UTC
Status changed from Monitoring to Resolved
Monitoring
Jun 4, 11:39 UTC
Status changed from Identified to Monitoring
Identified
Jun 4, 11:32 UTC
Status changed from Investigating to Identified |
|||||
|
DO
|
App Platform Deployments in Multiple Regions | App Platform Deployments | Resolved | low | May 29, 00:14 UTC |
Description<p> <small>May <var data-var='date'>29</var>, <var data-var='time'>07:58</var> UTC</small><br> <strong>Resolved</strong> - Our Engineering team has confirmed that the issue impacting build failures on App Platform has been resolved at 07:00 am UTC. All App Platform builds are now succeeding as expected. Customers who previously encountered build failures should now be able to deploy their applications without further issues.<br /><br />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. </p> <p> <small>May <var data-var='date'>29</var>, <var data-var='time'>01:58</var> UTC</small><br> <strong>Monitoring</strong> - Our Engineering team has implemented a fix to resolve the issue with build failures on App Platform. Users should see their builds deploy successfully now.<br /><br />We are closely monitoring the situation, and will post an update once we've confirmed this is fully resolved. </p> <p> <small>May <var data-var='date'>29</var>, <var data-var='time'>00:14</var> UTC</small><br> <strong>Investigating</strong> - Our Engineering team is currently investigating an issue with build failures on App Platform in multiple regions. Users may experience errors when attempting to build their applications, resulting in failed deployments.<br /><br />Our Engineering team is working to fix the issue and will share an update once we have more details.<br /><br />We apologize for the inconvenience this issue may be causing and appreciate your patience as we work to resolve it. </p> DetailsStatus Timeline
Resolved
May 29, 07:58 UTC
Status changed from Monitoring to Resolved
Monitoring
May 29, 01:58 UTC
Status changed from Investigating to Monitoring |
|||||
|
aws
|
Service impact: Increased API Error Rates | Resolved | medium | May 22, 16:38 UTC | |
DescriptionWe are investigating increased error rates for Route53 API calls. DetailsStatus Timeline
Resolved
May 24, 00:20 UTC
Auto-resolved: no longer in provider status feed |
|||||
|
DO
|
Cloud Firewall | Cloud Firewall | Resolved | low | May 20, 12:08 UTC |
Description<p> <small>May <var data-var='date'>20</var>, <var data-var='time'>13:03</var> UTC</small><br> <strong>Resolved</strong> - Between 06:35 UTC & 12:36 UTC today, our engineering team identified an issue impacting the Cloud Firewall. During this period, users might have encountered issues while updating their firewall rules.<br /><br />Our team has taken appropriate measures to address the issue. We can confirm that service has been restored and is now functioning normally.<br /><br />We regret the inconvenience caused and appreciate your patience and understanding. However, if you continue to experience any issues, please create a support ticket for further analysis. </p> <p> <small>May <var data-var='date'>20</var>, <var data-var='time'>12:43</var> UTC</small><br> <strong>Monitoring</strong> - Our engineering team has implemented a fix that affected the Cloud Firewall rules. Users should now be able to update their firewalls successfully.<br /><br />We are actively monitoring the situation to ensure overall stability. We appreciate your patience and will provide an update once the issue is fully confirmed as resolved. </p> <p> <small>May <var data-var='date'>20</var>, <var data-var='time'>12:08</var> UTC</small><br> <strong>Identified</strong> - Our engineering team identified an issue impacting Cloud Firewall Product. During this time, users may notice HTTP 500 errors when updating firewalls.<br /><br />We apologize for the inconvenience and will share an update once more information is available. </p> DetailsStatus Timeline
Resolved
May 20, 13:03 UTC
Status changed from Monitoring to Resolved
Monitoring
May 20, 12:43 UTC
Status changed from Identified to Monitoring |
|||||
|
DO
|
Cloud Firewall | Cloud Firewall | Resolved | low | May 20, 05:35 UTC |
Description<p> <small>May <var data-var='date'>20</var>, <var data-var='time'>07:48</var> UTC</small><br> <strong>Resolved</strong> - Our Engineering team has verified that the issue causing incorrect Cloud Firewall rules to display on the cloud panel is fully resolved. The user interface continues to function as expected, and all systems have returned to normal operating conditions.<br /><br />If you continue to experience problems, please open a ticket with our support team. Thank you for your patience throughout this incident. </p> <p> <small>May <var data-var='date'>20</var>, <var data-var='time'>07:15</var> UTC</small><br> <strong>Monitoring</strong> - Our Engineering team has implemented a fix to resolve the issue causing incorrect Cloud Firewall rules to display on the cloud panel. At this time, the user interface is functioning as expected, and we are actively monitoring the situation to ensure continued stability.<br /><br />We will provide a final update once we have verified that the issue is fully resolved. </p> <p> <small>May <var data-var='date'>20</var>, <var data-var='time'>05:35</var> UTC</small><br> <strong>Investigating</strong> - We are currently investigating an issue with incorrect Cloud Firewall rules appearing on the cloud panel. Our engineering team is aware of the situation and actively working to identify the root cause. Since this is a user interface issue, users should not experience any problems with other services or networking.<br /><br />We apologize for the inconvenience and appreciate your patience. We will continue to provide updates as we learn more. </p> DetailsStatus Timeline
Resolved
May 20, 07:48 UTC
Status changed from Monitoring to Resolved
Monitoring
May 20, 07:15 UTC
Status changed from Investigating to Monitoring |
|||||
|
DO
|
Block Storage Volume Performance | Block Storage Volume Performance | Resolved | low | May 20, 01:05 UTC |
Description<p> <small>May <var data-var='date'>20</var>, <var data-var='time'>05:13</var> UTC</small><br> <strong>Resolved</strong> - From 00:00 UTC to 01:40 UTC, users may have experienced degraded write performance and intermittent impacts to workloads dependent on Block Storage Volumes in the NYC3 region.<br /><br />Our Engineering team has confirmed that the underlying infrastructure issue affecting Block Storage Volumes at the storage layer has been fully resolved, and services are now operating normally.<br /><br />If you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused. </p> <p> <small>May <var data-var='date'>20</var>, <var data-var='time'>02:19</var> UTC</small><br> <strong>Monitoring</strong> - Our Engineering team has implemented mitigation measures for the infrastructure issue affecting Block Storage Volumes in the NYC3 region. The team is monitoring the situation, and we will share another update once the issue is fully resolved </p> <p> <small>May <var data-var='date'>20</var>, <var data-var='time'>01:05</var> UTC</small><br> <strong>Investigating</strong> - Our Engineering team is currently investigating an ongoing infrastructure issue in the NYC3 region affecting Block Storage Volumes at the storage layer. Users may experience degraded write performance and intermittent impact to services dependent on the affected storage infrastructure.<br /><br />We apologize for the inconvenience and will continue to provide updates as more information becomes available. </p> DetailsStatus Timeline
Resolved
May 20, 05:13 UTC
Status changed from Monitoring to Resolved
Monitoring
May 20, 02:19 UTC
Status changed from Investigating to Monitoring |
|||||
|
DO
|
SGP1 Network Maintenance 2026-05-19 14:30 UTC | SGP1 Network Maintenance 2026-05-19 14:30 UTC | Resolved | low | May 19, 14:30 UTC |
Description<p> <small>May <var data-var='date'>19</var>, <var data-var='time'>17:30</var> UTC</small><br> <strong>Completed</strong> - The scheduled maintenance has been completed. </p> <p> <small>May <var data-var='date'>19</var>, <var data-var='time'>14:30</var> UTC</small><br> <strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary. </p> <p> <small>May <var data-var='date'>17</var>, <var data-var='time'>14:35</var> UTC</small><br> <strong>Scheduled</strong> - Start: 2026-05-19 14:30 UTC<br />End: 2026-05-19 17:30 UTC<br /><br />During the above window, our Networking team will be making changes to the core networking infrastructure to improve performance and scalability in the SGP1 region.<br /><br />Expected impact:<br /><br />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.<br /><br />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 </p> DetailsAffected Regions
sgp1
Singapore 1
Status Timeline
Resolved
May 19, 17:30 UTC
Status changed from Scheduled to Resolved |
|||||
|
DO
|
Anthropic reported outage that's impacting access to their Serverless Inference models | Anthropic reported outage that's impacting access to their Serverless Inference models | Resolved | low | May 15, 01:23 UTC |
Description<p> <small>May <var data-var='date'>15</var>, <var data-var='time'>02:00</var> UTC</small><br> <strong>Resolved</strong> - As of the current time, our Engineering team has confirmed that the issue with Serverless Inference has been resolved. The root cause of the issue was an outage with our provider, Anthropic, which affected users of Sonnet 4.6 and Opus 4.7 models. According to Anthropic's status page (https://status.claude.com/incidents/8z7l5zcy0v3b), they have resolved the outage. If you continue to experience problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused. </p> <p> <small>May <var data-var='date'>15</var>, <var data-var='time'>01:23</var> UTC</small><br> <strong>Identified</strong> - According to Anthropic's status page (https://status.claude.com/incidents/8z7l5zcy0v3b), they have identified the root cause and are actively working on a fix. At this time, users may continue to experience errors when attempting to use Sonnet 4.6 and Opus 4.7 models. We will provide another update once Anthropic has implemented a fix and service is restored. </p> <p> <small>May <var data-var='date'>15</var>, <var data-var='time'>01:21</var> UTC</small><br> <strong>Monitoring</strong> - As of the current time, our Engineering team is aware of an ongoing incident with our provider, Anthropic, that is impacting Serverless Inference. The outage is affecting all users attempting to use Sonnet 4.6 and Opus 4.7 models. According to Anthropic's status page (https://status.claude.com/incidents/8z7l5zcy0v3b), they are currently experiencing an outage that is causing this disruption. We apologize for the inconvenience and will provide updates as more information becomes available. </p> DetailsStatus Timeline
Resolved
May 15, 02:00 UTC
Status changed from Monitoring to Resolved |
|||||
|
DO
|
DNS service and Certificates | DNS service, Certificates and Managed MongoDB | Resolved | low | May 14, 13:57 UTC |
Description<p> <small>May <var data-var='date'>14</var>, <var data-var='time'>20:46</var> UTC</small><br> <strong>Resolved</strong> - As of 19:50 UTC, the issue affecting the DNS service has been fully resolved, and all related services, including Let's Encrypt certificate issuance and Managed MongoDB provisioning, are now operating normally.<br /><br />The backlog of delayed requests has been successfully processed, and all DNS record updates, pending certificate, and MongoDB operations should now be complete. <br /><br />We apologize for the disruption this caused and appreciate your patience while our team worked to restore full functionality.<br /><br />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. </p> <p> <small>May <var data-var='date'>14</var>, <var data-var='time'>16:42</var> UTC</small><br> <strong>Monitoring</strong> - Our Engineering team has implemented a fix for the issue affecting our DNS service and are now seeing DNS record updates successfully propagate to the edge.<br /><br />As a result, Let's Encrypt certificate issuance and Managed MongoDB provisioning (including scaling operations) should resume. We are currently monitoring the systems as they process the backlog of delayed requests. Affected MongoDB clusters and certificate requests should complete their provisioning automatically.<br /><br />We will continue to monitor the situation closely to ensure full stability. We appreciate your patience throughout this process and will provide an update once the issue is fully confirmed as resolved. </p> <p> <small>May <var data-var='date'>14</var>, <var data-var='time'>15:52</var> UTC</small><br> <strong>Update</strong> - Our engineering team continues to investigate an issue affecting our DNS service. At this time, DNS resolution remains functional; however, new changes to DNS records are currently not being reflected at the edge.<br /><br />This issue is also impacting related services. Specifically, customers may be unable to create new Let's Encrypt certificates. Regarding Managed MongoDB, customers will be able to submit requests to create new clusters or scale existing ones, but the completion of the provisioning process is currently delayed. This is due to the dependency on Let's Encrypt certificate issuance, which requires functional DNS propagation.<br /><br />Affected clusters will automatically recover and complete their provisioning once the DNS issue is resolved. Our engineering team is actively working to restore full functionality across all affected services.<br /><br />We apologize for the inconvenience and will share more information as it becomes available. </p> <p> <small>May <var data-var='date'>14</var>, <var data-var='time'>13:57</var> UTC</small><br> <strong>Investigating</strong> - Our Engineering team is investigating an issue affecting our DNS service. At this time, DNS resolution remains functional but any changes to DNS records are not being reflected at the edge. Additionally, customers may be unable to create new Let's Encrypt certificates at this time. Our engineering team is actively working to identify the root cause and restore full functionality.<br /><br />We apologize for any inconvenience, and we'll share more information as it becomes available. </p> DetailsStatus Timeline
Resolved
May 14, 20:46 UTC
Status changed from Monitoring to Resolved
Monitoring
May 14, 16:43 UTC
Status changed from Investigating to Monitoring |
|||||
|
DO
|
Data-plane DOKS cluster in SYD1 region | Data-plane DOKS cluster in SYD1 region | Resolved | low | May 14, 04:30 UTC |
Description<p> <small>May <var data-var='date'>16</var>, <var data-var='time'>05:07</var> UTC</small><br> <strong>Completed</strong> - The scheduled maintenance currently in progress has encountered unexpected roadblocks. As a result, we have made the decision to pause the maintenance at this time.<br /><br />We will provide a further update with a specific time and date for the resumption and expected completion as soon as those details are finalized.<br /><br />We apologize for any inconvenience and thank you for your understanding.<br /><br />If you have questions or concerns about this maintenance, please reach out to us by opening up a ticket on your account. </p> <p> <small>May <var data-var='date'>15</var>, <var data-var='time'>06:06</var> UTC</small><br> <strong>Update</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary. </p> <p> <small>May <var data-var='date'>14</var>, <var data-var='time'>20:06</var> UTC</small><br> <strong>In progress</strong> - Phase 1 maintenance is complete. Phase 2 is scheduled to begin on the 15th of May 2026 (Friday) at 04:30 UTC. </p> <p> <small>May <var data-var='date'>14</var>, <var data-var='time'>20:05</var> UTC</small><br> <strong>Scheduled</strong> - Phase 1 maintenance is complete. Phase 2 is scheduled to begin on the 15th of May 2026 (Friday) at 04:30 UTC. </p> <p> <small>May <var data-var='date'>14</var>, <var data-var='time'>04:30</var> UTC</small><br> <strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary. </p> <p> <small>May <var data-var='date'>13</var>, <var data-var='time'>21:02</var> UTC</small><br> <strong>Scheduled</strong> - Phase 1 Start: 2026-05-14 04:30 UTC<br />Phase 1 End: 2026-05-14 17:30 UTC<br /><br />Phase 2 Start: 2026-05-15 04:30 UTC<br />Phase 2 End: 2026-05-15 17:30 UTC<br /><br /><br />During the above windows, our Engineering team will be performing upgrades to Functions backend infrastructure in the SYD1 region. <br /><br />Expected Impact:<br /><br />We anticipate some potential service disruptions during these maintenance windows. Function invocations may experience brief periods of elevated error rates or timeouts during node pool recycling in each region, and Apps that are configured with DBaaS Trusted Sources may see Trusted Source connectivity failures until DBaaS firewall rules are refreshed post-upgrade. We do not anticipate any impact to other non-Function components.<br /><br /><br />If you have any questions related to this event, please send us a ticket from your cloud support page. https://cloudsupport.digitalocean.com/s/createticket </p> DetailsAffected Regions
syd1
Sydney 1
Status Timeline
Resolved
May 16, 05:07 UTC
Status changed from Update to Resolved
Update
May 15, 06:06 UTC
Status changed from Scheduled to Update |
|||||
|
DO
|
GradientAI: Agent Platform Playground Interaction Erros | GradientAI: Agent Platform Playground Interaction Errors | Resolved | low | May 12, 10:24 UTC |
Description<p> <small>May <var data-var='date'>12</var>, <var data-var='time'>11:37</var> UTC</small><br> <strong>Resolved</strong> - The remediation for the issue affecting the GradientAI Agent Platform Playground has been fully implemented, and the service is operating normally. We are no longer observing customer impact related to this issue, and the incident has been resolved. </p> <p> <small>May <var data-var='date'>12</var>, <var data-var='time'>11:36</var> UTC</small><br> <strong>Monitoring</strong> - We have applied a fix for the issue affecting the GradientAI Agent Platform Playground and are monitoring the service to ensure continued stability. At this time, we are no longer observing new reports related to this issue. </p> <p> <small>May <var data-var='date'>12</var>, <var data-var='time'>11:14</var> UTC</small><br> <strong>Update</strong> - A fix has been applied for the issue affecting the GradientAI Agent Platform Playground, and we are observing recovery in service behavior. </p> <p> <small>May <var data-var='date'>12</var>, <var data-var='time'>10:50</var> UTC</small><br> <strong>Identified</strong> - We have identified the cause of the issue affecting the GradientAI Agent Platform Playground. Our engineering team is implementing a fix, and we will provide another update as soon as it is available. </p> <p> <small>May <var data-var='date'>12</var>, <var data-var='time'>10:24</var> UTC</small><br> <strong>Investigating</strong> - We are currently investigating an issue affecting the GradientAI Agent Platform Playground. Users may see a “Something went wrong” error for all agent interactions in the Playground. Agent functionality through API endpoints remains unaffected. We are actively working to identify the cause and will provide an update as soon as more information is available. </p> DetailsStatus Timeline
Resolved
May 12, 11:37 UTC
Status changed from Identified to Resolved
Identified
May 12, 10:50 UTC
Status changed from Investigating to Identified |
|||||
|
DO
|
Control Panel Errors | Control Panel Errors - Unable to Enable 2FA and Google/GitHub | Resolved | low | May 9, 11:15 UTC |
Description<p> <small>May <var data-var='date'> 9</var>, <var data-var='time'>14:42</var> UTC</small><br> <strong>Resolved</strong> - 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.<br /><br />Our team has taken appropriate measures to address the issue. We can confirm that service has been restored and is now functioning normally.<br /><br />We regret the inconvenience caused. However, if you continue to experience any issues, please create a support ticket for further analysis. </p> <p> <small>May <var data-var='date'> 9</var>, <var data-var='time'>13:51</var> UTC</small><br> <strong>Monitoring</strong> - 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.<br /><br />We appreciate your patience and will provide an update once the issue is fully confirmed as resolved. </p> <p> <small>May <var data-var='date'> 9</var>, <var data-var='time'>11:15</var> UTC</small><br> <strong>Investigating</strong> - 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.<br /><br />We apologize for the inconvenience and will provide an update as soon as more information becomes available. </p> DetailsStatus Timeline
Resolved
May 9, 14:42 UTC
Status changed from Monitoring to Resolved
Monitoring
May 9, 13:51 UTC
Status changed from Investigating to Monitoring |
|||||
|
DO
|
Let's Encrypt Outage Affecting Certificate Issuance and Managed Databases Operations | Let's Encrypt Outage Affecting Certificate Issuance and Managed Databases Operations | Resolved | low | May 8, 20:46 UTC |
Description<p> <small>May <var data-var='date'> 8</var>, <var data-var='time'>21:54</var> UTC</small><br> <strong>Resolved</strong> - 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. <br /><br />We appreciate your patience. If you continue to experience any issues, please open a support ticket from within your account. </p> <p> <small>May <var data-var='date'> 8</var>, <var data-var='time'>20:46</var> UTC</small><br> <strong>Identified</strong> - Our Engineering team is aware of an upstream outage with Let's Encrypt (see https://letsencrypt.status.io/) which impacts the following services: <br /><br />- Inability to create new Let's Encrypt certificates for Spaces, Load Balancers, and App Platform Custom Domains<br />- Stuck or delayed creates/forks/restores on Mongo, PG, and MySQL databases. <br /><br />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. <br /><br />We'll continue to monitor this situation and provide updates. We apologize for the inconvenience. </p> DetailsStatus Timeline
Resolved
May 8, 21:54 UTC
Status changed from Identified to Resolved |
|||||
|
DO
|
Multiple Services in NYC2 | Multiple Services in NYC2 | Resolved | low | May 8, 18:01 UTC |
Description<p> <small>May <var data-var='date'> 8</var>, <var data-var='time'>19:59</var> UTC</small><br> <strong>Resolved</strong> - 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. </p> <p> <small>May <var data-var='date'> 8</var>, <var data-var='time'>19:53</var> UTC</small><br> <strong>Update</strong> - We are continuing to monitor for any further issues. </p> <p> <small>May <var data-var='date'> 8</var>, <var data-var='time'>19:21</var> UTC</small><br> <strong>Monitoring</strong> - 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. </p> <p> <small>May <var data-var='date'> 8</var>, <var data-var='time'>18:01</var> UTC</small><br> <strong>Investigating</strong> - 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.<br /><br />Users with resources in the NYC2 region may experience issues with Droplet connectivity, API requests, or other services.<br /><br />We will provide additional updates as more information becomes available. We apologize for any inconvenience this may cause. </p> DetailsAffected Regions
nyc2
New York 2
Status Timeline
Resolved
May 8, 19:59 UTC
Status changed from Monitoring to Resolved
Monitoring
May 8, 19:21 UTC
Status changed from Investigating to Monitoring |
|||||
|
DO
|
Core Infrastructure Maintenance May 7, 2026, 15:00 UTC | Core Infrastructure Maintenance May 7, 2026, 15:00 UTC | Resolved | low | May 7, 15:20 UTC |
Description<p> <small>May <var data-var='date'> 7</var>, <var data-var='time'>21:00</var> UTC</small><br> <strong>Completed</strong> - The scheduled maintenance has been completed. </p> <p> <small>May <var data-var='date'> 7</var>, <var data-var='time'>15:20</var> UTC</small><br> <strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary. </p> <p> <small>May <var data-var='date'> 7</var>, <var data-var='time'>15:13</var> UTC</small><br> <strong>Scheduled</strong> - Start: 2026-05-07 15:00 UTC<br />End: 2026-05-07 21:00 UTC<br /><br />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.<br /><br />Expected Impact:<br /><br />During the maintenance window, users may experience brief periods of increased latency with the following platform operations:<br /><br />Cloud Control Panel and API operations<br />Event processing<br />Droplet creates, resizes, rebuilds, and power events<br />Managed Kubernetes reconciliation and scaling<br />Load Balancer operations<br />Container Registry operations<br />App Platform operations<br />Managed Database creation and scaling<br /><br />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.<br /><br />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 </p> DetailsStatus Timeline
Resolved
May 7, 21:00 UTC
Status changed from Scheduled to Resolved |
|||||
|
DO
|
Core Infrastructure Maintenance May 4th, 2026, 13:00 UTC | Core Infrastructure Maintenance May 4th, 2026, 13:00 UTC | Resolved | low | May 4, 13:00 UTC |
Description<p> <small>May <var data-var='date'> 4</var>, <var data-var='time'>21:01</var> UTC</small><br> <strong>Completed</strong> - The scheduled maintenance has been completed. </p> <p> <small>May <var data-var='date'> 4</var>, <var data-var='time'>13:01</var> UTC</small><br> <strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary. </p> <p> <small>May <var data-var='date'> 2</var>, <var data-var='time'>13:25</var> UTC</small><br> <strong>Scheduled</strong> - Start: 2026-05-04 13:00 UTC<br />End: 2026-05-04 21:00 UTC<br /><br />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.<br /><br />Expected Impact:<br /><br />During the maintenance window, users may experience brief periods of increased latency with the following platform operations:<br /><br />Cloud Control Panel and API operations<br />Event processing<br />Droplet creates, resizes, rebuilds, and power events<br />Managed Kubernetes reconciliation and scaling<br />Load Balancer operations<br />Container Registry operations<br />App Platform operations<br />Managed Database creation and scaling<br /><br />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.<br /><br />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 </p> DetailsStatus Timeline
Resolved
May 4, 21:01 UTC
Status changed from Scheduled to Resolved |
|||||
|
DO
|
Core Infrastructure Maintenance May 4, 2026, 13:00 UTC | Core Infrastructure Maintenance May 4, 2026, 13:00 UTC | Resolved | low | May 4, 13:00 UTC |
Description<p> <small>May <var data-var='date'> 4</var>, <var data-var='time'>21:00</var> UTC</small><br> <strong>Completed</strong> - The scheduled maintenance has been completed. </p> <p> <small>May <var data-var='date'> 4</var>, <var data-var='time'>13:00</var> UTC</small><br> <strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary. </p> <p> <small>May <var data-var='date'> 2</var>, <var data-var='time'>09:15</var> UTC</small><br> <strong>Scheduled</strong> - Start: 2026-05-04 13:00 UTC<br />End: 2025-05-04 21:00 UTC<br /><br />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.<br /><br />Expected Impact:<br /><br />During the maintenance window, users may experience brief periods of increased latency with the following platform operations:<br /><br />Cloud Control Panel and API operations<br />Event processing<br />Droplet creates, resizes, rebuilds, and power events<br />Managed Kubernetes reconciliation and scaling<br />Load Balancer operations<br />Container Registry operations<br />App Platform operations<br />Managed Database creation and scaling<br /><br />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.<br /><br />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 </p> DetailsStatus Timeline
Resolved
May 4, 21:00 UTC
Status changed from Scheduled to Resolved |
|||||
|
DO
|
SFO2 Network Maintenance | SFO2 Network Maintenance | Resolved | low | May 4, 13:00 UTC |
Description<p> <small>May <var data-var='date'> 4</var>, <var data-var='time'>15:00</var> UTC</small><br> <strong>Completed</strong> - The scheduled maintenance has been completed. </p> <p> <small>May <var data-var='date'> 4</var>, <var data-var='time'>13:00</var> UTC</small><br> <strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary. </p> <p> <small>May <var data-var='date'> 2</var>, <var data-var='time'>12:39</var> UTC</small><br> <strong>Scheduled</strong> - Start: 2026-05-04 13:00 UTC<br />End: 2026-05-04 15:00 UTC<br /><br />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.<br /><br />Expected impact:<br /><br />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.<br /><br />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 </p> DetailsAffected Regions
sfo2
San Francisco 2
Status Timeline
Resolved
May 4, 15:00 UTC
Status changed from Scheduled to Resolved |
|||||
|
DO
|
FRA1 Network Maintenance | FRA1 Network Maintenance | Resolved | low | Apr 30, 16:00 UTC |
Description<p> <small>Apr <var data-var='date'>30</var>, <var data-var='time'>19:00</var> UTC</small><br> <strong>Completed</strong> - The scheduled maintenance has been completed. </p> <p> <small>Apr <var data-var='date'>30</var>, <var data-var='time'>16:00</var> UTC</small><br> <strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary. </p> <p> <small>Apr <var data-var='date'>28</var>, <var data-var='time'>16:19</var> UTC</small><br> <strong>Scheduled</strong> - Start: Apr 30, 2026, 16:00 UTC to <br />End: Apr 30, 2026, 19:00 UTC<br /><br />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.<br /><br />Expected impact:<br /><br />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.<br /><br />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 </p> DetailsAffected Regions
fra1
Frankfurt 1
Status Timeline
Resolved
Apr 30, 19:00 UTC
Status changed from Scheduled to Resolved |
|||||
|
DO
|
SFO2 Network Maintenance | SFO2 Network Maintenance | Resolved | low | Apr 30, 13:00 UTC |
Description<p> <small>Apr <var data-var='date'>30</var>, <var data-var='time'>06:43</var> UTC</small><br> <strong>Completed</strong> - 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.<br /><br />Thank you for your understanding and patience as we work to improve performance and scalability.<br /><br />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 </p> <p> <small>Apr <var data-var='date'>28</var>, <var data-var='time'>13:16</var> UTC</small><br> <strong>Scheduled</strong> - Start: Apr 30, 2026, 13:00 UTC<br />End: Apr 30, 2026, 15:00 UTC<br /><br />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.<br /><br />Expected impact:<br /><br />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.<br /><br />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 </p> DetailsAffected Regions
sfo2
San Francisco 2
Status Timeline
Resolved
Apr 30, 06:43 UTC
Status changed from Scheduled to Resolved |
|||||
|
DO
|
NYC1 Network Maintenance | NYC1 Network Maintenance | Resolved | low | Apr 30, 10:00 UTC |
Description<p> <small>Apr <var data-var='date'>30</var>, <var data-var='time'>12:00</var> UTC</small><br> <strong>Completed</strong> - The scheduled maintenance has been completed. </p> <p> <small>Apr <var data-var='date'>30</var>, <var data-var='time'>10:00</var> UTC</small><br> <strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary. </p> <p> <small>Apr <var data-var='date'>28</var>, <var data-var='time'>10:14</var> UTC</small><br> <strong>Scheduled</strong> - Start: Apr 30, 2026, 10:00 UTC <br />End: Apr 30, 2026, 12:00 UTC<br /><br />Hello,<br /><br />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.<br /><br />Expected impact:<br /><br />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.<br /><br />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<br /><br />Thank you,<br />Team DigitalOcean </p> DetailsAffected Regions
nyc1
New York 1
Status Timeline
Resolved
Apr 30, 12:00 UTC
Status changed from Scheduled to Resolved |
|||||
|
DO
|
Core Infrastructure Maintenance Apr 29, 2026, 13:00 UTC | Core Infrastructure Maintenance Apr 29, 2026, 13:00 UTC | Resolved | low | Apr 29, 13:00 UTC |
Description<p> <small>Apr <var data-var='date'>29</var>, <var data-var='time'>15:29</var> UTC</small><br> <strong>Completed</strong> - 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.<br /><br />Thank you for your understanding and patience as we work to improve performance and scalability.<br /><br />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 </p> <p> <small>Apr <var data-var='date'>29</var>, <var data-var='time'>13:00</var> UTC</small><br> <strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary. </p> <p> <small>Apr <var data-var='date'>27</var>, <var data-var='time'>09:35</var> UTC</small><br> <strong>Scheduled</strong> - Start: 2026-04-29 13:00 UTC<br />End: 2026-04-29 21:00 UTC<br /><br />Hello,<br /><br />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.<br /><br />Expected Impact:<br /><br />During the maintenance window, users may experience brief periods of increased latency with the following platform operations:<br /><br />Cloud Control Panel and API operations<br />Event processing<br />Droplet creates, resizes, rebuilds, and power events<br />Managed Kubernetes reconciliation and scaling<br />Load Balancer operations<br />Container Registry operations<br />App Platform operations<br />Managed Database creation and scaling<br /><br />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.<br /><br />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<br /><br />Thank you,<br />Team DigitalOcean </p> DetailsStatus Timeline
Resolved
Apr 29, 15:29 UTC
Status changed from Scheduled to Resolved |
|||||
|
DO
|
Elevated 5xx “context canceled” errors impacting serverless inference customers | Elevated 5xx “context canceled” errors impacting serverless inference | Resolved | low | Apr 28, 13:45 UTC |
Description<p> <small>Apr <var data-var='date'>28</var>, <var data-var='time'>19:33</var> UTC</small><br> <strong>Resolved</strong> - All services are operating normally. We will continue to monitor the system to ensure ongoing reliability.<br /><br />Thank you for your patience while we worked to resolve this issue. </p> <p> <small>Apr <var data-var='date'>28</var>, <var data-var='time'>19:00</var> UTC</small><br> <strong>Monitoring</strong> - Service for Serverless Inference has been restored.<br />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.<br />Our team remains actively engaged to ensure full recovery. We appreciate your patience and will provide further updates as needed. </p> <p> <small>Apr <var data-var='date'>28</var>, <var data-var='time'>15:59</var> UTC</small><br> <strong>Identified</strong> - 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.<br /><br />We appreciate your patience and will provide updates as soon as more information becomes available. </p> <p> <small>Apr <var data-var='date'>28</var>, <var data-var='time'>13:45</var> UTC</small><br> <strong>Investigating</strong> - 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. </p> DetailsStatus Timeline
Resolved
Apr 28, 19:33 UTC
Status changed from Monitoring to Resolved
Monitoring
Apr 28, 19:00 UTC
Status changed from Identified to Monitoring
Identified
Apr 28, 15:59 UTC
Status changed from Investigating to Identified |
|||||
|
DO
|
Serverless Inference | Serverless Inference - Intermittent Rate Limiting Affecting Some Customers Using Anthropic Models | Resolved | low | Apr 27, 10:38 UTC |
Description<p> <small>Apr <var data-var='date'>27</var>, <var data-var='time'>11:37</var> UTC</small><br> <strong>Resolved</strong> - The issue is resolved, and service is operating normally. </p> <p> <small>Apr <var data-var='date'>27</var>, <var data-var='time'>11:07</var> UTC</small><br> <strong>Monitoring</strong> - 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. </p> <p> <small>Apr <var data-var='date'>27</var>, <var data-var='time'>10:38</var> UTC</small><br> <strong>Investigating</strong> - 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. </p> DetailsStatus Timeline
Resolved
Apr 27, 11:37 UTC
Status changed from Monitoring to Resolved
Monitoring
Apr 27, 11:09 UTC
Status changed from Investigating to Monitoring |
|||||
|
aws
|
Service impact: Increased Connectivity Issues | Resolved | medium | Apr 27, 04:27 UTC | |
DescriptionWe are investigating instance connectivity issues in a single Availability Zone (euw3-az2) in the EU-WEST-3 Region. DetailsStatus Timeline
Resolved
Apr 28, 17:15 UTC
Auto-resolved: no longer in provider status feed |
|||||
|
DO
|
Intermittent errors impacting Serverless Inference in ATL1 | Intermittent errors impacting some Serverless Inference models in ATL1 | Resolved | low | Apr 23, 22:26 UTC |
Description<p> <small>Apr <var data-var='date'>23</var>, <var data-var='time'>23:51</var> UTC</small><br> <strong>Resolved</strong> - This incident has been resolved. </p> <p> <small>Apr <var data-var='date'>23</var>, <var data-var='time'>22:26</var> UTC</small><br> <strong>Investigating</strong> - 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. </p> DetailsStatus Timeline
Resolved
Apr 23, 23:51 UTC
Status changed from Investigating to Resolved |
|||||
|
DO
|
App Platform Deployments | App Platform Deployments | Resolved | low | Apr 23, 08:08 UTC |
Description<p> <small>Apr <var data-var='date'>23</var>, <var data-var='time'>10:09</var> UTC</small><br> <strong>Resolved</strong> - 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.<br /><br />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.<br /><br />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. </p> <p> <small>Apr <var data-var='date'>23</var>, <var data-var='time'>09:52</var> UTC</small><br> <strong>Monitoring</strong> - 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.<br />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. </p> <p> <small>Apr <var data-var='date'>23</var>, <var data-var='time'>08:31</var> UTC</small><br> <strong>Update</strong> - 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.<br />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.<br />Our Engineering team is actively working to resolve these issues and will share an update as soon as more information becomes available.<br />We apologize for the inconvenience this may be causing and appreciate your patience. </p> <p> <small>Apr <var data-var='date'>23</var>, <var data-var='time'>08:08</var> UTC</small><br> <strong>Investigating</strong> - 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.<br /><br />Our Engineering team is working to fix the issue and will share an update once we have more information. <br /><br />We apologize for the inconvenience this issue may be causing and appreciate your patience as we work to resolve it. </p> DetailsStatus Timeline
Resolved
Apr 23, 10:09 UTC
Status changed from Monitoring to Resolved
Monitoring
Apr 23, 09:52 UTC
Status changed from Investigating to Monitoring |
|||||
|
DO
|
Onboarding UI Page for Kubernetes | Cloud UI for Managed Kubernetes | Resolved | low | Apr 23, 07:01 UTC |
Description<p> <small>Apr <var data-var='date'>23</var>, <var data-var='time'>08:46</var> UTC</small><br> <strong>Resolved</strong> - Our Engineering team has confirmed full resolution of the issue with Cloud UI for Managed Kubernetes at 09:19 UTC.<br /><br />All the services should be functioning as expected.<br /><br />If you continue to experience problems, please open a ticket with our support team. Thank you for your patience throughout this incident! </p> <p> <small>Apr <var data-var='date'>23</var>, <var data-var='time'>07:52</var> UTC</small><br> <strong>Update</strong> - 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.<br />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.<br />We apologize for the inconvenience and will share more information as soon as it becomes available </p> <p> <small>Apr <var data-var='date'>23</var>, <var data-var='time'>07:14</var> UTC</small><br> <strong>Update</strong> - 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.<br />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.<br />We apologize for the inconvenience and will share more information as soon as it becomes available. </p> <p> <small>Apr <var data-var='date'>23</var>, <var data-var='time'>07:01</var> UTC</small><br> <strong>Investigating</strong> - 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.<br /><br />We apologize for the inconvenience and will share more information as soon as it's available. </p> DetailsStatus Timeline
Resolved
Apr 23, 08:46 UTC
Status changed from Investigating to Resolved |
|||||
|
DO
|
Cloud Control Panel and API | Cloud Control Panel and API | Resolved | low | Apr 22, 11:06 UTC |
Description<p><small>Apr <var data-var='date'>22</var>, <var data-var='time'>11:47</var> UTC</small><br><strong>Resolved</strong> - Our Engineering team has resolved the issue that was impacting the DigitalOcean API and the Cloud Control Panel. The system is now operating normally.<br /><br />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.<br /><br />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.</p><p><small>Apr <var data-var='date'>22</var>, <var data-var='time'>11:25</var> UTC</small><br><strong>Monitoring</strong> - 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.<br /><br />We sincerely appreciate your patience and understanding as we work to restore normal service.</p><p><small>Apr <var data-var='date'>22</var>, <var data-var='time'>11:06</var> UTC</small><br><strong>Investigating</strong> - 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.<br /><br />We are actively looking into the root cause and will provide updates as soon as more information becomes available.<br /><br />We apologize for the inconvenience and appreciate your patience.</p> DetailsStatus Timeline
Resolved
Apr 22, 11:47 UTC
Status changed from Monitoring to Resolved
Monitoring
Apr 22, 11:25 UTC
Status changed from Investigating to Monitoring |
|||||
|
DO
|
DNS Resolution Issues with .co TLD | DNS Resolution for .co TLD | Resolved | low | Apr 17, 21:22 UTC |
Description<p><small>Apr <var data-var='date'>18</var>, <var data-var='time'>14:10</var> UTC</small><br><strong>Resolved</strong> - 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.<br /><br />We apologize for the inconvenience. If you continue to face any issues, please open a support ticket from within your account.</p><p><small>Apr <var data-var='date'>17</var>, <var data-var='time'>22:53</var> UTC</small><br><strong>Monitoring</strong> - Our Engineering team has implemented a fix to resolve the issue that was affecting the DNS resolution of .co top-level domain (TLD).<br /><br />During this time, users who are using DigitalOcean DNS resolvers in their resources should no longer experience issues related to the DNS resolution. <br /><br />Our Engineers are currently monitoring the situation. We will post an update as soon as the issue is fully resolved.</p><p><small>Apr <var data-var='date'>17</var>, <var data-var='time'>21:22</var> UTC</small><br><strong>Identified</strong> - 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.<br /><br />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.</p> DetailsStatus Timeline
Resolved
Apr 18, 14:10 UTC
Status changed from Monitoring to Resolved
Monitoring
Apr 17, 22:53 UTC
Status changed from Identified to Monitoring |
|||||
|
DO
|
Spaces Availability in NYC3 | Spaces availability in NYC3 | Resolved | low | Apr 17, 18:27 UTC |
Description<p><small>Apr <var data-var='date'>17</var>, <var data-var='time'>18:27</var> UTC</small><br><strong>Resolved</strong> - 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.</p> DetailsAffected Regions
nyc3
New York 3
|
|||||
|
DO
|
Core Infrastructure Maintenance in All Regions 2026-04-16 09:00 UTC | Core Infrastructure Maintenance in All Regions 2026-04-16 09:00 UTC | Resolved | low | Apr 16, 09:00 UTC |
Description<p> <small>Apr <var data-var='date'>22</var>, <var data-var='time'>18:31</var> UTC</small><br> <strong>Completed</strong> - The scheduled maintenance has been completed. </p> <p> <small>Apr <var data-var='date'>22</var>, <var data-var='time'>09:07</var> UTC</small><br> <strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary. </p> <p> <small>Apr <var data-var='date'>21</var>, <var data-var='time'>22:15</var> UTC</small><br> <strong>Scheduled</strong> - Phase 3 maintenance is complete. Phase 4 is scheduled to begin on the 22nd of April 2026 (Wednesday) at 09:00 UTC. </p> <p> <small>Apr <var data-var='date'>21</var>, <var data-var='time'>09:07</var> UTC</small><br> <strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary. </p> <p> <small>Apr <var data-var='date'>20</var>, <var data-var='time'>15:22</var> UTC</small><br> <strong>Scheduled</strong> - Phase 2 maintenance is complete. Phase 3 is scheduled to begin on the 21st of April 2026 (Tuesday) at 09:00 UTC. </p> <p> <small>Apr <var data-var='date'>20</var>, <var data-var='time'>09:25</var> UTC</small><br> <strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary. </p> <p> <small>Apr <var data-var='date'>16</var>, <var data-var='time'>15:05</var> UTC</small><br> <strong>Scheduled</strong> - Phase 1 maintenance is complete. Phase 2 is scheduled to begin on the 20th of April 2026 (Monday) at 09:00 UTC. </p> <p> <small>Apr <var data-var='date'>16</var>, <var data-var='time'>09:10</var> UTC</small><br> <strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary. </p> <p> <small>Apr <var data-var='date'>14</var>, <var data-var='time'>09:37</var> UTC</small><br> <strong>Scheduled</strong> - Hello,<br /><br />During the above window, our Engineering team will be performing maintenance on core control plane infrastructure across all regions. Please note that the existing infrastructure will continue running without issue. <br /><br />This maintenance will be carried out in four phases as outlined below:<br /><br />16 April 2026 (Thursday), 09:00–15:00 UTC<br />20 April 2026 (Monday), 09:00–15:00 UTC<br />21 April 2026 (Tuesday), 09:00–22:00 UTC<br />22 April 2026 (Wednesday), 09:00–22:00 UTC<br /><br />Expected Impact:<br /><br />We do not anticipate any impact, however, there is a small possibility that Control Panel functionality specifically CRUD (Create, Read, Update, Delete) operations may be affected during the maintenance window. All running workloads are expected to continue operating normally without interruption.<br /><br />Our team will be actively monitoring the environment throughout the maintenance, and any unexpected events will be promptly communicated through our status page.<br /><br />If you have any questions or concerns regarding this maintenance, please feel free to open a support ticket from https://cloudsupport.digitalocean.com/s/createticket. We’re here to help.<br /><br />Thank you,<br /><br />Team DigitalOcean </p> DetailsStatus Timeline
Resolved
Apr 22, 18:31 UTC
Status changed from Scheduled to Resolved |
|||||
|
DO
|
Serverless Inference | Serverless Inference | Resolved | low | Apr 15, 01:07 UTC |
Description<p><small>Apr <var data-var='date'>15</var>, <var data-var='time'>02:56</var> UTC</small><br><strong>Resolved</strong> - 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.<br /><br />Our Engineering team has confirmed full resolution of the issue, and all systems are now operating normally.<br /><br />If you continue to experience any issues, please open a ticket with our support team. We apologize for any inconvenience caused.</p><p><small>Apr <var data-var='date'>15</var>, <var data-var='time'>02:24</var> UTC</small><br><strong>Monitoring</strong> - 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.<br /><br />We will provide a further update once we confirm the issue is fully resolved.</p><p><small>Apr <var data-var='date'>15</var>, <var data-var='time'>01:07</var> UTC</small><br><strong>Investigating</strong> - 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.<br /><br />We apologize for the inconvenience and will share an update once we have more information.</p> DetailsStatus Timeline
Resolved
Apr 15, 02:56 UTC
Status changed from Monitoring to Resolved
Monitoring
Apr 15, 02:24 UTC
Status changed from Investigating to Monitoring |
|||||
|
DO
|
App Platform Deployments | App Platform Deployments | Resolved | low | Apr 14, 17:57 UTC |
Description<p><small>Apr <var data-var='date'>14</var>, <var data-var='time'>17:57</var> UTC</small><br><strong>Resolved</strong> - From 16:07 to 16:50 UTC, Our Engineering team observed an issue with App Platform Deployments in all regions. During this time, App deployments of both new and existing apps would have been affected. Our team has fully resolved the issues as of 16:50 UTC. All new and existing App deployments should now be functioning as expected. 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.</p> Details |
|||||
|
DO
|
Managed Database Resizes | Managed Database Resizes | Resolved | low | Apr 14, 12:53 UTC |
Description<p><small>Apr <var data-var='date'>14</var>, <var data-var='time'>15:19</var> UTC</small><br><strong>Resolved</strong> - Our Engineering team has resolved the issue with resize operations for Managed Databases and 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.</p><p><small>Apr <var data-var='date'>14</var>, <var data-var='time'>14:30</var> UTC</small><br><strong>Monitoring</strong> - Our Engineering team has taken action to mitigate the issue with resize operations for Managed Databases and implemented a fix . We are monitoring the situation and will post an update as soon as we confirm that the issue is fully resolved.</p><p><small>Apr <var data-var='date'>14</var>, <var data-var='time'>12:53</var> UTC</small><br><strong>Investigating</strong> - Our engineering team is investigating an issue impacting resize operations for Managed Databases. During this time, users may experience error when attempting to resize Managed Database via Cloud Control Panel and API in all regions. We apologize for the inconvenience and will share an update once we have more information.</p> DetailsStatus Timeline
Resolved
Apr 14, 15:19 UTC
Status changed from Monitoring to Resolved
Monitoring
Apr 14, 14:30 UTC
Status changed from Investigating to Monitoring |
|||||
|
DO
|
Droplet Availability in All Regions | Droplet Availability in All Regions | Resolved | low | Apr 10, 20:32 UTC |
Description<p><small>Apr <var data-var='date'>10</var>, <var data-var='time'>21:06</var> UTC</small><br><strong>Resolved</strong> - Our Engineering team has confirmed full resolution of the issue with creating Droplets in all regions. Users should be able to create Droplets without issue.<br /><br />We apologize for the inconvenience. If you continue to face any issues, please open a support ticket from within your account.</p><p><small>Apr <var data-var='date'>10</var>, <var data-var='time'>20:32</var> UTC</small><br><strong>Monitoring</strong> - Subject: Droplet Availability in All Regions<br /><br />Our Engineering team has identifed an issue with Droplet creates in all regions. A root cause has been found, a fix has been put in place and we are currently monitoring the situation to ensure full resolution. Users should be able to create new Droplets at this time. <br /><br />We will continue to monitor and we will post an update as soon as it is fully resolved. We apologize for the inconvenience.</p> DetailsStatus Timeline
Resolved
Apr 10, 21:06 UTC
Status changed from Monitoring to Resolved |
|||||
|
DO
|
MongoDB Maintenance | MongoDB Maintenance - BLR1, NYC3, SFO2, SGP1, SYD1, TOR1 | Resolved | low | Apr 9, 18:00 UTC |
Description<p><small>Apr <var data-var='date'> 9</var>, <var data-var='time'>22:51</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Apr <var data-var='date'> 9</var>, <var data-var='time'>18:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>18:23</var> UTC</small><br><strong>Update</strong> - We will be undergoing scheduled maintenance during this time.</p><p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>18:18</var> UTC</small><br><strong>Scheduled</strong> - Start: 2026-04-09 18:00 UTC <br />End: 2026-04-10 24:00 UTC <br /><br />During the above window, our Engineering team will perform maintenance on core MongoDB services in the BLR1, NYC3, SFO2, SGP1, SYD1 & TOR1regions to enhance security and improve auditing and compliance. Please note that existing databases and workloads will continue to function normally and will not be impacted.<br /><br />Expected Impact:<br /><br />We do not anticipate any service disruptions during this window. Your existing databases and workloads will continue to run normally without interruption.<br /><br />In the event that an unexpected issue occurs, administrative actions, such as creating, deleting, or scaling Managed MongoDB databases in the BLR1, NYC3, SFO2, SGP1, SYD1 & TOR1 regions, may experience delays.<br /><br />If an unexpected issue arises, we will work to keep any impact to a minimum and may revert the changes if required.<br /><br />If you have any questions related to this event, please open a ticket from your cloud support page: https://cloudsupport.digitalocean.com/s/createticket</p> DetailsAffected Regions
blr1
Bangalore 1
nyc3
New York 3
sfo2
San Francisco 2
sgp1
Singapore 1
syd1
Sydney 1
tor1
Toronto 1
Status Timeline
Resolved
Apr 9, 22:51 UTC
Status changed from Update to Resolved
Update
Apr 9, 18:00 UTC
Status changed from Scheduled to Update |
|||||
|
DO
|
MongoDB Maintenance | MongoDB Maintenance - AMS3, ATL1, LON1, NYC1, NYC2, SFO3 | Resolved | low | Apr 7, 18:00 UTC |
Description<p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>22:25</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>18:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Apr <var data-var='date'> 5</var>, <var data-var='time'>18:12</var> UTC</small><br><strong>Scheduled</strong> - Start: 2026-04-07 18:00 UTC<br />End: 2026-04-08 00:00 UTC<br /><br />During the above window, our Engineering team will perform maintenance on core MongoDB services in the AMS3, ATL1, LON1, NYC1, NYC2 & SFO3 regions to enhance security and improve auditing and compliance. Please note that existing databases and workloads will continue to function normally and will not be impacted.<br /><br />Expected Impact:<br /><br />We do not anticipate any service disruptions during this window. Your existing databases and workloads will continue to run normally without interruption.<br /><br />In the event that an unexpected issue occurs, administrative actions, such as creating, deleting, or scaling Managed MongoDB databases in the AMS3, ATL1, LON1, NYC1, NYC2 & SFO3 regions, may experience delays.<br /><br />If an unexpected issue arises, we will work to keep any impact to a minimum and may revert the changes if required.<br /><br />If you have any questions related to this event, please open a ticket from your cloud support page: https://cloudsupport.digitalocean.com/s/createticket</p> DetailsAffected Regions
ams3
Amsterdam 3
lon1
London 1
nyc1
New York 1
nyc2
New York 2
sfo3
San Francisco 3
Status Timeline
Resolved
Apr 7, 22:25 UTC
Status changed from Scheduled to Resolved |
|||||
|
DO
|
Control Plane | Control Plane | Resolved | low | Apr 7, 17:49 UTC |
Description<p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>17:49</var> UTC</small><br><strong>Resolved</strong> - Our Engineering team has resolved the control plane disruption that occurred from 17:06 to 17:18 UTC. During this time, users may have experienced intermittent issues with managing their resources through the Cloud Control Panel or DigitalOcean API. The root cause of the disruption was identified and addressed, and all services are now operating normally. <br /><br />If you continue to experience any problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused.</p> Details |
|||||
|
DO
|
Serverless Inference | Serverless Inference - High error rates for open source models ( Qwen 3 32B) | Resolved | low | Apr 7, 12:49 UTC |
Description<p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>15:50</var> UTC</small><br><strong>Resolved</strong> - Service has been fully restored, and the model is now operating normally. We have implemented improvements to enhance stability and reduce the likelihood of similar issues in the future.</p><p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>12:55</var> UTC</small><br><strong>Identified</strong> - We are currently investigating reports of elevated latency affecting requests to this model when using Serverless Inference and Agents.<br /><br />Earlier observations indicated increased error rates for the open-source Qwen 3 32B model. The Ray dashboard also showed multiple workers in a pending state, suggesting capacity constraints.<br /><br />Our analysis determined that the model was experiencing higher-than-expected request volume without sufficient resources to scale accordingly. To address this, the node pool size has been increased to improve available capacity. However, there are still insufficient nodes to fully support the desired number of model replicas.<br /><br />Following the node pool expansion, a new pod-related error has been identified. Our Engineering team is actively working to resolve this issue and restore full service performance.</p><p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>12:49</var> UTC</small><br><strong>Investigating</strong> - Serverless inference for alibaba-qwen3-32b (Qwen 3 32B) in tor1 is experiencing high error rates starting at 10:46 UTC.</p> DetailsStatus Timeline
Resolved
Apr 7, 15:50 UTC
Status changed from Identified to Resolved
Identified
Apr 7, 12:55 UTC
Status changed from Investigating to Identified |
|||||