Project status change failures in multiple regions
Resolved
Capacity availability and project creation, resize, and restart operations have returned to normal and have remained stable for an extended period of time. We are resolving this incident.
Out of an abundance of caution, and out of respect for the impact this incident had for our users, we held the incident open for a considerable amount of time after the observed impact was mitigated. We wanted to be certain any residual potential impact was fully cleared before formally resolving the statuspage.
Posted Jul 13, 2026 - 16:00 UTC
Update
Capacity has continued to recover across all regions, and the large majority of restart, resize, and project-creation operations are now completing normally. We are continuing to monitor the system.
We have added additional mitigations and machine types available to all Postgres versions, and we are also seeing error rates for these users stabilize. While there is still ongoing work behind the scenes to continue to improve our resiliency, users should no longer be affected by capacity issues stemming from this incident. We are showing stable capacity across all regions on all machine sizes and types.
We will be monitoring this thru the rest of the week to ensure ongoing work is effective and we don’t have any re-occurrence of these or similar issues before we resolve this entirely.
Posted Jul 06, 2026 - 16:36 UTC
Update
Capacity is currently available across all regions, and we are continuing to progress the remaining mitigation work, including bringing additional capacity online. This remains our highest priority.
We have recovered most projects that were unavailable due to infrastructure compatibility constraints. Our team is continuing to restore the remaining affected projects and will provide further updates as this work progresses.
The remaining impact is primarily limited to Medium instances running PostgreSQL versions earlier than 17.6.1.121.
New project deployments should succeed, but restarts or resizes for projects matching this profile may fail.
Existing projects are not affected unless they have been restarted or resized during this incident.
Posted Jul 03, 2026 - 16:03 UTC
Identified
We have identified the issue and are working on a fix. Impact is currently affecting project creation, project resizing, branch provisioning, and project restarts across multiple regions. We will provide another update as soon as we have more information.
Posted Jun 30, 2026 - 03:38 UTC
Investigating
We are currently investigating an issue affecting project creation in multiple regions.
Posted Jun 30, 2026 - 02:38 UTC
This incident affected: Compute capacity (ap-northeast-1, ap-northeast-2, ap-south-1, ap-southeast-1, ap-southeast-2, ca-central-1, eu-central-1, eu-central-2, eu-north-1, eu-west-1, eu-west-2, eu-west-3, sa-east-1, us-east-1, us-east-2, us-west-1).