Supabase reported this major-impact incident on its official status page on Aug 31, 2026, 16:28 UTC. It was resolved after 2h 38m.
Right now Supabase is degraded. Live Supabase status →
Project creation has returned to baseline consistently.
Project creation is reporting as recovered across the platform. We will monitor for stability in the near term.
We are seeing the mitigation steps having the desired effect. Project creation is recovering.
While the first set of actions are taking effect, we are implementing a second set of likely mitigations to attempt to facilitate improvement in project creation.
We continue to work this issue. The steps we have taken are addressing the hypothesized cause of the issue. We are implementing further related mitigations.
We have a working hypothesis on the cause of the issue, and are implementing steps to try to improve project creation performance.
Project creation is failing for new projects on the platform. We are investigating.
Our 5-minute checks didn't record a change in Supabase's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
Supabase reported 43 incidents in the last 90 days, 16 of them major or critical. A typical incident lasted 2h 2m. See Supabase's uptime and incident history