Network Connectivity in BLR1
Summary
Our Engineering team has confirmed the full resolution of the networking connectivity issue affecting the BLR1 region. Users should experience expected performance when accessing Droplets and other services. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Impact
minor
Timeline
[resolved] From 13:50 to 14:15 UTC, our Engineering team observed an issue with an upstream provider impacting network connectivity in the BLR1 region. During this time, users may have experienced increase in latency or packet loss when accessing Droplets and Droplet-based services, like Managed Kubernetes and Database Clusters in BLR1 region. The impact has now subsided and as of 14:15 UTC, users should already experience better performance when accessing Droplets and other services. We apologize for the inconvenience. If you are still experiencing any problems or have additional questions, then please open a support ticket within your account.
via statuspage[monitoring] Our Engineering team is still observing intermittent issues impacting network connectivity in the BLR1 region. Between 17:28 and 17:37 UTC, the team observed a major connectivity loss to this region and took immediate steps to reroute traffic via a different upstream provider to alleviate the impact. The issue BLR1 is experiencing at the moment stems from a broader Internet issue. Network accessibility in the region has improved as of now, and users should already experience better performance when accessing Droplets and other services. We are closely monitoring the situation to ensure stability. We appreciate your patience and will provide an update once the issue is fully confirmed as resolved.
via statuspage[resolved] Our Engineering team has confirmed the full resolution of the networking connectivity issue affecting the BLR1 region. Users should experience expected performance when accessing Droplets and other services. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
via statuspageLessons Learned
⚠DigitalOcean has experienced 94 incidents in the past year. This frequency suggests systemic reliability challenges that may warrant additional monitoring.
📊Incidents related to network, dns, database, authentication have occurred 299 times across all providers in the past year. This is one of the most common failure categories in cloud infrastructure.
💡This incident is categorized as: DNS Failure, Database Overload, Network / Routing, Authentication Issue. Consider implementing preventive measures specific to this failure category.
Similar Incidents
Block Storage Volume NYC1 and NYC3
DigitalOcean · Jul 19, 2026
Networking in BLR1
DigitalOcean · Jul 19, 2026
Some users are unable to access Codex
OpenAI · Jul 18, 2026
Elevated errors across Fable 5
Anthropic · Jul 17, 2026
Service impact: Inaccurate Estimated Billing Data
AWS · Jul 17, 2026