❌

Normal view

Received β€” 4 July 2026 ⏭ DigitalOcean Status - Incident History

Limited access to Deepseek V4 Pro model

Jul 5, 00:53 UTC
Resolved - Our Engineering team has confirmed that the issue with the Deepseek V4 Pro model in Serverless Inference and Agent Platform has been fully resolved. The model is now operational, and users should be able to use it without experiencing any errors.

If you continue to experience any problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused and appreciate your patience.

Jul 4, 23:18 UTC
Monitoring - Our Engineering team has implemented a fix for the issue with the Deepseek V4 Pro model in Serverless Inference and Agent Platform. The model should now be operational, and users should no longer receive error 429 messages when attempting to use it. We are currently monitoring the situation to ensure the fix is successful and the model is functioning as expected. We will post an update if any further issues arise. If you continue to experience problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused.

Jul 4, 22:13 UTC
Investigating - Our Engineering team is investigating reports of an incident affecting the Deepseek V4 Pro model in Serverless Inference and Agent Platform. Users may experience errors when attempting to use this model, specifically receiving error 429 messages. We apologize for the inconvenience and are working to resolve the issue as soon as possible. We will provide an update once we have more information.

Droplet Actions in NYC3

Jul 4, 15:10 UTC
Resolved - Our Engineering team has confirmed that the issue impacting Droplets in the NYC3 region has been fully resolved. Users can now perform actions on their Droplets or create new Droplets in this region without any issues.

We appreciate your patience while we worked to resolve this issue. If you continue to experience any problems, please open a support ticket from your account so our team can investigate further.

Jul 4, 14:42 UTC
Monitoring - Our Engineering team has implemented a fix to address the issue affecting Droplets in the NYC3 region. The issue, which began at 12:38 UTC, caused disruptions to customers attempting to perform actions on their Droplets in the NYC3 region.

During this time, customers may also have experienced errors when trying to create Droplets in this region.

We are actively monitoring the situation to ensure the fix remains effective and will provide another update once the issue has been fully resolved.

NYC2 Network Maintenance

Jul 7, 15:30 UTC
Completed - The scheduled maintenance has been completed.

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

Jul 4, 09:05 UTC
Scheduled - Start: 2026-07-07 10:30 UTC
End: 2026-07-07 15:30 UTC

During the above maintenance window, our Networking Engineering team will be making changes to the core networking infrastructure on Baremetal GPU to enhance performance and scalability in the NYC2 region.

Expected impact:

We do not expect any customer impact during this maintenance. However, if any unexpected issues arise, our team will continuously monitor the situation and take appropriate corrective actions, including rolling back the change if necessary to restore service stability. We will make every effort to minimize any impact.

If you have any questions related to the maintenance, please don’t hesitate to reach out to us through https://cloudsupport.digitalocean.com/s/createticket

Received β€” 2 July 2026 ⏭ DigitalOcean Status - Incident History

Managed Database Clusters

Jul 3, 08:20 UTC
Resolved - Our engineering team has resolved the issue with Managed Database Clusters. All database systems should now be operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.

Jul 3, 06:08 UTC
Monitoring - Our engineering team has implemented a fix to resolve the issue with Managed Database Clusters and is monitoring the situation. We will post an update as soon as the issue is fully resolved.

Jul 3, 02:28 UTC
Update - Our engineering team is still investigating the issue affecting Managed Database Clusters. Users may still encounter delays creating/scaling/forking/restoring the aforementioned Managed Database Clusters.

We are working to resolve this as soon as possible. we apologize for the inconvenience. We will post an update here once we have more information.

Jul 2, 22:04 UTC
Investigating - Our engineering team is investigating an issue affecting Managed Database Clusters. Currently, users may encounter delays when creating/scaling/forking and restoring Standard MySQL, Standard PostgreSQL, OpenSearch, Kafka, and Valkey clusters through the Cloud Control Panel or API.

We apologize for the inconvenience and will provide further updates as soon as more information is available.

Received β€” 1 July 2026 ⏭ DigitalOcean Status - Incident History

DNS Lookup Failures for Managed Database

Jul 1, 16:28 UTC
Resolved - The intermittent DNS lookup failures between Managed Kubernetes and Managed Database hostnames in the FRA1 region have been resolved for now but please let us know if you see the issue again. Connectivity has remained stable, and all systems are operating normally. 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.

Jul 1, 12:15 UTC
Update - We are continuing to investigate this issue.

Jul 1, 11:35 UTC
Investigating - As of 06:39 UTC, our Engineering team is investigating reports of intermittent DNS lookup failures for Managed Database hostnames from Managed Kubernetes, primarily affecting connections from Managed Kubernetes to Managed Database hostnames.

At this point, customers in the FRA1 region may experience intermittent connectivity issues.

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

Droplet Resize

Jul 1, 13:28 UTC
Resolved - Our Engineering team has confirmed that the issue impacting Droplet resizes using the "Downscale Anytime" option has been fully resolved. Users can now resize their Droplets using the "Downscale Anytime" option without any issues.

We appreciate your patience while we worked to resolve this issue. If you continue to experience any problems, please open a support ticket from your account so our team can investigate further.

Jul 1, 12:43 UTC
Monitoring - Our Engineering team has identified the root cause of the issue affecting Droplet resizes using the "Downscale Anytime" option and has implemented a fix. Users should now be able to resize their Droplets using the "Downscale Anytime" option without experiencing any issues or errors.

We are actively monitoring the situation to ensure the fix remains effective and will provide another update once the issue has been fully resolved.

Jul 1, 11:13 UTC
Investigating - Our Engineering team is investigating an issue affecting Droplet resizes using the "Downscale Anytime" option. At this time users may find this option unavailable or unresponsive in the Cloud Control Panel.

As a workaround, resizes can be performed via the API while we work to resolve this issue.

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

Agent Timeouts While Retrieving Data from Knowledge Bases

Jul 2, 03:38 UTC
Resolved - This incident has been resolved, and our teams continue to monitor the results. If you experience any further issues, please contact support.

Jul 1, 08:39 UTC
Identified - Our Engineering team has identified the issue causing Agents to experience timeouts while retrieving data from Knowledge Bases.

Please be assured that our Engineering team is actively working on a fix and is treating this issue with high priority.

We sincerely apologise for any inconvenience this may have caused and appreciate your patience and understanding. If you have any further questions, please create a support ticket so that we can investigate your specific case further.

Jul 1, 06:25 UTC
Investigating - Our Engineering team is currently investigating an issue where Agents are experiencing timeouts while retrieving data from Knowledge Bases. As a result, affected Agents may fail to retrieve data and return the following error:

"Failed to retrieve data from Knowledge base(s) - timeout"

Please be assured that we are treating this as a high-priority issue and are actively working to mitigate it.

We sincerely apologise for any inconvenience this may have caused and appreciate your patience and understanding. If you have any further questions, please create a support ticket so that we can investigate your specific case further.

Received β€” 27 June 2026 ⏭ DigitalOcean Status - Incident History

Droplet Backup Service

Jun 27, 18:24 UTC
Resolved - Between 00:00 UTC & 16:00 UTC today, our Engineering team identified an issue affecting backup operations on Droplets. During this period, backups scheduled within this window may not have been created and may appear as missing.

Our team has taken necessary measures to resolve the issue, and we can confirm that the backup service has been restored and is now functioning normally. Upcoming scheduled backups should be performed as expected.

We sincerely apologize for any inconvenience this may have caused and appreciate your understanding. However, if you have any further questions or concerns, please create a support ticket for further analysis.

Received β€” 26 June 2026 ⏭ DigitalOcean Status - Incident History

Anthropic Inference Model Availability

Jun 27, 05:15 UTC
Resolved - Our Engineering team has resolved the issue that was causing HTTP 400 errors for requests to Anthropic models. Users should now be able to access Anthropic models without any issues.
If you continue to experience problems, please open a ticket with our Support team so we can investigate further.
We apologize for any inconvenience this may have caused.

Jun 27, 04:43 UTC
Monitoring - Our Engineering team has mitigated an issue with Anthropic models. Previously, users may have encountered 400 errors when attempting to use any Anthropic model.

Although the root cause of the issue is still being addressed by Anthropic, users should now be able to access and use Anthropic models again. We will continue to monitor the situation and provide updates if necessary. If you continue to experience problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused.

Received β€” 22 June 2026 ⏭ DigitalOcean Status - Incident History

SFO1 Network Maintenance

Jun 24, 12:30 UTC
Completed - The scheduled maintenance has been completed.

Jun 24, 09:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Jun 22, 09:40 UTC
Scheduled - Start: 2026-06-24 9:30 UTC
End: 2026-06-24 12:30 UTC

During the above window, our Networking team will be making changes to the core networking infrastructure to improve performance and scalability in the SFO1 region.

Expected impact:

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 SFO1 region. We will endeavor to minimize any such impact.

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

Received β€” 19 June 2026 ⏭ DigitalOcean Status - Incident History

Monitoring Graphs in the Cloud Control Panel

Jun 19, 16:37 UTC
Resolved - 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.

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.

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

Jun 19, 14:50 UTC
Monitoring - 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.

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.

Jun 19, 14:00 UTC
Investigating - 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.

We apologize for the inconvenience caused. We'll update once we have more information

Received β€” 17 June 2026 ⏭ DigitalOcean Status - Incident History

Core Infrastructure Maintenance June 17, 2026, 09:00 UTC

Jun 17, 18:00 UTC
Completed - The scheduled maintenance has been completed.

Jun 17, 09:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Jun 17, 05:53 UTC
Scheduled - Core Infrastructure Maintenance

Start: 2025-06-17 09:00 UTC
End: 2025-06-17 18:00 UTC

During the above time, our Engineering Team will be performing maintenance to failover some internal databases from one cluster to another.

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.

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.

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 β€” 16 June 2026 ⏭ DigitalOcean Status - Incident History

Intermittent 500 Errors on Serverless/GenAI Inference API

Jun 17, 00:29 UTC
Resolved - The connectivity issues affecting our Serverless/GenAI Inference API have been fully resolved.
Our engineering teams successfully completed the connectivity restoration. All systems should be functioning normally, and the endpoint should be fully operational.

Jun 16, 23:29 UTC
Monitoring - 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.

Jun 16, 22:00 UTC
Investigating - We are actively investigating an issue causing elevated HTTP 500 error rates for customers utilizing our Serverless/GenAI Inference API.
Customer Impact: Customers making calls to the inference APIβ€”specifically targeting /v1/* endpointsβ€”will experience intermittent HTTP 500 errors and failed requests.

SGP1 Network Maintenance

Jun 18, 17:30 UTC
Completed - The scheduled maintenance has been completed.

Jun 18, 14:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Jun 16, 14:32 UTC
Scheduled - Start: 2026-06-18 14:30 UTC
End: 2026-06-18 17:30 UTC

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.

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

Received β€” 11 June 2026 ⏭ DigitalOcean Status - Incident History

DeepSeek V4 Pro is returning HTTP 429 "Rate limit exceeded"

Jun 11, 17:42 UTC
Resolved - This incident has been resolved.

Jun 11, 14:31 UTC
Identified - The issue has been identified and a fix is being implemented.

Jun 11, 14:30 UTC
Update - We are continuing to investigate this issue.

Jun 11, 14:24 UTC
Investigating - We are currently facing issues with Gradient AI DeepSeek V4 Pro is returning HTTP 429 "Rate limit exceeded"

Received β€” 8 June 2026 ⏭ DigitalOcean Status - Incident History

AMS2 Network Maintenance

Jun 10, 18:30 UTC
Completed - The scheduled maintenance has been completed.

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

Jun 8, 15:41 UTC
Scheduled - Start: 2026-06-10 15:30 UTC
End: 2026-06-10 18:30 UTC

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.

Expected impact:

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.

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

Received β€” 4 June 2026 ⏭ DigitalOcean Status - Incident History

DNS API Service

Jun 4, 11:47 UTC
Resolved - 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.

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.

If you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused.

Jun 4, 11:39 UTC
Monitoring - 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.

We are monitoring the situation closely and will share an update once the issue is resolved completely.

Jun 4, 11:32 UTC
Identified - 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.

We will post an update as soon as additional information is available.

Jun 4, 10:59 UTC
Update - 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.

We apologize for the inconvenience and will share more information as it becomes available.

Jun 4, 10:12 UTC
Investigating - 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.

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

Received β€” 28 May 2026 ⏭ DigitalOcean Status - Incident History

App Platform Deployments

May 29, 07:58 UTC
Resolved - 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.

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.

May 29, 01:58 UTC
Monitoring - 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.

We are closely monitoring the situation, and will post an update once we've confirmed this is fully resolved.

May 29, 00:14 UTC
Investigating - 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.

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

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

Received β€” 20 May 2026 ⏭ DigitalOcean Status - Incident History

Cloud Firewall

May 20, 13:03 UTC
Resolved - 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.

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 and appreciate your patience and understanding. However, if you continue to experience any issues, please create a support ticket for further analysis.

May 20, 12:43 UTC
Monitoring - Our engineering team has implemented a fix that affected the Cloud Firewall rules. Users should now be able to update their firewalls successfully.

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.

May 20, 12:08 UTC
Identified - Our engineering team identified an issue impacting Cloud Firewall Product. During this time, users may notice HTTP 500 errors when updating firewalls.

We apologize for the inconvenience and will share an update once more information is available.

Cloud Firewall

May 20, 07:48 UTC
Resolved - 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.

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

May 20, 07:15 UTC
Monitoring - 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.

We will provide a final update once we have verified that the issue is fully resolved.

May 20, 05:35 UTC
Investigating - 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.

We apologize for the inconvenience and appreciate your patience. We will continue to provide updates as we learn more.

❌