Is Supabase down?
Operationalchecked 3 minutes ago
We reached Supabase from all 10 regions we check.
As of Oct 5, 2026, 8:13 PM UTC, Supabase answered RealUptime's probes in all 10 regions that returned a reading.
Last outage: 1h 5m on Sep 15, 2026 (web surface, from Europe, South America, US-East, UK, US-Central, Southeast Asia, US-West, Australia and Canada).
Supabase reports: All systems operational (“All Systems Operational”)
Supabase reports an active incident: Intermittent latency in Eastern US (minor incident, since Sep 29, 2026, 4:26 PM UTC). Their summary currently reads “All systems operational” even so: the summary and the incident come from two separately polled feeds and can disagree.
Supabase's own component breakdown, as they publish it
- AnalyticsOperational
- ap-northeast-1Operational
- API GatewayOperational
- ap-northeast-2Operational
- AuthOperational
- ap-south-1Operational
- Connection PoolerOperational
- ap-southeast-1Operational
- DashboardOperational
- ap-southeast-2Operational
- DatabaseOperational
- ca-central-1Operational
- Edge FunctionsOperational
- eu-central-1Operational
- Management APIOperational
- eu-central-2Operational
- RealtimeOperational
- eu-north-1Operational
- StorageOperational
- eu-west-1Operational
- eu-west-2Operational
- eu-west-3Operational
- sa-east-1Operational
- us-east-1Operational
- us-east-2Operational
- us-west-1Operational
- us-west-2Operational
These are Supabase's components, named and scored by Supabase. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.
This is Supabase's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.
Supabase response time, by region
Is it Supabase, or is it you?
Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Supabase -- it cannot diagnose Supabase's own systems.
Get an email when we see Supabase go down, and when it is back
Get told when we measure this
We will tell you when our probes stop reaching Supabase, and again when they can reach it again. That is our own measurement from ten regions, not Supabase's status page. No account, no card.
What we measured, and what people reported
- North AmericaOperationalUS-East, US-West, US-Central, Canada
- US-EastOperationallatency: 370msstatus code: 401checked: Oct 5, 2026, 7:53 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Supabase normally. We do not have enough reports from US-East to say anything about what people there are seeing.
- US-WestOperationallatency: 415msstatus code: 401checked: Oct 5, 2026, 7:47 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Supabase normally. We do not have enough reports from US-West to say anything about what people there are seeing.
- US-CentralOperationallatency: 100msstatus code: 401checked: Oct 5, 2026, 8:11 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Supabase normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
- CanadaOperationallatency: 107msstatus code: 401checked: Oct 5, 2026, 8:12 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Supabase normally. We do not have enough reports from Canada to say anything about what people there are seeing.
- South AmericaOperationallatency: 183msstatus code: 401checked: Oct 5, 2026, 8:13 PM UTC0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Supabase normally. We do not have enough reports from South America to say anything about what people there are seeing.
- EuropeOperationalEurope, UK
- EuropeOperationallatency: 91msstatus code: 401checked: Oct 5, 2026, 7:51 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Supabase normally. We do not have enough reports from Europe to say anything about what people there are seeing.
- UKOperationallatency: 273msstatus code: 401checked: Oct 5, 2026, 7:21 PM UTC0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Supabase normally. We do not have enough reports from UK to say anything about what people there are seeing.
- Asia PacificOperationalAsia-Pacific, Southeast Asia, Australia
- Asia-PacificOperationallatency: 93msstatus code: 401checked: Oct 5, 2026, 7:50 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Supabase normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
- Southeast AsiaOperationallatency: 143msstatus code: 401checked: Oct 5, 2026, 8:11 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Supabase normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
- AustraliaOperationallatency: 505msstatus code: 401checked: Oct 5, 2026, 7:17 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Supabase normally. We do not have enough reports from Australia to say anything about what people there are seeing.
Somewhere else or not sure: 0 people in the last 5 minutes
These are unverified reports from people using Supabase, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Supabase yet, which is not evidence that nothing is wrong.
Recent outages
measured entries are our own probes' readings; declared entries are the vendor's. How this check works
We have been measuring Supabase since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.
Need this in writing? Generate an SLA evidence report for Supabase covering any window you pick, with our measurements and Supabase's own claim at the time, side by side.
Full availability history for Supabase: 90-day availability by region, month-by-month uptime, and every incident on record.
Monitor your own site the same way
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversPut this badge in your README
Live, from this page's own readings.[](https://realuptime.io/outages/supabase)<a href="https://realuptime.io/outages/supabase"><img src="https://realuptime.io/outages/supabase/badge.svg?days=30" alt="Supabase uptime measured by RealUptime"></a>The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.
What Supabase's SLA implies, from our measurement
Below your target
We measured 1h 5m of downtime for Supabase over the last 30 days, which is 99.8494% uptime by our reading. A 99.9% target allows 43 minutes over that period.
That is 21 minutes more than the target allows. The figure above is the pro-rata share of one month's fee for the time we could not reach it. Your contract probably uses a tiered credit schedule instead, and we have not read it, so treat this as one common way to reason about a credit rather than the amount they owe.
This is computed from our own probe measurements, not from Supabase's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.