AuraDB Professional tier in the GCP us-east1 (South Carolina) region ran out of the provisioned capacity impacting new and existing customers wanting to run databases in this region.
During the incident, new databases could not be created and any existing paused databases could not be resumed based on the availability of capacity at the specific time.
In the early stages of the incident any database creation that was initiated would not complete. As Neo4j became aware of the issue, the capability to create new databases in that region was removed. Neo4j also removed non-customer-facing (internal) databases to free up capacity which allowed pause and resume operations to succeed while work to provision additional capacity was completed.
An attempt to provision more capacity in the region failed due to unexpected deployment issues. Neo4j overcame the new issues which allowed the provisioning to be successful. Once additional capacity was added Neo4j re-enabled the creation of AuraDB instances in the affected region.
Neo4j has taken steps to enhance the capacity monitoring and alerts of all regions, and modified internal processes designed to ensure the capability to create new databases, in the affected region(s), are temporarily disabled in situations where new capacity must be provisioned.