Is Supabase down? › Outage history › Sep 4, 2026

Supabase outage on Sep 4, 2026: what happened

On Sep 4, 2026, the Supabase status page reported "Project Lifecycle Actions Showing increased error rates across all regions". About 7 hours 11 min: from Sep 4, 2026, 01:08 UTC to Sep 4, 2026, 08:18 UTC, by the official start and resolution times.

Started

Sep 4, 2026, 01:08 UTC

Resolved

Sep 4, 2026, 08:18 UTC

Duration

7 hours 11 min

Official impact

Critical

Source

Project Lifecycle Actions Showing increased error rates across all regions on the Supabase status page

The Supabase status page rated it "Critical", its highest impact level: an outage of the affected parts, not only slowness.

What caused the Supabase outage?

The Supabase status page has not published a cause. When it identified the problem at 00:30 UTC on Sep 4, 2026, it said: "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 provide additional updates as we have more information."

When was it fixed?

The Supabase status page marked it resolved at Sep 4, 2026, 08:18 UTC, 7 hours 11 min after it started. A fix was in place and being monitored from Sep 4, 2026, 04:28 UTC. Its resolution note: "Lifecycle operations have been re-enabled for 100% of users and error rates have returned to normal."

Timeline of official updates

Every update the Supabase status page posted, oldest first. Times are UTC.

1. Sep 4, 2026, 00:15 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

2. Sep 4, 2026, 00:30 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 provide additional updates as we have more information.

3. Sep 4, 2026, 00:58 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 more information.

4. Sep 4, 2026, 01:37 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.

5. Sep 4, 2026, 02:02 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.

6. Sep 4, 2026, 03:01 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.

7. Sep 4, 2026, 03:41 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.

8. Sep 4, 2026, 04:28 UTC 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.

9. Sep 4, 2026, 08:18 UTC resolved

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

Supabase outage questions

Other recent Supabase incidents

• Elevated Mgmt API Error Rates in Multiple Regions Oct 22, 2026, 11:29 UTC, ongoing, 1 hour 6 min so far
• Project lifecycle operation errors in the EU region Oct 22, 2026, 03:53 UTC, ongoing, 8 hours 42 min so far
• Intermittent connection errors via the connection pooler in us-east-1 Oct 21, 2026, 16:27 UTC, duration not stated
• Project lifecycle operations such as project creation, pausing, and restoration, in all regions Oct 21, 2026, 15:36 UTC, 1 hour 16 min
• Projects stuck in restarting state Oct 20, 2026, 21:59 UTC, 7 hours 41 min
• Support Form Errors Oct 19, 2026, 17:13 UTC, 60 minutes

Full Supabase outage history and biggest outages → · Recent outages across all services →

Quotes are the Supabase status page's own words, from the official incident. Is It Up or Down is independent and not affiliated with Supabase. Times are UTC.