Live / DigitalOcean / Incident
DigitalOcean: VPC Networking Availability
DigitalOcean · digitalocean.comMinor incidentResolved2026-10-05 12:13 UTC
Public — what happened
Summary
DigitalOcean reported a minor problem with its VPC Networking service, saying that starting around 08:48 UTC on 2026-10-05, customers could have seen slow or failed attempts to set up or remove VPC peerings, VPC Native DOKS clusters and Private Network Connections, along with trouble adding cluster members and possibly creating routes and subnets. The company said resources already in place and their network connections were not affected. DigitalOcean posted about the issue at 10:38 UTC and said at 11:02 UTC that a fix had been applied and a backlog of stuck requests had been cleared, without naming a cause. In its final update at 12:13 UTC, it said the disruption had actually been fully resolved as of 10:29 UTC and that operations had stayed stable.
Affected
Global
Timeline
- Started — 2026-10-05 10:38 UTC
- Identified — 2026-10-05 10:38 UTC
- Monitoring — 2026-10-05 11:02 UTC
- Resolved — 2026-10-05 12:13 UTC · 1h 35m after it started
What SquidGrid measured
SquidGrid measured 54 internet paths into DigitalOcean’s network during this incident. None of them ran meaningfully slower than the same paths the day before.
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
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.