Company Logo

Is there an DigitalOcean outage?

DigitalOcean status: Minor Outage

Last checked: 7 minutes ago

Get notified about any outages, downtime or incidents for DigitalOcean and 1800+ other cloud vendors. Monitor 10 companies, for free.

Subscribe for updates

DigitalOcean outages and incidents

Outage and incident data over the last 30 days for DigitalOcean.

There have been 8 outages or incidents for DigitalOcean in the last 30 days.

Severity Breakdown:

Tired of searching for status updates?

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 Now

Components and Services Monitored for DigitalOcean

Outlogger tracks the status of these components for Xero:

API Active
Billing Active
Cloud Control Panel Active
Cloud Firewall Active
Community Active
DNS Active
Reserved IP Active
Support Center Performance Issues
WWW Active
Amsterdam Active
Bangalore Active
Frankfurt Active
Global Active
London Active
New York Active
San Francisco Active
Singapore Active
Sydney Active
Toronto Active
AMS3 Active
BLR1 Active
FRA1 Active
Global Active
NYC3 Active
SFO2 Active
SFO3 Active
SGP1 Active
SYD1 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
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
AMS3 Active
BLR1 Active
FRA1 Active
Global Active
LON1 Active
NYC1 Active
SFO3 Active
SGP1 Active
SYD1 Active
TOR1 Active
Global Active
NYC2 Active
TOR1 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
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
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
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
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
AMS3 Active
BLR1 Active
FRA1 Active
Global Active
NYC3 Active
SFO2 Active
SFO3 Active
SGP1 Active
SYD1 Active
AMS3 Active
FRA1 Active
Global Active
NYC3 Active
SFO3 Active
SGP1 Active
SYD1 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
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
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
Active
Amsterdam Active
Bangalore Active
Frankfurt Active
Global Active
London Active
New York Active
San Francisco Active
Singapore Active
Sydney Active
Toronto Active
Active
AMS3 Active
BLR1 Active
FRA1 Active
Global Active
NYC3 Active
SFO2 Active
SFO3 Active
SGP1 Active
SYD1 Active
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
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
Active
AMS3 Active
BLR1 Active
FRA1 Active
Global Active
LON1 Active
NYC1 Active
SFO3 Active
SGP1 Active
SYD1 Active
TOR1 Active
Active
Global Active
NYC2 Active
TOR1 Active
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
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
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
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
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
Active
AMS3 Active
BLR1 Active
FRA1 Active
Global Active
NYC3 Active
SFO2 Active
SFO3 Active
SGP1 Active
SYD1 Active
Active
AMS3 Active
FRA1 Active
Global Active
NYC3 Active
SFO3 Active
SGP1 Active
SYD1 Active
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
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

Latest DigitalOcean outages and incidents.

View the latest incidents for DigitalOcean and check for official updates:

Updates:

  • Time: June 27, 2024, 11:57 p.m.
    Status: Resolved
    Update: Our Engineering team has confirmed that this incident has been fully resolved. Thank you for your patience. If you continue to experience any problems, please open a ticket with our support team for further review.
  • Time: June 27, 2024, 11:22 p.m.
    Status: Monitoring
    Update: Our Engineering team has confirmed that the issue for Droplets with previously failed events has been remediated, and further events should now successfully complete. We are continuing to monitor this situation and will post an update as soon as the issue is fully resolved.
  • Time: June 27, 2024, 9:12 p.m.
    Status: Identified
    Update: Our Engineering team has completed deployment of the fix. No additional users should now experience event failures. Droplets that experienced failed events are now being remediated to fix their event state, so that future events can succeed normally. We will provide another update once the remediation step is complete.
  • Time: June 27, 2024, 8:54 p.m.
    Status: Identified
    Update: Beginning around 16:00 UTC, our Engineering team identified an uptick in event errors for Droplets that utilize a Reserved IP in multiple regions. A subset of users are experiencing errors in processing events, especially "power on", via both API and the Cloud Control Panel. Our team has identified the root cause of the issue and a fix is currently in progress. We will provide another update once the fix is confirmed.

Updates:

  • Time: June 26, 2024, 2:10 p.m.
    Status: Resolved
    Update: Our Engineering team has confirmed the full resolution of the issue impacting the Managed Kubernetes cluster creation. As of 12:18 UTC the functionality has been restored completely and users should be able to deploy new clusters via Cloud Control Panel and API. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
  • Time: June 26, 2024, 1:36 p.m.
    Status: Monitoring
    Update: Our Engineering team has deployed a fix for the issue impacting the Managed Kubernetes cluster creation across all regions. The impact has been mitigated and users should no longer experience any issues deploying new clusters via Cloud Control panel and API. We are monitoring the situation and will post an update once the incident is completely resolved.
  • Time: June 26, 2024, 12:05 p.m.
    Status: Investigating
    Update: Our Engineering team is investigating an issue impacting our Managed Kubernetes service in all regions. Beginning 11:10 UTC, users may have experienced errors while creating new clusters using Control panel and API. We apologize for the inconvenience and will share an update once we have more information.

Updates:

  • Time: June 19, 2024, 11:04 p.m.
    Status: Resolved
    Update: Our engineering team has resolved the issue with creating a monitoring alert in the Monitoring section of the Cloud Control Panel. Thank you for your patience. If you continue to experience any problems, please open a support ticket from within your account.
  • Time: June 19, 2024, 10:22 p.m.
    Status: Monitoring
    Update: Our Engineering team has implemented a fix regarding the issue with creating a monitoring alert in the Monitoring section of the Cloud Control Panel. We are monitoring the situation to ensure there is no recurrence. We will post another update once we confirm the issue is fully resolved.
  • Time: June 19, 2024, 7:25 p.m.
    Status: Investigating
    Update: Our Engineering team is investigating an issue impacting our Monitoring Alerts service. During this time, users may have been experiencing errors or unexpected delays while trying to create monitoring alerts via Cloud Control Panel. We apologize for the inconvenience and will post an update as soon as we have additional information.

Updates:

  • Time: June 18, 2024, 1:15 p.m.
    Status: Resolved
    Update: As of 13.10 UTC, our Engineering team has confirmed full resolution of networking in our SFO region. 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.
  • Time: June 18, 2024, 12:03 p.m.
    Status: Monitoring
    Update: Our Engineering team has confirmed that the fix implemented earlier was successful in mitigating the issue with connectivity in our SFO regions. Users should now be able to connect to their Droplet and Droplet-based services without any issues. At this time, all services should now be operating normally. We will monitor this incident for a short period of time to confirm full resolution.
  • Time: June 18, 2024, 10:25 a.m.
    Status: Identified
    Update: As of 09:40 UTC, our Engineering team has identified the cause and applied a fix to mitigate the connectivity issue impacting the entire SFO region. We are still looking into this failure, but users should be seeing improvements in reaching their Droplet and Droplet-based services. We'll continue to monitor the situation to confirm this incident is fully resolved and will post an update soon.
  • Time: June 18, 2024, 9:05 a.m.
    Status: Investigating
    Update: Our Engineering team is continuing to investigate the issue with connectivity in our SFO regions. During this time, users may encounter errors and connection timeouts for Droplet and Droplet-based resources in the SFO region. Our team is diligently working on identifying and mitigating the issue at the earliest. We regret any inconvenience caused and will post an update as additional information is available.
  • Time: June 18, 2024, 8:38 a.m.
    Status: Investigating
    Update: Our Engineering team is investigating an issue with connectivity in our SFO regions. During this time users may experience connection timeouts and errors for Droplet and Droplet-based resources. We apologize for the inconvenience and will share an update once we have more information.

Updates:

  • Time: June 17, 2024, 7:37 p.m.
    Status: Resolved
    Update: From 17:02 - 18:44 UTC, the Spaces API experienced availability dips. These dips caused Spaces bucket operations in SGP1 for a subset of users to experience latency or 503 errors. The fix implemented by our Engineering team has been monitored and availability for the Spaces API is stable. Users should be able to interact with their Spaces buckets successfully. If you continue to experience any issues, please reach out to the Support team from within your account.
  • Time: June 17, 2024, 7:07 p.m.
    Status: Monitoring
    Update: Our Engineering team has identified and implemented a fix for an issue impacting Spaces SGP1 region. We are now monitoring the situation closely and will post an update as soon as the issue is fully resolved. Thank you for your patience!
  • Time: June 17, 2024, 6:49 p.m.
    Status: Investigating
    Update: Our Engineering team is investigating an issue with spaces in SGP1 region. During this time, users may experience 503 errors while accessing bucket operations. We apologize for the inconvenience and will share an update once we have more information.

Check the status of similar companies and alternatives to DigitalOcean

Hudl
Hudl

Systems Active

OutSystems
OutSystems

Systems Active

Postman
Postman

Systems Active

Mendix
Mendix

Systems Active

Bandwidth
Bandwidth

Issues Detected

DataRobot
DataRobot

Systems Active

Grafana Cloud
Grafana Cloud

Systems Active

SmartBear Software
SmartBear Software

Systems Active

Test IO
Test IO

Systems Active

Copado Solutions
Copado Solutions

Systems Active

CircleCI
CircleCI

Systems Active

LaunchDarkly
LaunchDarkly

Systems Active

Frequently Asked Questions - DigitalOcean

Is there a DigitalOcean outage?
The current status of DigitalOcean is: Minor Outage
Where can I find the official status page of DigitalOcean?
The official status page for DigitalOcean is here
How can I get notified if DigitalOcean is down or experiencing an outage?
To get notified of any status changes to DigitalOcean, simply sign up to OutLogger's free monitoring service. OutLogger checks the official status of DigitalOcean every few minutes and will notify you of any changes. You can veiw the status of all your cloud vendors in one dashboard. Sign up here
What does DigitalOcean do?
Cloud hosting solutions designed for small and mid-sized businesses that are easy to use and can be expanded as needed.