30 days uptime
95.632%
25 of 30 days clean · 1d 7h total downtime
All windows
Last resolved incident
5 days ago · lasted 2h 43m · Minor
Predicted resolution
n=27~149m (p25 71m – p75 257m)
Based on 27 historical None incidents · currently 17430m elapsed.
5/21/2026, 4:46:59 PM · resolved 5/21/2026, 7:30:07 PM · Resolved
5/21/2026, 8:30:51 AM · resolved 5/21/2026, 11:00:04 AM · Resolved
5/20/2026, 9:04:18 PM · resolved 5/21/2026, 4:48:47 AM · Resolved
5/20/2026, 3:40:53 PM · resolved 5/20/2026, 7:50:07 PM · Resolved
28signals across 1 source
synthetic_probe 28
Official status page: https://status.supabase.com (opens in new tab)
Live status pill for Supabase. Updates automatically — no maintenance, no API key.
PREVIEW
Drop into any HTML page — README, docs, vendor homepage. No iframe, no dependencies.
<script src="https://checkupstream.com/embed/badge.js?service=supabase"></script>Self-contained, CSP-friendly. Theme + size are query params; revalidates every 60s.
<iframe src="https://checkupstream.com/embed/supabase" style="border:0;width:260px;height:44px" loading="lazy" title="Supabase status badge"></iframe>GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
[](https://checkupstream.com/reliability/supabase)Useful for status-page composers (Notion, Slab, custom dashboards) that accept image URLs.
https://checkupstream.com/embed/supabase/badge.svgSupabase is currently Operational. 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 5 days ago and lasted 2h 43m (degraded performance).
Looking for the live "is Supabase down" view? See the Supabase Status page.
5/18/2026, 11:26:56 PM · resolved 5/19/2026, 12:20:14 AM · Resolved
Supabase's 30-day customer-perceived uptime is 95.632%. The figure is weighted (full-outage = 1.0, degraded = 0.3) so component blips don't collapse the score the way a raw incident-count would.
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.