Is Supabase down?
Vendor reports an incidentWhat Supabase reports
Supabase reports an incident on its status page: API Gateway Request Issues.
Impact: minor. Since 2026-10-22 17:01 UTC.
Latest update, 2026-10-22 18:17 UTC: We have additional mitigations we will be deploying to reinforce our backplane. We will leave this statuspage up and in Monitoring status until all mitigations are deployed. Updates will be forthcoming if anything changes that could impact customers.
Our regional reading
This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.
Checks passingchecked 21 minutes ago
Our checks of Supabase pass from all 10 regions we check.
As of Oct 23, 2026, 1:40 AM UTC, RealUptime's checks of Supabase passed in all 10 regions that returned a reading.
Supabase reports: All systems operational (“All Systems Operational”)
Supabase reports an active incident: API Gateway Request Issues (minor incident, since Oct 22, 2026, 5:01 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
- ap-east-1Operational
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
Check your own site while you wait on Supabase
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.
Email me when Supabase reports an incident on its status page, and again when it reports it resolved.
Get an email when Supabase reports an incident
Email me when Supabase reports an incident on its status page, and again when it reports it resolved. No account, no card.
What our checks show, and what people reported
- North AmericaChecks passingUS-East, US-West, US-Central, Canada
- US-EastChecks passinglatency: 43msstatus code: 401checked: Oct 23, 2026, 1:39 AM 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-WestChecks passinglatency: 290msstatus code: 401checked: Oct 23, 2026, 1:40 AM 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-CentralChecks passinglatency: 100msstatus code: 401checked: Oct 23, 2026, 1:10 AM 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.
- CanadaChecks passinglatency: 82msstatus code: 401checked: Oct 23, 2026, 1:10 AM 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 AmericaChecks passinglatency: 217msstatus code: 401checked: Oct 23, 2026, 1:09 AM 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.
- EuropeChecks passingEurope, UK
- EuropeChecks passinglatency: 56msstatus code: 401checked: Oct 23, 2026, 1:40 AM 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.
- UKChecks passinglatency: 52msstatus code: 401checked: Oct 23, 2026, 1:09 AM 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 PacificChecks passingAsia-Pacific, Southeast Asia, Australia
- Asia-PacificChecks passinglatency: 242msstatus code: 401checked: Oct 23, 2026, 1:39 AM 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 AsiaChecks passinglatency: 224msstatus code: 401checked: Oct 23, 2026, 1:10 AM 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.
- AustraliaChecks passinglatency: 203msstatus code: 401checked: Oct 23, 2026, 1:09 AM 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 probe events
check 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 check readings and Supabase's own claim at the time, side by side.
Full check history for Supabase: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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 by RealUptime's checks" height="20"></a>The badge shows the share of our checks that passed over the last 30 days. 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.
To cite this page: RealUptime, "Is Supabase down?", https://realuptime.io/outages/supabase. The readings change with every check, so give the date you read them.
Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.
What we check
What our check can and cannot see
A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.
Host checked: api.supabase.com