Supabase: Project Lifecycle Activity Degradation
Is it fixed? Yes.
Resolved after <1 min. First reported Sep 19, 22:12 UTC, resolved Sep 19, 22:12 UTC. The vendor posted it on its status page first.
What happened
Project lifecycle operations are behaving normally after a degradation issue was resolved. No specific affected versions or workarounds were provided.
What caused it?
Under active investigation. No report has identified a root cause yet.
No verified workaround yet
This incident was resolved upstream without a reported workaround.
Official fixTimeline
- Investigating(done)
- Workaround available(skipped)
- Resolved(done)
- Archived
Evidence
1 report · 1 StatusShow
- [1]Status First reportProject Lifecycle Activity Degradation(opens official status page in a new tab)
Status: Resolved Project lifecycle operations are behaving normally.
by supabase status
FAQ
What happened in the Supabase outage?
Project lifecycle operations are behaving normally after a degradation issue was resolved. No specific affected versions or workarounds were provided.
What is affected by the Supabase outage?
Supabase.
When did the Supabase outage start and end?
It started Sep 19, 22:12 UTC and was resolved Sep 19, 22:12 UTC, after <1 min.
How do I get alerts for Supabase?
Subscribe to the Supabase RSS feed for every new Supabase incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Supabase is down. Supabase feed
Where does this information come from?
WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source, including the vendor’s own status page.