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: Sept. 27, 2024, 6:16 p.m.
    Status: Resolved
    Update: As of 17:05 UTC, our Engineering team has resolved the issue affecting new account sign-ups. Users should no longer experience errors and are now able to complete the sign-up process successfully. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
  • Time: Sept. 27, 2024, 5:23 p.m.
    Status: Monitoring
    Update: Our Engineering team has implemented a fix to resolve the issue affecting new account sign-ups. Users should no longer encounter errors and can now successfully sign up again. Our Engineering team is continuing to monitor the situation, and we will provide an update as soon as the issue is fully resolved.
  • Time: Sept. 27, 2024, 4:41 p.m.
    Status: Investigating
    Update: Our Engineering team is currently investigating an issue affecting registering for a new account at cloud.digitalocean.com. Since 00:00 UTC, some users may encounter errors and be unable to complete the registration process. We apologize for any inconvenience this may cause and will provide an update as soon as we have more information.

Updates:

  • Time: Sept. 26, 2024, 8:43 p.m.
    Status: Resolved
    Update: From 18:22 UTC to 19:13 UTC, users may have experienced issues or errors when attempting to create or modify DigitalOcean services deployed in the SYD1 region and also when attempting to create or manage Volumes globally. Our Engineering team has confirmed the full resolution of this issue. If you continue to experience problems, please open a ticket with our support team. Thank you for being so patient, and we apologize for any inconvenience.
  • Time: Sept. 26, 2024, 7:33 p.m.
    Status: Monitoring
    Update: Our Engineering team identified the issue and took quick action to mitigate the impact to the SYD1 control plane. Customers may have also encountered errors when attempting to create or manage Volumes globally during this time. Currently, users should no longer experience issues or errors when attempting to create or modify DigitalOcean services deployed in the SYD1 region. We are monitoring the situation closely and will post an update as soon as the issue is fully resolved.
  • Time: Sept. 26, 2024, 7:08 p.m.
    Status: Investigating
    Update: As of 18:24 UTC, our Engineering team is investigating an issue impacting the control plane in the SYD1 region. At this time customers may encounter errors when attempting to create or modify DigitalOcean services deployed in the SYD1 region. Connectivity to existing services should not be impacted. This is believed to be related to earlier network maintenance being carried out in the region: https://status.digitalocean.com/incidents/1sf8jl4s1sp4 We apologize for the inconvenience and will share an update once we have further information.

Updates:

  • Time: Oct. 4, 2024, 5:37 p.m.
    Status: Postmortem
    Update: ## **Incident Summary** On September 25, 2024 at 22:25 UTC, DigitalOcean experienced a reduction of datacenter capacity in SFO3 and impacted the availability of select DigitalOcean services. Due to a majority of the line cards rebooting at the same time on one of our core routers in SFO3, an inter-regional traffic interruption and traffic drop to the network backbone occurred. This issue impacted users of any DigitalOcean services in the SFO3 region, with a longer impact on select Managed Kubernetes Clusters \(DOKS\).  ‌ ## **Incident Details** _Networking_ * **Root Cause**: Several line cards rebooted at the same time on one of the core routers, due to hardware errors on the network device. * **Impact**: Datacenter traffic capacity to/from the backbone was reduced by half during this incident. Network connectivity to some DigitalOcean services was affected. * **Response**: All of the crashed line cards came online quickly, allowing network traffic to begin flowing again and the core router to become operational. _Specific Impact on DOKS_ * **Root Cause:** Due to the network issues from line card reboots, a number of DOKS fleet machines became unhealthy as guest networking failed to recover from the hardware fault. * **Impact:** Some customer clusters experienced connectivity issues and difficulty in accessing the K8s control plane until networking for the underlying nodes was restored. * **Response:** All affected nodes across the SFO3 region in the DOKS fleet were recycled. ## **Timeline of Events** Sep 25 22:21 - Large majority of line cards rebooted on the core router. Sep 25 22:24 - Line cards became online. Sep 25 22:25 - Network protocols started session establishment process. Sep 25 22:30 - Traffic on the affected core router was restored. Sep 25 22:50 - SFO3 control plane systems all reconnected and recovered.  Sep 25 23:07 - DOKS API servers degraded. Sep 25 23:59 - Some DOKS clusters in the SFO3 region could not be scraped. Several nodes were discovered to be in a “not ready” state. Sep 26 01:40 - All impacted DOKS nodes recycled and clusters are operational.  ## **Remediation Actions** DigitalOcean teams are working on multiple types of remediation to help prevent a similar incident from happening in the future.  DigitalOcean is working with the vendor support team for the devices to determine the root cause of the line card crash, as well as upgrading software on the core routers in the SFO3 region..  During the incident, engineers had to manually remediate affected nodes across the entire SFO3 DOKS fleet to restore service. Teams are exploring methods to reduce the need for manual action in the future, by increasing thresholds for automated remediation actions, such that service is restored as quickly as possible.
  • Time: Sept. 26, 2024, 2:45 a.m.
    Status: Resolved
    Update: From 22:25 to 22:50 UTC, users may have experienced network connectivity issues with all DigitalOcean services deployed in the SFO3 region. Additionally, from 22:25 until 01:40 UTC, users may have encountered network connectivity issues affecting their Managed Kubernetes clusters in the SFO3 region. Our Engineering team has fully resolved the issues impacting connectivity in the region, 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 caused.
  • Time: Sept. 26, 2024, 2:15 a.m.
    Status: Monitoring
    Update: Our Engineering team has implemented a fix to resolve the issue affecting networking connectivity with Managed Kubernetes clusters in the SFO3 region and is closely monitoring the situation. We will provide an update as soon as the issue is fully resolved.
  • Time: Sept. 26, 2024, 1:27 a.m.
    Status: Identified
    Update: Our Engineering team has identified the cause of the networking connectivity issues with Managed Kubernetes clusters in the SFO3 region and is actively working on rolling out a fix. Once we have additional information, we will share another update.
  • Time: Sept. 26, 2024, 12:38 a.m.
    Status: Investigating
    Update: We are continuing to investigate the network connectivity issue with Managed Kubernetes clusters. During this investigation, we have also identified an earlier period of network connectivity disruption affecting all services in the region, from 22:25 to 22:50 UTC. At this time, some Managed Kubernetes clusters may continue experiencing network connectivity issues, but all other services in the region should be accessible as normal.
  • Time: Sept. 25, 2024, 11:34 p.m.
    Status: Investigating
    Update: Our Engineering team is currently investigating issues with network connectivity for Managed Kubernetes clusters in the SFO3 region. During this time, some users may experience difficulties connecting to their Managed Kubernetes clusters, or connecting to other services from their clusters. We apologize for the inconvenience and will provide an update as soon as we have more information.

Updates:

  • Time: Sept. 25, 2024, 10:59 p.m.
    Status: Resolved
    Update: Our Engineering team has identified and resolved an issue that impacted the ability to resize Droplets via both the API and UI from 18:15 until 21:55 UTC. During this time, users might have experienced errors when attempting to resize their Droplets through the API or the UI. Additionally, in an effort to resolve the issue with resizes, a secondary issue affected all event processing and some API calls for Droplets and related services from 21:50 until 22:00 UTC. Swift action was taken by our Engineering team to restore full functionality, and now everything is operating normally. We apologize for any inconvenience this may have caused. If you have any questions or continue to experience issues, please reach out via a Support ticket on your account.

Updates:

  • Time: Sept. 25, 2024, 4:10 p.m.
    Status: Resolved
    Update: From 00:01 to 15:15 UTC, users may have experienced errors when attempting to resize their MongoDB Managed Database clusters. Our Engineering team has confirmed the full resolution of issue. Users should now be able to resize their MongoDB clusters normally. If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel.
  • Time: Sept. 25, 2024, 3:36 p.m.
    Status: Monitoring
    Update: Our Engineering team has implemented a fix to resolve the issues impacting the resizing of Managed Database Clusters. Users should now be able to resize their existing MongoDB clusters without any issues. We are actively monitoring the situation and will post an update as soon as the issue is fully resolved.
  • Time: Sept. 25, 2024, 3:14 p.m.
    Status: Investigating
    Update: Our Engineering team is investigating an issue with MongoDB Managed Databases. At this time, users may experience errors while attempting to resize their existing MongoDB clusters. We apologize for the inconvenience and will provide another update as soon as possible.

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.

Start monitoring now!

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.

Get Started for Free