MongoDB Cluster Creation Failure
Incident
Report for DigitalOcean
Resolved
The maintenance that was scheduled to prevent the recurrence of this issue has been completed as of 19:00 UTC and our Engineering team has confirmed that the issue affecting the creation of Mongo Managed Database clusters is fully resolved.
We appreciate your patience throughout the process and if you continue to experience problems, please open a ticket with our support team for further review.
We appreciate your patience throughout the process and if you continue to experience problems, please open a ticket with our support team for further review.
Update
Our Engineering team has identified that urgent maintenance is needed in order to remediate this incident and prevent a recurrence.
From 18:00 -19:00 UTC, we’ll be performing that maintenance. Further details and updates throughout the maintenance can be found here: https://status.digitalocean.com/incidents/cq5jj3snkp64
Once completed, we will update this incident after confirming the issue is fully resolved.
From 18:00 -19:00 UTC, we’ll be performing that maintenance. Further details and updates throughout the maintenance can be found here: https://status.digitalocean.com/incidents/cq5jj3snkp64
Once completed, we will update this incident after confirming the issue is fully resolved.
Monitoring
Our engineering team has implemented a fix to resolve the issue that was preventing users from creating a MongoDB cluster in any region and is monitoring the situation. We will post an update as soon as the issue is fully resolved.
Identified
Our engineering team has identified the cause of the issue that was preventing users from creating a MongoDB cluster in any region and is working on a fix. We will post an update as soon as additional information is available.
Investigating
As of 09:30 UTC, our engineering team is investigating an issue that prevents creating a MongoDB cluster in any region. During this time, you may face issues when creating a MongoDB cluster. 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).