Live / DigitalOcean / Incident
DigitalOcean: Networking in BLR1
DigitalOcean · digitalocean.comMinor incidentResolved2026-07-19 09:52 UTC
Public — what happened
Summary
DigitalOcean said that starting at 06:57 UTC on July 19, 2026, Droplets (its virtual servers) in the BLR1 region had trouble sending traffic out to the internet, which could cause timeouts or failed connections to outside services. At 08:27 UTC the company said it had traced the problem to upstream network connectivity and was working with its upstream providers on a fix. A fix was in place by 09:31 UTC, and DigitalOcean marked the incident resolved at 09:52 UTC.
Affected
BLR1
Timeline
- Started — 2026-07-19 06:57 UTC
- Investigating — 2026-07-19 06:57 UTC
- Identified — 2026-07-19 08:27 UTC
- Monitoring — 2026-07-19 09:31 UTC
- Resolved — 2026-07-19 09:52 UTC · 2h 54m after it started
With SquidGrid — where it starts on the route
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 seeCustomers 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