← Back to DigitalOcean History
minor✓ Resolved
Reserved IP routing in TOR1
Status
resolved
Duration
3h 45m
Updates
4
Coverage
0 articles
INCIDENT TIMELINE
✓ Resolved
This incident has been resolved.
resolved
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
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
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
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.
📊 TECHNICAL DETAILS
Internal ID
b647af0f-c73d-4682-8a27-a8a79433b3e7
External ID
nfhvp4yhyrfl
🕐 Started
🔄 Last Updated
✓ Resolved
MINOR
Impact Level
3h 45m
Total Duration
4
Status Updates
Affected Components
Reserved IPTOR1
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we request generation of one.
0 / 100 requests100 more needed