CheckUpstream measured Supabase at 100.000% availability across 2824 independent checks (global · api). 87 incidents were recorded in the past 12 months; the most recent resolved earlier today after 3 hours. Status signals are polled from Supabase's official Atlassian Statuspage status page, alongside independent probes and community reports. Supabase publishes 1 product-level SLA uptime commitment (up to 99.9%), and service credits must be claimed within 30 days of a breach.
30 days measured availability how this is computed
100.000%
global · api · n=2824 · p95 261ms (30d)
Share of our own checks against Supabase endpoints that returned Supabase's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 14 incidents · 11 of 30 days with none posted · 8d 9h of declared impact
Within Supabase's published 99.9% target for this window.
Fewer incidents in the last 30 days than 5% of 232 tracked services.
Share of each window with no impact declared by Supabase
7d
55.399%
30d
71.965%
90d
90.635%
180d
93.989%
1y
97.035%
Downtime like this can be refundable
If you're a paying Supabase customer, outages in these windows may count against Supabase's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Supabase entitlement →Does Supabase actually matter to you?
A Supabase outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →Predicted resolution
n=46~124m (p25 54m – p75 235m)
Based on 46 historical Minor incidents · currently 26123m elapsed.
From 13 incidents Supabase published and resolved in the last 30 days, measured between their own start and resolution times. It describes how long Supabase takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Excluded: 1 still open.
Aug 31, 16:28 UTC · resolved in 2h 41m · Resolved
Aug 27, 17:20 UTC · resolved in 3d 22h · Resolved
Aug 26, 19:49 UTC · resolved in 22h 35m · Resolved
2signals across 1 source
Synthetic probes 2
All of these are CheckUpstream's own probes. Nobody else has reported Supabase in this window, so nothing here is corroboration.
Live Supabase status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/supabase)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Supabase is currently Degraded. CheckUpstream tracks Supabase in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Supabase's last resolved incident started earlier today and lasted 2h 41m (a partial outage).
Looking for the live "is Supabase down" view? See the Supabase Live status page.
Aug 24, 13:52 UTC · resolved in 2h 2m · Resolved
Aug 19, 15:52 UTC · resolved in 2m · Resolved
Aug 17, 01:47 UTC · resolved in 7m · Resolved
Aug 14, 09:31 UTC · resolved in 9m · Resolved
Aug 14, 09:31 UTC · resolved in 1h 19m · Resolved
Aug 14, 02:23 UTC · resolved in 12m · Resolved
Aug 14, 02:23 UTC · in progress · Identified
Aug 3, 15:28 UTC · resolved in 2d 2h · Resolved
Jul 31, 18:36 UTC · resolved in 4d 1h · Resolved
Jul 31, 18:36 UTC · resolved in 13m · Resolved
Jul 31, 12:27 UTC · resolved in 1h 7m · Resolved
Jul 30, 20:57 UTC · resolved in 1h 2m · Resolved
Jul 30, 20:51 UTC · resolved in 9m · Resolved
Jul 30, 20:51 UTC · resolved in 5h 54m · Resolved
Supabase's 30-day measured availability is 100.000%, from CheckUpstream's own probes against Supabase endpoints. It is the share of checks that returned the expected response, not a figure taken from Supabase's status page.
Sign up to CheckUpstream and add Supabase to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Supabase's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.