Databases & data infrastructure
Is Supabase down?
Live Supabase status, measured independently. We probe 5 Supabase endpoints from monitoring regions on every continent and record every outage we detect.
Supabase is up
Our probes are reaching Supabase normally from every region we check from.
Checked every minute from 6 regions on every continent.
- Uptime, 24 hoursUptime, last 24 hours
- Uptime, 7 daysUptime, last 7 days
- Uptime, 30 daysUptime, last 30 days
- Website100% uptime, 30 days6 regions, 76 to 183 msUnknownp50median response102 msp95slowest 5% of checks245 ms500 ms250024 h ago12 h agonow
- Management API99.98% uptime, 30 days6 regions, 48 to 215 msUnknownp50median response122 msp95slowest 5% of checks195 ms200 ms100024 h ago12 h agonow
- Dashboard99.99% uptime, 30 days6 regions, 63 to 143 msUnknownp50median response83 msp95slowest 5% of checks224 ms500 ms250024 h ago12 h agonow
- Documentation100% uptime, 30 days6 regions, 75 to 155 msUnknownp50median response95 msp95slowest 5% of checks308 ms500 ms250024 h ago12 h agonow
- Official status feed83.32% uptime, 30 days6 regions, 80 to 471 msUnknownp50median response249 msp95slowest 5% of checks510 ms500 ms250024 h ago12 h agonow
Daily strip:99.9% or better95–99.9%below 95%no data yet
Get notified when Supabase goes down
Follow these 5 checks from your own workspace and get alerted through Slack, email, webhooks, or on-call the moment Supabase goes down. They don't count against your monitor quota. Free plan, no card required.
About Supabase outages
Supabase bundles Postgres, authentication, file storage, realtime subscriptions, and edge functions behind one API. Because the whole backend of an app often lives on it, a Supabase incident can make an application unusable even though its frontend hosting is fine.
Projects run in the region you chose, so many Supabase incidents affect one region only. We probe the website, the management API, the dashboard, and the documentation; you should also probe your own project's REST endpoint.
What we check
Every row is a real monitor in upti.my, running from each of our regions. A failure in some regions marks the row degraded; failures from every region mark it down and open an outage.
| Check | Target | Expects | Interval |
|---|---|---|---|
Website supabase.com is unreachable. | httpsupabase.com | HTTP 200 | 1 min |
Management API The management API is not answering. The dashboard and CLI cannot manage projects. | httpapi.supabase.com/v1/projects | HTTP 401 | 2 min |
Dashboard The Supabase dashboard is unreachable. | httpsupabase.com/dashboard/sign-in | HTTP 200 | 2 min |
Documentation Supabase's documentation is unreachable. | httpsupabase.com/docs | HTTP 200 | 5 min |
Official status feed Supabase's status page is unreachable. | httpstatus.supabase.com/api/v2/status.json | HTTP 200 | 5 min |
For component-level detail and incident write-ups from the vendor, see Supabase's official status page.
Recent Supabase outages we detected
An outage is recorded when a probe fails from every monitoring region and closed when it recovers. Partial and single-region problems show as degraded above but are not listed here.
Supabase is up. Is your Supabase integration?
The incidents that actually hurt are usually not global outages. They are the parts of your own system that depend on Supabase and fail quietly. Here is what teams that rely on Supabase monitor on their side.
Your project's REST and Auth endpoints
Probe https://<ref>.supabase.co/rest/v1/ and /auth/v1/health with your anon key. That tells you about your project in your region, which is what your users experience.
HTTP monitoring with headersLogin and signup flows
Auth can be degraded while the database is fine. A browser check that actually signs in catches it.
Browser checksSupabase status: frequently asked questions
Each project is its own Postgres instance. Connection pool exhaustion, a paused free-tier project, or a compute limit will make your project fail while the platform is healthy. Probing your own project endpoint is the only way to see that.
Look at the per-region results above. If our probes fail from every region, Supabase has a real outage and it will appear in the outage list. If they succeed everywhere, the problem is most likely on your side: your network, DNS resolver, a browser extension, a corporate proxy, or your own integration. If only some regions fail, Supabase may have a regional incident that does not affect you.
Every probe runs at least every five minutes from each monitoring region, and most run every minute. This page refreshes its data every minute. Uptime figures are calculated from all checks across all regions.
Official status is updated by people after an incident is confirmed and often lags the first failures by many minutes; our probes react within a minute or two. In the other direction, we only see public endpoints, so an internal incident may not show on our probes. Use both.
Yes. Use "Notify me about Supabase" above: your upti.my workspace follows these exact checks, free plan included, and every outage opens an incident there and routes alerts to Slack, email, webhooks, or on-call. Nothing is duplicated and it doesn't use your monitor quota. Better still, also monitor your own dependency on Supabase: the API route, webhook receiver, or scheduled job that calls it, so you learn about the failure that actually affects your users.
Related
Other databases & data infrastructure
upti.my is not affiliated with Supabase. Supabase and related marks are the property of their respective owners and are used here only to identify the service being measured. Results reflect the reachability of public endpoints from our monitoring regions and may differ from the vendor's own reporting.