New Multi-region uptime checks and custom-domain status pages

Project Lifecycle Actions Showing increased error rates across all regions

Critical Impact Resolved Duration: 8h 4m September 4, 2026
View the provider incident record →

Current answer

Supabase experienced a critical incident: Project Lifecycle Actions Showing increased error rates across all regions. ServiceAlert observed recovery on Sep 4, 2026.

Official Supabase status page Current Supabase status ServiceAlert observed status change:

Looking for an update now? Check the current status, or follow Supabase for future changes.

Incident Lifecycle

Investigating Identified Identified Identified Identified Identified Identified Monitoring
Affected Components
Management API

Incident Timeline

Monitoring
Lifecycle operations have been re-enabled for 100% of users and error rates have returned to normal.

We are going to monitor to ensure that things stay stable. The team is working through any remaining projects which did not automatically resolve.

Some users may also notice that backups will happen a bit later than usual, but these jobs are running and completing normally.
Sep 4, 2026 at 4:28 AM UTC
Identified
We've increased project lifecycle operations to 50% of users and things are holding steady. We're continuing to ramp this up until operations are restored for all users.

This is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc.

Running projects remain running, and the data APIs and direct postgres client connections are NOT affected.
Sep 4, 2026 at 3:41 AM UTC
Identified
Error rates have returned to normal, and the backlogs are draining well. We are beginning to slowly re-enable lifecycle operations for users.

We will be monitoring impact, and we hope to have this re-enabled everywhere soon. We will leave this in this state until lifecycle operations have been completely restored.

Running projects remain running, and the data APIs and direct postgres client connections are NOT affected.
Sep 4, 2026 at 3:01 AM UTC
Identified
We are seeing incremental improvements internally. There is a large backlog of actions that we are working through, but things are progressing. Once we make it through most of the backlog, we will re-enable lifecycle actions.

This is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc.

Running projects remain running, and the data APIs and direct postgres client connections are NOT affected.
Sep 4, 2026 at 2:02 AM UTC
Identified
The team is continuing to work on restoring project lifecycle operations. Out of caution, we have disabled lifecycle operations.

This is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc.

Running projects remain running, and the data APIs and direct postgres client connections are NOT affected.

We will provide additional updates as we have more information.
Sep 4, 2026 at 1:37 AM UTC
Identified
The team has applied a fix, but error rates remain high. We are continuing to work and will take other necessary steps to resolve this as soon as possible.

Running projects remain running, and the data APIs and direct postgres client connections are NOT affected.

Out of an abundance of caution, we would suggest against taking any of these actions until this incident is resolved: Creates, Configuration changes, Restarts, or Compute size changes. We will provide additional updates as we have ...
Sep 4, 2026 at 12:58 AM UTC
Identified
We have identified the source of the errors with project lifecycle actions, and the team is currently working to resolve it.

This is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc.

Running projects remain running, and the data APIs and direct postgres client connections are NOT affected.

Out of an abundance of caution, we would suggest against taking any of these actions until this incident is resolved. We will provid...
Sep 4, 2026 at 12:30 AM UTC
Investigating
We are seeing increased error rates in actions across all project lifecycle actions - Creations, Deletions, Restores, Configuration and Compute size upgrades. We are currently looking into the cause.

Out of an abundance of caution, we would suggest against taking any of these actions until this incident is resolved. We will provide additional updates as we have more information
Sep 4, 2026 at 12:15 AM UTC
Was your business affected by this Supabase outage?
Follow Supabase and route available status alerts to email or a team channel.