DigitalOcean Status

12 min read Original article ↗

All Systems Operational

Cloud Control Panel Operational

Cloud Firewall Operational

Support Center Operational

Agentic Inference Cloud Operational

Agent Runtime Operational

Inference Operational

ADK Operational

Knowledge Bases Operational

Guardrails Operational

Model Services Operational

App Platform Operational

Global Operational

Amsterdam Operational

Atlanta Operational

Bangalore Operational

Frankfurt Operational

London Operational

New York Operational

San Francisco Operational

Singapore Operational

Sydney Operational

Toronto Operational

Container Registry Operational

Global Operational

AMS3 Operational

BLR1 Operational

FRA1 Operational

NYC3 Operational

SFO2 Operational

SFO3 Operational

SGP1 Operational

SYD1 Operational

Droplets Operational

Global Operational

AMS2 Operational

AMS3 Operational

ATL1 Operational

BLR1 Operational

FRA1 Operational

LON1 Operational

NYC1 Operational

NYC2 Operational

NYC3 Operational

SFO1 Operational

SFO2 Operational

SFO3 Operational

SGP1 Operational

SYD1 Operational

TOR1 Operational

Event Processing Operational

Global Operational

AMS2 Operational

AMS3 Operational

ATL1 Operational

BLR1 Operational

FRA1 Operational

LON1 Operational

NYC1 Operational

NYC2 Operational

NYC3 Operational

SFO1 Operational

SFO2 Operational

SFO3 Operational

SGP1 Operational

SYD1 Operational

TOR1 Operational

Functions Operational

Global Operational

AMS3 Operational

BLR1 Operational

FRA1 Operational

LON1 Operational

NYC1 Operational

SFO3 Operational

SGP1 Operational

SYD1 Operational

TOR1 Operational

GPU Droplets Operational

Global Operational

ATL1 Operational

NYC2 Operational

TOR1 Operational

Managed Databases Operational

Global Operational

AMS3 Operational

ATL1 Operational

BLR1 Operational

FRA1 Operational

LON1 Operational

NYC1 Operational

NYC2 Operational

NYC3 Operational

SFO2 Operational

SFO3 Operational

SGP1 Operational

SYD1 Operational

TOR1 Operational

Monitoring Operational

Global Operational

AMS2 Operational

AMS3 Operational

ATL1 Operational

BLR1 Operational

FRA1 Operational

LON1 Operational

NYC1 Operational

NYC2 Operational

NYC3 Operational

SGP1 Operational

SFO1 Operational

SFO2 Operational

SFO3 Operational

SYD1 Operational

TOR1 Operational

Networking Operational

Global Operational

AMS2 Operational

AMS3 Operational

ATL1 Operational

BLR1 Operational

FRA1 Operational

LON1 Operational

NYC1 Operational

NYC2 Operational

NYC3 Operational

SFO1 Operational

SFO2 Operational

SFO3 Operational

SGP1 Operational

SYD1 Operational

TOR1 Operational

Network File Storage Operational

Kubernetes Operational

Global Operational

AMS3 Operational

ATL1 Operational

BLR1 Operational

FRA1 Operational

LON1 Operational

NYC1 Operational

NYC3 Operational

SFO2 Operational

SFO3 Operational

SGP1 Operational

SYD1 Operational

TOR1 Operational

Load Balancers Operational

Global Operational

AMS2 Operational

AMS3 Operational

ATL1 Operational

BLR1 Operational

FRA1 Operational

LON1 Operational

NYC1 Operational

NYC2 Operational

NYC3 Operational

SFO1 Operational

SFO2 Operational

SFO3 Operational

SGP1 Operational

SYD1 Operational

TOR1 Operational

Spaces Operational

Global Operational

AMS3 Operational

ATL1 Operational

BLR1 Operational

FRA1 Operational

NYC3 Operational

SFO2 Operational

SFO3 Operational

SGP1 Operational

SYD1 Operational

LON1 Operational

Spaces CDN Operational

Global Operational

AMS3 Operational

ATL1 Operational

FRA1 Operational

NYC3 Operational

SFO3 Operational

SGP1 Operational

SYD1 Operational

LON1 Operational

VPC Operational

Global Operational

AMS2 Operational

AMS3 Operational

ATL1 Operational

BLR1 Operational

FRA1 Operational

LON1 Operational

NYC1 Operational

NYC2 Operational

NYC3 Operational

SFO1 Operational

SFO2 Operational

SFO3 Operational

SGP1 Operational

SYD1 Operational

TOR1 Operational

Volumes Operational

Global Operational

AMS2 Operational

AMS3 Operational

ATL1 Operational

BLR1 Operational

FRA1 Operational

LON1 Operational

NYC1 Operational

NYC2 Operational

NYC3 Operational

SFO1 Operational

SFO2 Operational

SFO3 Operational

SGP1 Operational

SYD1 Operational

TOR1 Operational

Operational

Degraded Performance

Partial Outage

Major Outage

Maintenance

Scheduled Maintenance

NYC2 Network Maintenance Jul 7, 2026 10:30-15:30 UTC

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


Posted on Jul 04, 2026 - 09:05 UTC

Past Incidents

Jul 6, 2026

No incidents reported today.

Jul 5, 2026

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 5, 00:53 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, 23:18 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.
Jul 4, 22:13 UTC

Jul 4, 2026

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, 15:10 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.


Jul 4, 14:42 UTC

Jul 3, 2026

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, 08:20 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, 06:08 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 3, 02:28 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.


Jul 2, 22:04 UTC

Jul 2, 2026

Resolved - This incident has been resolved, and our teams continue to monitor the results. If you experience any further issues, please contact support.
Jul 2, 03:38 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, 08:39 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.


Jul 1, 06:25 UTC

Jul 1, 2026

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, 16:28 UTC

Update - We are continuing to investigate this issue.
Jul 1, 12:15 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.


Jul 1, 11:35 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, 13:28 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, 12:43 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.


Jul 1, 11:13 UTC

Jun 30, 2026

No incidents reported.

Jun 29, 2026

No incidents reported.

Jun 28, 2026

No incidents reported.

Jun 27, 2026

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.


Jun 27, 18:24 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, 05:15 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.


Jun 27, 04:43 UTC

Jun 26, 2026

No incidents reported.

Jun 25, 2026

No incidents reported.

Jun 24, 2026

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

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 24, 09:30 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


Jun 22, 09:40 UTC

Jun 23, 2026

No incidents reported.

Jun 22, 2026

No incidents reported.