Apr 6, 01:01 UTC
Resolved - Our Engineering team has resolved the issue affecting Mongo 8 Database operations. Users should be able to create new Mongo 8 Databases, and other operations such as upgrading, scaling, and forking should complete successfully now.

If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.

Apr 5, 22:01 UTC
Update - Our Engineering team is actively investigating the issue affecting Mongo 8 Database operations.

We apologize for the continued inconvenience. We will provide additional updates as soon as more information becomes available.

Apr 5, 19:54 UTC
Update - Our Engineering team is continuing to investigate the cause of the issue with Mongo 8 Database creation in our AMS3 region and is taking action to resolve this issue. In addition to the database creation, users may see failures when scaling the instance or performing any control plane operations.

We will continue to share updates as soon as we have new information.

Apr 5, 16:52 UTC
Investigating - Our Engineering team is investigating an issue with Mongo 8 database creation in the AMS3 region. At this time, users may experience errors while attempting to create a new Mongo 8 database instance in the AMS3 region.

We apologize for the inconvenience and will provide another update as soon as possible.

Apr 5, 13:59 UTC
Resolved - Our Engineering team has confirmed the full resolution of the networking issue affecting the LON1 region. Users should be able to access all resources without any issues.

If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.

Apr 5, 13:35 UTC
Monitoring - Our Engineering team made routing changes to remediate the networking issue due to an impact by an upstream provider and confirmed that it has successfully mitigated the connectivity issues in the LON1 region. Users should not be seeing any issues with networking in the LON1 region.

We will monitor this incident for a short period to confirm full resolution.

Apr 5, 12:45 UTC
Identified - Our Engineering team has identified the cause and applied a fix to mitigate the connectivity issue impacting the entire LON1 region. Users should be seeing improvements in reaching their resources in the LON1 region.

We'll continue to monitor the situation to confirm this incident is fully resolved and will post an update soon.

Apr 5, 12:17 UTC
Investigating - Our Engineering team is currently investigating an issue impacting networking in the LON1 region. Users may experience network connectivity loss to the resources residing in this region.

We apologize for the inconvenience and will share an update once we have more information.