DNS Lookup Failures for Managed Database
Jul 1, 11:35 UTCJul 1, 16:28 UTC
Duration
4h 53m
Impact
Minor
Root cause
Not disclosed
DigitalOcean, 90 days
12 incidents
Affected
FRA1DNSKubernetes - FRA1Managed Databases - FRA1
Final update
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.
Timeline
- Resolved · Jul 1, 16:28 UTC
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.
- Investigating · Jul 1, 12:15 UTC
We are continuing to investigate this issue.
- Investigating · Jul 1, 11:35 UTC
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.
More from DigitalOcean
Full historyKubernetes Cluster Management Operationslasted 3h 40mApp Platform Deploymentslasted 0mDNS Resolution for Managed Kuberneteslasted 1h 27mVPC Networking Availabilitylasted 1h 35mA Network Disruption in BLR1 Region Impacted Multiple Products (Resolved)lasted 0mSupport Portal Service Disruptionlasted 11h 21m