Last checked: 11 seconds ago
Get notified about any outages, downtime or incidents for DigitalOcean and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for DigitalOcean.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
Component | Status |
---|---|
API | Active |
Billing | Active |
Cloud Control Panel | Active |
Cloud Firewall | Active |
Community | Active |
DNS | Active |
Reserved IP | Active |
Support Center | Performance Issues |
WWW | Active |
App Platform | Active |
Amsterdam | Active |
Bangalore | Active |
Frankfurt | Active |
Global | Active |
London | Active |
New York | Active |
San Francisco | Active |
Singapore | Active |
Sydney | Active |
Toronto | Active |
Container Registry | Active |
AMS3 | Active |
BLR1 | Active |
FRA1 | Active |
Global | Active |
NYC3 | Active |
SFO2 | Active |
SFO3 | Active |
SGP1 | Active |
SYD1 | Active |
Droplets | Active |
AMS2 | Active |
AMS3 | Active |
BLR1 | Active |
FRA1 | Active |
Global | Active |
LON1 | Active |
NYC1 | Active |
NYC2 | Active |
NYC3 | Active |
SFO1 | Active |
SFO2 | Active |
SFO3 | Active |
SGP1 | Active |
SYD1 | Active |
TOR1 | Active |
Event Processing | Active |
AMS2 | Active |
AMS3 | Active |
BLR1 | Active |
FRA1 | Active |
Global | Active |
LON1 | Active |
NYC1 | Active |
NYC2 | Active |
NYC3 | Active |
SFO1 | Active |
SFO2 | Active |
SFO3 | Active |
SGP1 | Active |
SYD1 | Active |
TOR1 | Active |
Functions | Active |
AMS3 | Active |
BLR1 | Active |
FRA1 | Active |
Global | Active |
LON1 | Active |
NYC1 | Active |
SFO3 | Active |
SGP1 | Active |
SYD1 | Active |
TOR1 | Active |
GPU Droplets | Active |
Global | Active |
NYC2 | Active |
TOR1 | Active |
Kubernetes | Active |
AMS3 | Active |
BLR1 | Active |
FRA1 | Active |
Global | Active |
LON1 | Active |
NYC1 | Active |
NYC3 | Active |
SFO2 | Active |
SFO3 | Active |
SGP1 | Active |
SYD1 | Active |
TOR1 | Active |
Load Balancers | Active |
AMS2 | Active |
AMS3 | Active |
BLR1 | Active |
FRA1 | Active |
Global | Active |
LON1 | Active |
NYC1 | Active |
NYC2 | Active |
NYC3 | Active |
SFO1 | Active |
SFO2 | Active |
SFO3 | Active |
SGP1 | Active |
SYD1 | Active |
TOR1 | Active |
Managed Databases | Active |
AMS3 | Active |
BLR1 | Active |
FRA1 | Active |
Global | Active |
LON1 | Active |
NYC1 | Active |
NYC2 | Active |
NYC3 | Active |
SFO2 | Active |
SFO3 | Active |
SGP1 | Active |
SYD1 | Active |
TOR1 | Active |
Monitoring | Active |
AMS2 | Active |
AMS3 | Active |
BLR1 | Active |
FRA1 | Active |
Global | Active |
LON1 | Active |
NYC1 | Active |
NYC2 | Active |
NYC3 | Active |
SFO1 | Active |
SFO2 | Active |
SFO3 | Active |
SGP1 | Active |
SYD1 | Active |
TOR1 | Active |
Networking | Active |
AMS2 | Active |
AMS3 | Active |
BLR1 | Active |
FRA1 | Active |
Global | Active |
LON1 | Active |
NYC1 | Active |
NYC2 | Active |
NYC3 | Active |
SFO1 | Active |
SFO2 | Active |
SFO3 | Active |
SGP1 | Active |
SYD1 | Active |
TOR1 | Active |
Spaces | Active |
AMS3 | Active |
BLR1 | Active |
FRA1 | Active |
Global | Active |
NYC3 | Active |
SFO2 | Active |
SFO3 | Active |
SGP1 | Active |
SYD1 | Active |
Spaces CDN | Active |
AMS3 | Active |
FRA1 | Active |
Global | Active |
NYC3 | Active |
SFO3 | Active |
SGP1 | Active |
SYD1 | Active |
Volumes | Active |
AMS2 | Active |
AMS3 | Active |
BLR1 | Active |
FRA1 | Active |
Global | Active |
LON1 | Active |
NYC1 | Active |
NYC2 | Active |
NYC3 | Active |
SFO1 | Active |
SFO2 | Active |
SFO3 | Active |
SGP1 | Active |
SYD1 | Active |
TOR1 | Active |
VPC | Active |
AMS2 | Active |
AMS3 | Active |
BLR1 | Active |
FRA1 | Active |
Global | Active |
LON1 | Active |
NYC1 | Active |
NYC2 | Active |
NYC3 | Active |
SFO1 | Active |
SFO2 | Active |
SFO3 | Active |
SGP1 | Active |
SYD1 | Active |
TOR1 | Active |
View the latest incidents for DigitalOcean and check for official updates:
Description: Our Engineering team has confirmed the full resolution of this incident. From 20:14 to 22:03 UTC, users may have experienced errors when connecting to their Apps or with their Apps connecting to other services, as well as delays in deploying Apps. Users should now be able to connect to their Apps normally, and any delayed deployments should complete successfully. If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel.
Status: Resolved
Impact: Minor | Started At: Sept. 19, 2024, 9:07 p.m.
Description: From 21:35 to 00:45 UTC, users may have experienced networking connectivity issues in our SGP1 region, which impacted a subset of DigitalOcean services. Our Engineering team has confirmed the full resolution of the issue. Users should be able to access all resources as normal. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Status: Resolved
Impact: Minor | Started At: Sept. 18, 2024, 11:10 p.m.
Description: From 14:15 to 17:53 UTC, users may have experienced delays for App Platform deployments, as well as latency and errors when fetching Spaces endpoint information and toggling the CDN for a Spaces Bucket, due to an upstream provider issue. Our Engineering team has confirmed the full resolution of the issue with the upstream provider. Users should now be able to deploy to App Platform and manage their Spaces Buckets as normal. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Status: Resolved
Impact: Minor | Started At: Sept. 18, 2024, 3:02 p.m.
Description: Our Engineering team identified an issue with accessing Cloud Panel and Application deployment which is due to the increased level of HTTP 499 errors rates at Upstream Provider end. From 04:21 - 06:06 UTC, users may have experienced issues while accessing Cloud Panel and Application deployments. Our Upstream provider and the Engineering team closely worked together to resolve the issue. The impact has completely subsided and users should no longer see any issues with the impacted services. If you continue to experience problems, please open a ticket with our support team from your Cloud Control Panel. Thank you for your patience, and we apologize for any inconvenience.
Status: Resolved
Impact: None | Started At: Sept. 16, 2024, 7 a.m.
Description: From 22:03 September 11 to 00:13 September 12 UTC, users may have experienced failures with creating Droplets in the LON1 region. Our Engineering team has confirmed resolution of this issue with users now being able to create Droplets in LON1. Thank you for your patience. If you continue to experience any problems, please open a support ticket from within your account.
Status: Resolved
Impact: Minor | Started At: Sept. 11, 2024, 11:45 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.