DigitalOcean Services Status

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 07, 2026 - 18:00 UTC
Scheduled - Start: 2026-04-07 18:00 UTC
End: 2026-04-08 00:00 UTC

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.

Expected Impact:

We do not anticipate any service disruptions during this window. Your existing databases and workloads will continue to run normally without interruption.

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.

If an unexpected issue arises, we will work to keep any impact to a minimum and may revert the changes if required.

If you have any questions related to this event, please open a ticket from your cloud support page: https://cloudsupport.digitalocean.com/s/createticket

Apr 7, 2026 18:00 - Apr 8, 2026 00:00 UTC
API Operational
Billing Operational
BYOIP Operational
Cloud Control Panel Operational
Cloud Firewall Operational
Community Operational
DNS Operational
Support Center Operational
Reserved IP Operational
WWW Operational
Gradient AI 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 Under Maintenance
Global Operational
AMS3 Under Maintenance
ATL1 Under Maintenance
BLR1 Operational
FRA1 Operational
LON1 Under Maintenance
NYC1 Under Maintenance
NYC2 Under Maintenance
NYC3 Operational
SFO2 Operational
SFO3 Under Maintenance
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
ATL1 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
CSPM Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Apr 7, 2026
Resolved - 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.

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

Apr 7, 17:49 UTC
Resolved - 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.
Apr 7, 15:50 UTC
Identified - We are currently investigating reports of elevated latency affecting requests to this model when using Serverless Inference and Agents.

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.

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.

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.

Apr 7, 12:55 UTC
Investigating - Serverless inference for alibaba-qwen3-32b (Qwen 3 32B) in tor1 is experiencing high error rates starting at 10:46 UTC.
Apr 7, 12:49 UTC
Apr 6, 2026
Resolved - This incident has been resolved.
Apr 6, 18:02 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 6, 15:15 UTC
Investigating - Our Engineering team is investigating an issue with Serverless inference.

At this time, users may experience high error rates for open source models (llama 3.3 70b).

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

Apr 6, 12:28 UTC
Apr 5, 2026

No incidents reported.

Apr 4, 2026

No incidents reported.

Apr 3, 2026

No incidents reported.

Apr 2, 2026

No incidents reported.

Apr 1, 2026

No incidents reported.

Mar 31, 2026

No incidents reported.

Mar 30, 2026

No incidents reported.

Mar 29, 2026

No incidents reported.

Mar 28, 2026

No incidents reported.

Mar 27, 2026
Completed - The scheduled maintenance has been completed.
Mar 27, 23:16 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 27, 19:00 UTC
Scheduled - Start: 2026-03-27 19:00 UTC
End: 2026-03-28 02:00 UTC

During the above window, our Engineering team will perform maintenance on core MongoDB services in the FRA1 region 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.

Expected Impact:

We do not anticipate any service disruptions during this window. Your existing databases and workloads will continue to run normally without interruption.

In the event that an unexpected issue occurs, administrative actions, such as creating, deleting, or scaling Managed MongoDB databases in the FRA1 region, may experience delays.

If an unexpected issue arises, we will work to keep any impact to a minimum and may revert the changes if required.

If you have any questions related to this event, please open a ticket from your cloud support page: https://cloudsupport.digitalocean.com/s/createticket

Mar 25, 19:01 UTC
Mar 26, 2026

No incidents reported.

Mar 25, 2026

No incidents reported.

Mar 24, 2026

No incidents reported.