DigitalOcean incident: Reserved IP routing in TOR1

Affected components

• Reserved IP
• TOR1

1. resolvedJul 16, 2026, 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.

2. monitoringJul 16, 2026, 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.

3. identifiedJul 16, 2026, 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.

4. investigatingJul 16, 2026, 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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in DigitalOcean's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Mux: video live and playback issuesCritical · Jul 15, 2026, 19:13 UTC
• Linear: Some customers are seeing issues with Linear loadingMajor · Jul 16, 2026, 16:47 UTC
• LaunchDarkly: LaunchDarkly is operational but customer action may be requiredMinor · Jul 10, 2026, 16:00 UTC
• Twilio: SMS Delivery Failures from Twilio to Vodafone AustraliaMinor · Jul 13, 2026, 02:47 UTC
• Twilio: SMS Delivery Delays from Twilio to Liberty Mobile Puerto RicoMinor · Jul 13, 2026, 20:24 UTC
• Grafana Cloud: Issue with Dashboard Views Being RegisteredMinor · Jul 14, 2026, 08:10 UTC
• Twilio: SMS Delivery Delays from Twilio to MTN NigeriaMinor · Jul 15, 2026, 21:27 UTC
• Akamai: Application Load Balancer reporting availability issuesMinor · Jul 16, 2026, 04:21 UTC
• Grafana Cloud: Adaptive Metrics aggregation delay in eu-west-0 region.Minor · Jul 16, 2026, 12:56 UTC
• Clerk: Elevated API ErrorsMinor · Jul 16, 2026, 13:04 UTC

How often does DigitalOcean have incidents?

DigitalOcean reported 20 incidents in the last 90 days, 3 of them major or critical. A typical incident lasted 5h 35m. See DigitalOcean's uptime and incident history