Live / DigitalOcean / Incident
DigitalOcean: Reserved IP routing in TOR1
DigitalOcean · digitalocean.comMinor incidentResolved2026-07-16 17:24 UTC
Public — what happened
Summary
DigitalOcean reported a problem with Reserved IPs in its TOR1 (Toronto) region starting at 13:39 UTC on July 16, 2026, during which traffic going to and from those addresses was failing. While it worked on the problem, the company suggested customers try detaching the Reserved IP and attaching it to their Droplet again as a possible temporary fix. DigitalOcean said at 15:30 UTC that it had found the cause, though it did not describe it publicly, and it rolled out a fix at 17:01 UTC. The company declared the issue fully resolved at 17:24 UTC.
Affected
Reserved IP, TOR1
Timeline
- Started — 2026-07-16 13:39 UTC
- Investigating — 2026-07-16 13:39 UTC
- Identified — 2026-07-16 15:30 UTC
- Monitoring — 2026-07-16 17:01 UTC
- Resolved — 2026-07-16 17:24 UTC · 3h 45m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach DigitalOcean against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for DigitalOcean: paths off baseline right now, where on the route conditions change, and its full incident track record.
Included with any paid plan.
Open the DigitalOcean report →
More from DigitalOcean