Supabase Status · History · Incident #6966
RESOLVEDProject Lifecycle Actions Showing increased error rates across all regions
Critical · Started Sep 4, 2026 · 12:15 AM
Supabase Status · History · Incident #6966
RESOLVEDCritical · Started Sep 4, 2026 · 12:15 AM
Duration
8h 2m
Severity
Critical
Detection lead
—
User reports
—
Summary
Lifecycle operations have been re-enabled for 100% of users and error rates have returned to normal.
Started
Sep 4, 2026 · 12:15 AM
Resolved
Sep 4, 2026 · 8:18 AM
Duration
8h 2m
Severity
Critical
Event timeline
Investigating
Sep 4 · 12:15 AM SupabaseWe 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
Identified
Sep 4 · 12:30 AM SupabaseWe 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.
Identified
Sep 4 · 12:58 AM SupabaseThe 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.
Identified
Sep 4 · 1:37 AM SupabaseThe 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.
Identified
Sep 4 · 2:02 AM SupabaseWe 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.
Identified
Sep 4 · 3:01 AM SupabaseError 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.
Identified
Sep 4 · 3:41 AM SupabaseWe'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.
Monitoring
Sep 4 · 4:28 AM SupabaseLifecycle 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.
Resolved
Sep 4 · 8:18 AM SupabaseLifecycle operations have been re-enabled for 100% of users and error rates have returned to normal.
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026. Pulsetic® is a registered trademark.