DNS Lookup Failures for Managed Database

lowDigitalOceanJul 1, 2026 11:35Duration: 4h 53m

networkdnsdatabase

DNS FailureDatabase OverloadNetwork / Routing

Summary

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.

Impact

minor

Timeline

Jul 1, 2026 11:35

[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.

via statuspage

+40m

Jul 1, 2026 12:15

[investigating] We are continuing to investigate this issue.

via statuspage

+4h 13m

Jul 1, 2026 16:28

[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.

via statuspage

Lessons Learned

⚠DigitalOcean has experienced 94 incidents in the past year. This frequency suggests systemic reliability challenges that may warrant additional monitoring.

📊Incidents related to network, dns, database have occurred 211 times across all providers in the past year. This is one of the most common failure categories in cloud infrastructure.

💡This incident is categorized as: DNS Failure, Database Overload, Network / Routing. Consider implementing preventive measures specific to this failure category.