Last checked: 3 minutes 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: From 15:20 - 16:10 UTC, our Engineering team observed an issue with network connectivity in the BLR1 region. During this time, users might have experienced varying amounts of packet loss and high latency with network connections going in or out of the BLR1 region, resulting in issues connecting to DigitalOcean services. As of 16:10 UTC, the impact has subsided and users should no longer be facing network connectivity issues. We apologize for the inconvenience and if you are still experiencing issues or have any additional questions then please open a support ticket from within your account.
Status: Resolved
Impact: None | Started At: Sept. 11, 2024, 5:22 p.m.
Description: From 18:23 to 19:21 UTC, users were unable to complete registration of new cloud.digitalocean.com accounts, due to an upstream outage. This issue is now fully resolved and users should be able to sign up normally. We apologize for the inconvenience and invite users to retry any failed attempts. If you continue to experience issues or have any questions, please reach out to Support from within your account.
Status: Resolved
Impact: Minor | Started At: Sept. 10, 2024, 7:18 p.m.
Description: Our Engineering team identified a networking issue with our upstream provider in the SGP1 region. From 00:25 to 04:00 UTC, users may have experienced connectivity issues to DockerHub from Droplets, App Platform and Managed Kubernetes in the SGP1 region. Our Engineering team has confirmed there is no longer any impact and connectivity should be restored for all customers. We apologize for the inconvenience. If you continue to experience any issues, please open a support ticket from within your account.
Status: Resolved
Impact: None | Started At: Sept. 10, 2024, 5:11 a.m.
Description: From 17:04 UTC to 21:43 UTC, users may not have seen the option to resize an attached Block Storage Volume via the Cloud Control Panel, or may have encountered errors when attempting to resize attached Volumes via the API. Our Engineering team has confirmed the resolution of the issue and Volume resizes should now be functioning normally in all regions. 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. 9, 2024, 9:15 p.m.
Description: Our Engineering team has resolved the issue with Managed Kubernetes clusters in the SFO3 region. All services should now be 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.
Status: Resolved
Impact: Minor | Started At: Aug. 30, 2024, 1:37 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.