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

As listed on DigitalOcean’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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

The full archive is on the DigitalOcean status & history page.

Related: DigitalOcean status & history. SquidGrid is not affiliated with DigitalOcean.