Is Supabase down right now?

Operational. We reached Supabase from all 4 regions we check.

How does RealUptime check if Supabase is down?

RealUptime checks Supabase with scheduled HTTP probes against its public, unauthenticated functional endpoints, run from named regions on a fixed cadence, plus an extra confirmation probe whenever a signal suggests a problem. This verifies that the functional endpoints we probe actually answer, not that every feature of Supabase works end to end.

What does "degraded" mean for Supabase?

Degraded means Supabase answered our probe but at several times its own seven-day median response time. Degraded only ever applies to a reading that answered: a surface that is down, or one that refused our probe, is reported as down or awaiting data instead, never softened into "degraded".

What is Supabase's current response time?

RealUptime's most recent measured response time for Supabase, by region: US-East: 709 ms, US-West: 347 ms, Europe: 240 ms, Asia-Pacific: 788 ms. This is the latest single probe reading per region, not an average.

When did RealUptime last check Supabase?

RealUptime's probes last checked Supabase at 2026-09-03T01:27:25.751Z.

Is Supabase down?

Short linkrlup.io/down/supabase

I'm having a problem

Operationalchecked 2 minutes ago

We reached Supabase from all 4 regions we check.

Functional endpoints verified

No outage recorded in the 14 days we have measured Supabase (since Aug 20, 2026).

Supabase's own status page reports "Partially Degraded Service." That is their claim, not our measurement: our probes are currently reaching Supabase, and an incident they declare can affect parts of the service our checks do not exercise. We show both and never merge them.

our independent probeslive · checked Sep 3, 2026, 1:27 AM UTC

US-East709 msOperational

US-West347 msOperational

Europe240 msOperational

Asia-Pacific788 msOperational

their status pagetheir claim, not our reading

Supabase reports: Minor incident (“Partially Degraded Service”)

from Supabase's own status page, checked Sep 3, 2026, 12:27 AM UTC

Supabase's status page reports Partially Degraded Service. Our probes are currently reaching Supabase successfully with normal latency. RealUptime's independent checks are currently succeeding from all 4 regions. These observations can coexist: a partial error-rate degradation on their side does not have to affect every request. Our checks measure whether a single request succeeds, not the vendor's internal error rate, so this can happen when an issue affects only part of a service that our simple check does not exercise. We show what we measured, not what they report: differences can mean a partial or user-specific issue that a simple reachability check won't catch. Read both before you draw a conclusion.

Supabase's own component breakdown, as they publish it

AnalyticsOperational
ap-northeast-1Operational
ap-northeast-2Operational
API GatewayDegraded performance
ap-south-1Operational
AuthOperational
ap-southeast-1Operational
Connection PoolerOperational
ap-southeast-2Operational
DashboardOperational
ca-central-1Operational
DatabaseOperational
Edge FunctionsOperational
eu-central-1Operational
eu-central-2Operational
Management APIOperational
eu-north-1Operational
RealtimeOperational
eu-west-1Operational
StorageOperational
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

US-East

711msp95 · latest

2s1s0ms

Aug 5Aug 19Sep 3

US-West

338msp95 · latest

1s500ms0ms

Aug 5Aug 19Sep 3

Europe

90msp95 · latest

1s500ms0ms

Aug 5Aug 19Sep 3

Asia-Pacific

925msp95 · latest

2s1s0ms

Aug 5Aug 19Sep 3

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.

What we measured, and what people reported

US-East
Operationallatency: 709msstatus code: 401checked: Sep 3, 2026, 12:43 AM UTC
0 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-West
Operationallatency: 347msstatus code: 401checked: Sep 3, 2026, 12:47 AM UTC
0 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.
Europe
Operationallatency: 240msstatus code: 401checked: Sep 3, 2026, 1:27 AM UTC
0 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.
Asia-Pacific
Operationallatency: 788msstatus code: 401checked: Sep 3, 2026, 12:46 AM UTC
0 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.
US-Central
Not monitored from this regionSupabase is not monitored from this region.
0 people in the last 5 minutesNot enough reports to say
Canada
Not monitored from this regionSupabase is not monitored from this region.
0 people in the last 5 minutesNot enough reports to say
UK
Not monitored from this regionSupabase is not monitored from this region.
0 people in the last 5 minutesNot enough reports to say
Southeast Asia
Not monitored from this regionSupabase is not monitored from this region.
0 people in the last 5 minutesNot enough reports to say
Australia
Not monitored from this regionSupabase is not monitored from this region.
0 people in the last 5 minutesNot enough reports to say
South America
Not monitored from this regionSupabase is not monitored from this region.
0 people in the last 5 minutesNot enough reports to say

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

User unable to log in to Supabase Dashboard, 1h 49mdeclared on their status page2026-09-01

Project Creation Failures, 2h 38mdeclared on their status page2026-08-31

Projects failing to load Supautils in multiple regions, 1mdeclared on their status page2026-08-28

Increased response times for requests, 94h 37mdeclared on their status page2026-08-27

pgBouncer issues on some older projects, 22h 35mdeclared on their status page2026-08-26

Increased rates of Pooler connection timeouts in us-east-1, 1h 12mdeclared on their status page2026-08-24

Issues affecting automatic disk resizing, 2hdeclared on their status page2026-08-24

Error spikes in one of the ap-northeast-2 Supavisor clusters, 3h 49mdeclared on their status page2026-08-24

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 servers

Tell me when this goes down

Put this badge in your README

Live, from this page's own readings.

[![Supabase uptime measured by RealUptime](https://realuptime.io/outages/supabase/badge.svg?days=30)](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

Window

What you pay per month

Uptime target in your contract

Include outages only one region saw (none)

At or above your target

We measured none of downtime for Supabase over the 337h 29m since we started watching it on 2026-08-20, which is 100% uptime by our reading. A 99.9% target allows 20 minutes over that period.

By our measurement there is no shortfall to claim for this period.

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.

What we check

primaryfunctional

https://api.supabase.com/v1/projects

secondary

https://status.supabase.com/

RealUptime is not affiliated with Supabase; the name identifies what we measured, and nothing here speaks for Supabase's own team. We send a single web request to Supabase from 4 regions on our own schedule and time the response. We do not see inside Supabase's systems, do not use an account or real transaction, and are not the same signal Supabase's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Supabase is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Supabase operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. Read the full methodology.

Related services

Akamai Amplitude Anthropic Auth0 AWS (Amazon Web Services)