Network connectivity in BLR1
Final update
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.
Timeline
- Resolved · Nov 8, 15:15 UTC
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.
More from DigitalOcean
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 1609:48 UTC | Support Portal Service Disruption | minor | 11h 21m |
| Sep 910:47 UTC | Power Degradation impacting GPU Performance in ATL1 | minor | 1h 38m |
| Aug 2417:14 UTC | Cloud Control Panel and API | critical | 25h 50m |
| Aug 2305:11 UTC | Managed Databases Creation | minor | 9h 22m |
| Aug 2112:59 UTC | Container Registry and Spaces Accessibility | minor | 1h 53m |
| Aug 1911:10 UTC | Major Service Interruption in MKC1 | critical | 8h 25m |
From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.