Vendor record
Supabase
Checked
Front door check counts and Supabase’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We send a request to a documented Supabase endpoint and count the checks that got the answer it is documented to give.
No clear answer in 24 hours. These counts are from before this check went quiet.
Front door reachable in 2,073 of 2,073 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
806 more checks gave no clear answer and are not counted.
- Endpoint checked
- api.supabase.com
- Scope
- apiNo vendor region
- First check in this window
- Latest clear answer
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Supabase product, region or your app worked.
How we count front door checksSupabase says
Incident posts from Supabase’s status page, with its titles, impact levels and times. They say what Supabase chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
90
incidents Supabase posted, last 180 days
Median recorded duration: 2h 43m. From 87 incidents with vendor-supplied starts and recorded closure times.
Most recent records · all dates
Realtime latency
MinorStarted, per Supabase
Latest status Supabase postedInvestigating. No resolution posted.
Edge Function Degradation
MajorStarted, per Supabase
Latest status Supabase postedInvestigating. No resolution posted.
Log ingestion impaired
MajorStarted, per Supabase
Latest status Supabase postedInvestigating. No resolution posted.
Upgrade Issues
MinorSupabase’s postStarted, per Supabase
Closed in our record(2h 56m)
Increased errors on management api leading to project operation failures
MinorSupabase’s postStarted, per Supabase
Closed in our record(1h 16m)
15 older records
Intermittent latency in Eastern US
MinorSupabase’s postStarted, per Supabase
Closed in our record(6d 19h)
Log Ingestion Degradation
MinorSupabase’s postStarted, per Supabase
Closed in our record(52m)
Project Lifecycle Issues in eu-west-1
MajorSupabase’s postStarted, per Supabase
Closed in our record(2h 3m)
Permission errors in the Supabase Dashboard
CriticalSupabase’s postStarted, per Supabase
Closed in our record(1h 12m)
Supabase CLI CI workflow failures
MinorSupabase’s postStarted, per Supabase
Closed in our record(1h 51m)
Storage search failing for restored projects
MinorSupabase’s postStarted, per Supabase
Closed in our record(1d)
Increased error rate in project creation and project restore
MajorSupabase’s postStarted, per Supabase
Closed in our record(1h 28m)
Supavisor connection disruptions in EU West 1 (Ireland)
MinorSupabase’s postStarted, per Supabase
Closed in our record(1h 35m)
Project creations are degraded in multiple regions
MinorSupabase’s postStarted, per Supabase
Closed in our record(36m)
Project Lifecycle Activity Degradation
MajorSupabase’s postStarted, per Supabase
Closed in our record(2h 3m)
Query slowness for projects running Postgres version 14 in us-east-1 and ap-northeast-2
MinorSupabase’s postStarted, per Supabase
Closed in our record(2h 46m)
Edge Function Latency
MinorSupabase’s postStarted, per Supabase
Closed in our record(3h 5m)
Auth Service Outage
MinorSupabase’s postStarted, per Supabase
Closed in our record(2h 22m)
Unresponsive Projects
MajorSupabase’s postStarted, per Supabase
Closed in our record(1d 3h)
Project Lifecycle Actions Showing increased error rates across all regions
CriticalSupabase’s postStarted, per Supabase
Closed in our record(8h 4m)
Your code, your dependencies
See which of your code paths call Supabase
Connect GitHub or GitLab to find where your public or private repository uses Supabase. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add Supabase status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is Supabase currently down?
Supabase's latest recorded status is Partial Outage. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did Supabase last have an outage?
The most recent closed incident record began 10 days ago and spans 2h 56m. The vendor reported degraded performance. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for Supabase?
No. CheckUpstream checks Supabase’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.
How do I monitor Supabase in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track Supabase?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.