DigitalOcean outage, July 2026: Block Storage Volume NYC1, NYC3, SGP1, SYD1 and BLR1
DigitalOcean reported and resolved an incident: Block Storage Volume NYC1, NYC3, SGP1, SYD1 and BLR1. It lasted 5.7 hours.
OKResolved
From DigitalOcean's official status page, in their words.
What happened
- Started
- Resolved
- Duration
- 5.7 hours
- Impact
- minor
- Affected
- BLR1, NYC1, NYC3, SGP1, SYD1
- Investigating
- Identifiednot posted
- Monitoring
- Resolved
Why it happened
DigitalOcean has not given a cause in its updates. We never guess one.
How it was resolved
Our Engineering team has confirmed that the issue regarding volume attachment to Droplets in the NYC1, NYC3, SGP1, SYD1, and BLR1 regions has been fully resolved, and all services are now operating normally. If you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused.
Timeline
Oldest first, from the first notice to the resolution. From DigitalOcean's official status page, in their words.
- investigating
Our Engineering team is investigating an issue with attaching volume to the droplets in the NYC1, NYC3, SGP1, SYD1 and BLR1 regions. During this time you may experience an issue with attaching volume to the Droplet(s). We apologize for the inconvenience and will share an update once we have more information.
- investigating
We are continuing to investigate this issue.
- investigating
We are continuing to investigate this issue.
- monitoring
Our Engineering team has identified the root cause of the issue preventing volume attachments to Droplets in NYC1, NYC3, SGP1, SYD1, and BLR1 and has successfully implemented a fix. You should now be able to attach volumes to your Droplet(s) without encountering any further errors or issues. We are actively monitoring the situation to ensure the fix remains effective and will provide another update once the issue has been fully resolved.
- resolved
Our Engineering team has confirmed that the issue regarding volume attachment to Droplets in the NYC1, NYC3, SGP1, SYD1, and BLR1 regions has been fully resolved, and all services are now operating normally. If you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused.
What this means for a business (and what to check now)
- Retry anything that failed during the 5.7 hours.
- Enter any payments, bookings or jobs you took another way.
- If a deadline fell inside the window, keep this page as your record of the outage.
The full guide: what to do when a service you rely on is down
Other DigitalOcean incidents
- Kubernetes Cluster Management Operations, resolved after 3.7 hours
- App Platform Deployments, resolved after 1 minute
- DNS Resolution for Managed Kubernetes, resolved after 1.5 hours
- VPC Networking Availability, resolved after 1.6 hours
- A Network Disruption in BLR1 Region Impacted Multiple Products (Resolved), resolved after 1 minute
Hear about the next DigitalOcean incident as it starts
Free email alerts when the official status changes, with what to do while it is down.