Live  /  DigitalOcean  /  Incident

DigitalOcean: Block Storage Volume NYC1, NYC3, SGP1, SYD1 and BLR1

DigitalOcean · digitalocean.comMinor incidentResolved2026-07-19 15:32 UTC
Public — what happened

Summary

DigitalOcean reported a problem on July 19, 2026, starting at 09:51 UTC, in which customers in its NYC1, NYC3, SGP1, SYD1 and BLR1 regions could have trouble connecting block storage volumes to their Droplets (virtual servers). The company said its engineers found the underlying cause and put a fix in place by 14:52 UTC, though it did not describe what that cause was. After a period of watching the fix, DigitalOcean declared the issue fully resolved at 15:32 UTC.

Affected

BLR1, NYC1, NYC3, SGP1, SYD1

As listed on DigitalOcean’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach DigitalOcean against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for DigitalOcean: paths off baseline right now, where on the route conditions change, and its full incident track record.

Included with any paid plan.

Open the DigitalOcean report →

More from DigitalOcean

The full archive is on the DigitalOcean status & history page.

Related: DigitalOcean status & history. SquidGrid is not affiliated with DigitalOcean.