Managed Database Cluster
Incident
Report for DigitalOcean
Resolved
As of 06:25 UTC, our Engineering team has confirmed that the issue impacting the newly created Managed Database Clusters has been fully resolved.
Users will no longer experience issues with the newly created Managed Database Cluster.
If you continue to experience any issues with Managed Database Clusters please open a ticket with our support team. Thank you for your patience.
Users will no longer experience issues with the newly created Managed Database Cluster.
If you continue to experience any issues with Managed Database Clusters please open a ticket with our support team. Thank you for your patience.
Monitoring
As of 06:15 UTC, our Engineering team has identified the issue impacting our Managed Database product and a fix has been implemented to mitigate the issue. Currently, new users may no longer experience issues with the newly created Managed Database Cluster due to hostname resolution.
Users who already have a Managed Database cluster are not impacted by this incident.
Thank you for your patience and we apologize for the inconvenience caused. We are monitoring the situation and will post an update once the incident is completely resolved.
Users who already have a Managed Database cluster are not impacted by this incident.
Thank you for your patience and we apologize for the inconvenience caused. We are monitoring the situation and will post an update once the incident is completely resolved.
Investigating
Our Engineering team is currently investigating reports of issues impacting a subset of users using our Managed Database Clusters.
During this time, hostnames for the newly created Managed Database Cluster are not resolving. However, previously created Clusters are not impacted due to the same.
We apologize for the inconvenience and will share an update once we have more information.
During this time, hostnames for the newly created Managed Database Cluster are not resolving. However, previously created Clusters are not impacted due to the same.
We apologize for the inconvenience and will share an update once we have more information.
This incident affected: Managed Databases (AMS3, BLR1, FRA1, LON1, NYC1, NYC2, NYC3, SFO2, SFO3, SGP1, SYD1, TOR1).