Loading status…
Loading status…
Supabase status · AI & APIs · checked (24s ago)
Partly — Supabase is up but running slower than usual (Partially Degraded Service).
According to Supabase's official status page, Supabase was reporting “Partially Degraded Service” when isuptime last checked at . Over the last 30 days, Supabase's feed reported no outage in 100.00% of our checks.
isuptime cannot fix Supabase, and neither can you. These are the things that are actually worth doing until it comes back.
Status shown for each is read from that provider's own feed, on the same schedule as this page.
Everything above is read from Supabase's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Supabase in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
Supabase is an open-source Firebase alternative built on Postgres: a hosted database with auto-generated REST and GraphQL APIs, plus authentication, storage, edge functions and realtime subscriptions.
Supabase's status page covers the platform — the API gateway, dashboard, authentication and storage — rather than individual customer projects. That gap matters more here than for most services: your project runs on a specific instance, and a single project can be paused, out of disk, or restarting while the platform reports fully operational.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where Supabase's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Supabase was down.
8 other services isuptime tracks were also reporting a problem as of the same check, 24s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Supabase's status endpoint.
Supabase has published 50 incidents in the last 12 months, the 20 most recent shown here. Only what Supabase posted itself — not every problem users hit.
monitoring · Sep 23, 09:31 AM (7h ago)
resolved · Sep 23, 09:21 AM (8h ago)
resolved · Sep 22, 10:49 AM (1d ago)
resolved · Sep 22, 08:33 AM (1d ago)
resolved · Sep 19, 08:12 PM (3d ago)
resolved · Sep 16, 05:53 PM (6d ago)
resolved · Sep 16, 09:24 AM (7d ago)
resolved · Sep 16, 07:17 AM (7d ago)
resolved · Sep 11, 05:00 PM (12d ago)
resolved · Sep 10, 03:26 PM (13d ago)
resolved · Sep 9, 08:47 AM (14d ago)
resolved · Sep 4, 12:15 AM (19d ago)
resolved · Sep 1, 08:45 AM (22d ago)
resolved · Aug 31, 04:28 PM (23d ago)
resolved · Aug 28, 04:18 PM (26d ago)
resolved · Aug 27, 05:20 PM (27d ago)
resolved · Aug 26, 07:49 PM (27d ago)
resolved · Aug 24, 03:26 PM (30d ago)
resolved · Aug 24, 01:52 PM (30d ago)
resolved · Aug 24, 06:02 AM (30d ago)
Check your project's own health in the dashboard first. Free-tier projects are paused after a week of inactivity and return connection errors until they are restored. Row-level security policies rejecting queries look identical to a database outage from the client side. Connection pool exhaustion under load is a common cause of intermittent failures that never reach the status page.