A Network Disruption in BLR1 Region Impacted Multiple Products (Resolved)

What to do

• Check whether you use DigitalOcean Bangalore, BLR1, BLR1, BLR1 and 4 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 0m it lasted.

  Anything that failed between 2026-10-03 14:51 UTC and 2026-10-03 14:51 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 1

1. resolvedOct 3, 2026, 2:51 PM UTC

   From 11:59 UTC to 13:02 UTC on October 3, 2026, a networking disruption in our BLR1 region affected multiple products, including Monitoring, App Platform, Managed Databases, Functions, Load Balancers, Spaces, and the Cloud Control Panel. During this period, some users experienced degraded connectivity, increased latency, or intermittent errors when accessing resources in the region. Multiple network paths operated by our upstream connectivity providers were unavailable, including redundant paths intended to maintain connectivity during a disruption. Traffic shifted to a remaining link with insufficient capacity to handle the full load, resulting in network saturation and the connectivity issues described above. Our Engineering and Network teams worked closely with our upstream providers to restore normal routing and connectivity. All affected services have since returned to normal operation. We apologize for the disruption and its impact on your work. If you continue to experience unexpected behavior, please open a support ticket so our team can investigate and assist you.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.