Live / DigitalOcean / Incident
DigitalOcean: DNS Lookup Failures for Managed Database
DigitalOcean · digitalocean.comMinor incidentResolved2026-07-01 16:28 UTC
Public — what happened
Summary
DigitalOcean said some customers in its FRA1 region had trouble with Managed Kubernetes clusters intermittently failing to look up the addresses of Managed Database services, which could interrupt connections between the two. The company first posted about the problem at 11:35 UTC on July 1, 2026, saying reports of the failures dated back to 06:39 UTC. It did not name a cause in its updates. At 16:28 UTC it marked the issue resolved, saying connections had stayed stable, and asked customers to contact support if the problem came back.
Affected
FRA1, FRA1, DNS
Timeline
- Started — 2026-07-01 11:35 UTC
- Investigating — 2026-07-01 11:35 UTC (2 updates)
- Resolved — 2026-07-01 16:28 UTC · 4h 53m 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