- Level
- confirmed
- Worst impact
- Degraded
- Components
- FRA1, FRA1, DNS
- Regions
- us
- Down Index
- 25of 100
What to do
Check whether you use DigitalOcean FRA1, FRA1, DNS in us. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 4h 53m it lasted.
Anything that failed between 2026-07-01 11:35 UTC and 2026-07-01 16:28 UTC may need a replay.Subscribe to DigitalOcean's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=digitalocean works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from DigitalOcean 3
- investigating
As of 06:39 UTC, our Engineering team is investigating reports of intermittent DNS lookup failures for Managed Database hostnames from Managed Kubernetes, primarily affecting connections from Managed Kubernetes to Managed Database hostnames. At this point, customers in the FRA1 region may experience intermittent connectivity issues. We apologize for the inconvenience and will share an update once we have more information.
provider
- investigating
We are continuing to investigate this issue.
provider
- resolved
The intermittent DNS lookup failures between Managed Kubernetes and Managed Database hostnames in the FRA1 region have been resolved for now but please let us know if you see the issue again. Connectivity has remained stable, and all systems are operating normally. If you continue to experience any problems, please open a ticket with our support team. Thank you for your patience, and we apologize for any inconvenience.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-1618e433b1
Is DigitalOcean still down?
No, this incident was resolved 2026-07-01 16:28 UTC. For DigitalOcean's live state, see https://down.guide/digitalocean.
How long did it last?
4h 53m, from 2026-07-01 11:35 UTC to 2026-07-01 16:28 UTC, by the times DigitalOcean posted.
What was affected?
DigitalOcean named FRA1, FRA1, DNS in us.
What caused it?
DigitalOcean hasn't published a root cause. If it does, it shows here.
Where does this come from?
DigitalOcean's official status page, https://status.digitalocean.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.