Database Clusters updating status over 1days

If the status is stuck in a Managed Database, there is a good chance that is something on our end that we'd need to investigate and resolve. To get help with this, you can open a Support Ticket from Cloud Manager or give us a call. If you have already opened a ticket, check back and see if it's been updated at this time.

For anyone who find this in the future, here is some guidance for reaching out about this issue. The more information customers provide in their initial updates, the better the chance we can help, so consider providing information like the following when you open a ticket:

• How you added the IP to your Access Controls. Did you use Cloud Manager or the API?
• The IP address or range you tried to add.
• What time you tried to add it (and what time zone you're in).
• A list of any recent changes you've made to your cluster, such as updating the password for the linroot user.

While I can't say for sure, I have seen a recent example of this that was caused by a brief networking issue while the customer was updating their Access Controls. In that case, we were able to restore the cluster to a running state and then the customer tried again and successfully updated the Access Control List to add the new IP.