DigitalOcean Services Status

Investigating - Our Engineering team is investigating reports that alerts are not received when alerts are configured with tags. Users may not receive email notification of alerts when using tags, although resources specified by name are still monitored and receiving alerts properly.

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

Feb 19, 2025 - 20:36 UTC
API Operational
Billing Operational
Cloud Control Panel Operational
Cloud Firewall Operational
Community Operational
DNS Operational
Support Center Operational
Reserved IP Operational
WWW Operational
GenAI Platform Operational
App Platform Operational
Global Operational
Amsterdam 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
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
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
NYC2 Operational
TOR1 Operational
Managed Databases Operational
Global Operational
AMS3 Operational
BLR1 Operational
FRA1 Operational
LON1 Operational
NYC1 Operational
NYC2 Operational
NYC3 Operational
SFO2 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
TOR1 Operational
Monitoring Degraded Performance
Global Degraded Performance
AMS2 Operational
AMS3 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
BLR1 Operational
FRA1 Operational
LON1 Operational
NYC1 Operational
NYC2 Operational
NYC3 Operational
SFO1 Operational
SFO2 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
TOR1 Operational
Kubernetes Operational
Global Operational
AMS3 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
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
FRA1 Operational
NYC3 Operational
SFO2 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
BLR1 Operational
Spaces CDN Operational
Global Operational
AMS3 Operational
FRA1 Operational
NYC3 Operational
SFO3 Operational
SGP1 Operational
SYD1 Operational
VPC Operational
Global Operational
AMS2 Operational
AMS3 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
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
Past Incidents
Feb 19, 2025

Unresolved incident: Monitoring Alerts with tags.

Feb 18, 2025

No incidents reported.

Feb 17, 2025

No incidents reported.

Feb 16, 2025

No incidents reported.

Feb 15, 2025

No incidents reported.

Feb 14, 2025

No incidents reported.

Feb 13, 2025

No incidents reported.

Feb 12, 2025

No incidents reported.

Feb 11, 2025
Resolved - Our Engineering team has confirmed the full resolution of the issue affecting the Spaces Buckets creation and App Platform deployment in BLR1 region . All our services in the region should now be functioning normally.

Users should no longer experience any issues with the creation of Spaces Buckets and App Platform application creations and deployments.

If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel. Thank you for your patience and we apologize for any inconvenience.

Feb 11, 11:44 UTC
Monitoring - Our engineering team has identified the cause and deployed a fix for the issue with Spaces Buckets creation and App Platform deployment in BLR1 region.

Spaces Buckets and App Platform application creations and deployments should now function as expected.

We are actively monitoring the situation and will provide an update once we confirm the incident is completely resolved.

Feb 11, 10:38 UTC
Identified - Our Engineering team has identified the cause of the issue affecting the creation of Spaces Buckets and App Platform application creations and deployments in BLR1. The impact is mitigated by implementing a temporary fix and is actively working on a permanent fix.

Users should now be able to create Spaces Bucket and deploy App Platform application in the BLR1 region.

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

Feb 11, 10:18 UTC
Investigating - As of 08:32 UTC, our Engineering team is investigating an issue affecting the creation of Spaces Buckets in BLR1. During this period, users may also have experienced errors in DigitalOcean Container Registry creations and App Platform application creations and deployments.

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

Feb 11, 09:07 UTC
Feb 10, 2025

No incidents reported.

Feb 9, 2025

No incidents reported.

Feb 8, 2025

No incidents reported.

Feb 7, 2025

No incidents reported.

Feb 6, 2025
Resolved - From 00:04 UTC to 00:41 UTC, users experienced issues accessing the Cloud Control Panel and API as well as experienced event failures.

Our Engineering team has resolved the issue, and Cloud Control Panel, API and events should now be functioning normally.

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

Feb 6, 01:29 UTC
Monitoring - Our Engineering team has implemented a fix regarding the issue impacting our Cloud Control Panel and API. We are monitoring the situation to ensure there is no recurrence.

We will post another update once we confirm the issue is fully resolved.

Feb 6, 01:01 UTC
Update - We are continuing to investigate this issue.
Feb 6, 00:37 UTC
Update - We are continuing to investigate this issue.
Feb 6, 00:27 UTC
Investigating - As of 00:16 UTC, our Engineering team is investigating an issue impacting our Cloud Control Panel and API.

During this time, users will experience errors when trying to use the public API at api.digitalocean.com or while accessing our Cloud Control Panel at https://cloud.digitalocean.com. Users may also see issues with processing Droplet and Kubernetes cluster creations along with Droplet based events.

We are now confirming the full impact. We regret any inconvenience and will let you know as soon as more information is available.

Feb 6, 00:26 UTC
Feb 5, 2025
Resolved - Our Engineering team identified an issue affecting Reserved IP assignments across all regions. From 00:26 to 03:26 UTC, users may have experienced issues with assigning Reserved IPs to Droplets.

A fix has been implemented and as of 03:26 UTC, all Reserved IP assignments have been successful. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.

Feb 5, 04:21 UTC
Resolved - Our Engineering Team has confirmed that the issue affecting GenAI agents in the Cloud has been fully resolved. Users should no longer see the "Failed to Update" banner and all functionality remains unaffected.

If you continue to experience any problems, please reach out to our support team by opening a ticket from within your Cloud Control Panel.

Feb 5, 03:26 UTC
Monitoring - Our Engineering team has implemented a fix to resolve the issues impacting GenAI agents in the Cloud. The banner should no longer appear, and functionality remains unaffected.

We are actively monitoring the situation and will post an update as soon as the issue is fully resolved.

Feb 5, 02:09 UTC
Identified - Our Engineering Team has identified an issue with GenAI agents where some customers may see a "Failed to Update" banner in the Cloud. Despite this message, customers can still update their images and use them as normal.

We apologize for the inconvenience and will provide another update as soon as possible.

Feb 4, 20:41 UTC