- Level
- confirmed
- Worst impact
- Degraded
- Components
- BLR1, NYC1, NYC3, SGP1, SYD1
- Down Index
- 21of 100
What to do
Check whether you use DigitalOcean BLR1, NYC1, NYC3, SGP1 and 1 more. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 5h 41m it lasted.
Anything that failed between 2026-07-19 09:51 UTC and 2026-07-19 15:32 UTC may need a replay.Subscribe to DigitalOcean's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=digitalocean works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from DigitalOcean 5
- 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.
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
We are continuing to investigate this issue.
provider
- 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.
provider
- 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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-2e0a105826
Is DigitalOcean still down?
No, this incident was resolved 2026-07-19 15:32 UTC. For DigitalOcean's live state, see https://down.guide/digitalocean.
How long did it last?
5h 41m, from 2026-07-19 09:51 UTC to 2026-07-19 15:32 UTC, by the times DigitalOcean posted.
What was affected?
DigitalOcean named BLR1, NYC1, NYC3, SGP1 and 1 more.
What caused it?
DigitalOcean hasn't published a root cause. If it does, it shows here.
Where does this come from?
DigitalOcean's official status page, https://status.digitalocean.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.