Reserved IP routing in TOR1
Jul 16, 13:39 UTCJul 16, 17:24 UTC
Duration
3h 45m
Impact
Minor
Root cause
Network
DigitalOcean, 90 days
30 incidents
Affected
Reserved IPTOR1Networking - TOR1
Final update
Our Engineering team has confirmed that the underlying issue affecting Reserved IP routing in the TOR1 region has been fully resolved, and services are now operating normally. If you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused.
Timeline
- Resolved · Jul 16, 17:24 UTC
Our Engineering team has confirmed that the underlying issue affecting Reserved IP routing in the TOR1 region has been fully resolved, and services are now operating normally. If you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused.
- Monitoring · Jul 16, 17:01 UTC
Our Engineering team has implemented a fix for the issue affecting Reserved IP routing in the TOR1 region, and we are currently monitoring the results. Inbound and outbound traffic to and from Reserved IPs in TOR1 should now be restored. If you reassigned your Reserved IP as a workaround and are still experiencing issues, please reach out to our support team. We will continue to monitor the situation closely and provide a further update once we have confirmed the issue is fully resolved.
- Identified · Jul 16, 15:30 UTC
Our Engineering team has identified the cause of the issue affecting Reserved IP routing in the TOR1 region, which was causing inbound and outbound traffic to and from Reserved IPs in TOR1 to fail. Detaching and reassigning the Reserved IP to the Droplet may restore connectivity in the meantime. We recommend trying this workaround if you are still experiencing issues with your Reserved IP in TOR1. Our engineering team is now working on implementing a fix. We will provide updates as more information becomes available.
- Investigating · Jul 16, 13:39 UTC
Our Engineering team is investigating an issue affecting Reserved IP routing in the TOR1 region. The issue is causing inbound and outbound traffic to and from Reserved IPs in TOR1 to fail. In the meantime, detaching and reassigning the Reserved IP to the Droplet may restore connectivity. We recommend trying this workaround if you are experiencing issues with your Reserved IP in TOR1. Our engineering team is actively investigating the root cause and working towards a resolution. We will provide updates as more information becomes available.
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 |
Also caused by network
All| Started | Vendor | Incident | Impact | Duration |
|---|---|---|---|---|
| Sep 1901:36 UTC | Elevated errors in Ashburn, VA (IAD) | none | 0m | |
| Sep 1411:59 UTC | Increased wait times for macOS jobs | minor | 1h | |
| Sep 410:57 UTC | Increased errors on High Performance Edge Network - FRA Region | minor | 0m | |
| Sep 214:18 UTC | Upstream network issues | minor | 1h 39m | |
| Sep 116:11 UTC | Service degradation in GCP us-central-1 | none | 19m | |
| Sep 114:44 UTC | Multiple products in us-central1-b are experiencing network service degradation. | major | 4h 8m |
From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.