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

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.