We have identified and patched the issue to prevent it from reoccurring. The engineering team has addressed all major issues and will continue monitoring support channels for any continued issues.

We have identified the issue that caused the downtime and have applied a fix to prevent it from recurring. The engineering team is still monitoring the service and addressing a few edge cases affecting a small number of databases that may have resulted from this issue.

We've been able to recover API access to all affected projects. They should now be able to access their data and all services without any issues. Our engineering team is working to recover remaining problems on a small number for databases.

We've confirmed there is no data loss. At the moment, we're in the process of restoring access to the database tables, but it will take some time to get all of them online.

We are still working through multiple avenues to bring back services.

We have narrowed down the problem and are working to bring the services back online.

We're still investigating the issue and will provide an update soon.

Some users are receiving "Collection not found" when accessing data in their project. We are investigating and will update shortly.