Is it down for me?
Testing supabase.com from your device…
S
Is Supabase down right now?
Most checked
Not listed? Type its address, like example.com, to check it now.
Supabase is up
Our last check from one location (UtiBox server · Newark, US) found it answering normally in 178 ms.
Checked from Newark, USNext check in 1 s
Response timelive · Newark, US
178ms
Newark, USUS178 ms
Checking from 12 regions…
Request waterfall
Do all locations agree?
Live counters
People checking
Live01 · Is it working?
Status at a glance
UtiBox check · our ownUp
178ms
Supabase is up. Total time to the final page on our latest check.
FromNewark, US
ServerNear Walnut, US
Checked Full result
Community · quick voteLast 24 hours
Is Supabase working for you?
Thanks, you said it works
What’s the problem? Pick one to send your answer.
No votes yet. Be the first to answer.
0 answers in the last 24 hours · 0 problem reports
One answer per person, counted for 24 hours.
Answers per hour
24 h agoNow
No answers in the last 24 hours
See what people say 0 posts today
Regionsour server so far
1/1 up
Only our server so far. The regional checks run when the page opens.
- Newark · US178 msour server
Median 178 mslocations by DB-IP
90-day history
UpDegradedDownNo data
—No measurements yet
90 days agoToday
Last 24 hours · response time, ms
User reports are in CommunityFrom the communityLive counts
0posts today
No posts yet. Be the first to say how Supabase is working for you.
- “It’s down” in the last hour0
- People who voted, 24 h0
02 · How it was reached
The journey to supabase.com
Our latest check, step by step. Tap a step to open its full record.
Latest check ·
Response by regionFrom Newark, US to supabase.com (server near Walnut, US)
-
- DNS lookup27 ms
- Connect12 ms
- TLS handshake55 ms
- First byte98 ms
Map locations are approximate, from IP addresses.IP location by DB-IP
Test from another country
Is Supabase blocked or down in your country?
Our main check runs from Newark, US. Run the same test from up to 3 internet providers in another country to see whether supabase.com is blocked or broken there.
Probes by Globalping, a free network run by jsDelivr. One test uses up to 3 probes, home and mobile providers first.
For long-term evidence of website blocking, see OONI Explorer, where volunteers measure censorship around the world.
Supabase not working? Try these fixes
01
Reload without cache
Press Ctrl + Shift + R (⌘ + Shift + R on a Mac).
02
Try a private window
Rules out extensions and stored cookies.
03
Switch networks
Move from Wi-Fi to mobile data, or the other way round.
04
Flush DNS
Windows: ipconfig /flushdns · macOS: sudo dscacheutil -flushcache
05
Pause VPN or ad blocker
They can block or reroute requests.
06
Check the time on your device
A wrong clock breaks secure connections.
Still stuck? Find out if the problem is your own connection.Test my connection
Outage historyAll outages
| Date | Problem | Duration | Peak reports | Status |
|---|---|---|---|---|
| No confirmed incidents recorded for Supabase. | ||||
Share this statusFree to embed
The badge shows whether supabase.com is up and the share of our checks that were up over the last 7 days. It updates every few minutes.
Status report (PDF)
A landscape PDF of this page: the result now, 90 days of uptime, every layer of the latest check, other places, outages and the response headers. Each copy gets its own reference and a QR code anyone can scan to verify it.
Community · supabase.com
Supabase community
What people say about Supabase, in their own words, kept apart from our own checks.
0posts today
0“it’s down” in the last hour
0people voted, 24 h
Live counts · real numbers, refreshed with the page
Share how Supabase is working for you
What’s the problem? (optional)
0 / 280
Optional. We never show your exact location.
Posts are public after a quick review. Don’t share personal details or links.
Posts
No posts yet.
Be the first to say how Supabase is working for you.
No posts of this type yet.
That’s every post from the last 30 days.
Is Supabase working for you?
Last 24 hours0say it works
0have a problem
No votes yet
What’s the problem? Pick one to send your answer.
One answer per person, counted for 24 hours.
User reports, last 24 h
0 total24 h ago12 hNow
Problem types
last 24 hoursHaving one of these? Tap it to start a report.
Official · provider-reported
Supabase official status
What Supabase status says about its own service, read from its public status page. A separate signal from our own check and from what people report.
Official · reported by Supabase status
status.supabase.com
Operational
All Systems Operational
Read from the official feed · the provider last updated it .
What Supabase status reports about Supabase. A site can answer our own check while the provider reports a problem with one of its features, and the other way round.
Status information is provided by the service operator. UtiBox is independent and isn’t affiliated with Supabase. It may not reflect regional or account-specific problems.
Components
1 of 1 operational- ap-east-1Operational
Open incidents
None
None reported for Supabase in the last report we read.
Planned maintenance · 1
Scheduled maintenance: Shared Pooler (Supavisor), eu-central-2 Scheduled
updated
Our record of the official status
Last 30 days · the worst state we read each day30 days agoToday
OperationalDegradedNot read
Our first successful read in this window was on 9 Nov 2026.
Past official updates
Newest first29 resolved updates since Sep 2026 · 3 major · last one 12 Nov 2026 (1 h 18 min)
- Nov 2026 · 11
-
Elevated Error rates for All Supabase project APIs
“We are currently seeing slightly increased error rates for API requests to the Data APIs, Auth, Storage, and other HTTP API routes across all regions The team is currently investigating.”
No components listedRead on Supabase status -
Database Connection Errors
“We have observed increased connection errors, some databases may be unavailable with all services unhealthy.”
No components listedRead on Supabase status -
Storage request degradation in eu-west-1
“Between 14:14-14:18 UTC and 14:25-14:29, Storage requests may have been slow or aborted in the eu-west-1 region. This issue has been resolved and we do not expect recurrence. We are monitoring the region.”
No components listedRead on Supabase status -
Project Lifecycle Issues in ap-northeast-1
“Project lifecycle operations have been impacted by an issue in ap-northeast-1. We are investigating along with our upstream provider.”
No components listedRead on Supabase status -
Interruption in connections to Supavisor in eu-west-2
“We detected an interruption in connections to Supavisor in eu-west-2 between 09:42 and 09:52 GMT which may have affected connections for some users. This has since been resolved and we are monitoring to ensure all systems have fully recovered.”
No components listedRead on Supabase status -
Increased Errors with Project Lifecycle Operations in US-West-2
“All Project Lifecycle operations are currently impacted by an upstream provider incident affecting EC2 instances in US-West-2. Currently up and active projects are unaffected and remain healthy. New project creation, unpauses, restore actions, project size changes, restarts and other lifecycle operations may encounter errors. We advise against taking these actions in US-West-2 at this time while we work with our provider to resolve this issue.”
No components listedRead on Supabase status -
Intermittent 502/503 errors for pg_net calls to Edge Functions
“We are seeing intermittent 502 and 503 errors affecting Edge Functions requests in ap-southeast-1. We will provide updates and more information becomes available.”
No components listedRead on Supabase status -
Storage issues in us-east-1 and eu-central-1
“We have identified some customers in us-east-1 are experiencing 5XX errors when interacting with our Storage components. We are investigating.”
No components listedRead on Supabase status -
Intermittent errors on Supavisor Shared Pooler in us-east-2
“Between 2026-11-04 00:02 and 00:50 UTC there were elevated errors on Supavisor Shared Pooler in the us-east-2 region. Errors have subsided and things are back to normal. Example errors were ``` ClientHandler: (ECHECKOUTFAILED) checkout failed due to %{"C" => "08006", "M" => "Failed to connect to database: {:error, :timeout} DbHandler: Connection failed {:error, :timeout} to ~c".......us-east-2.compute.internal" ```”
No components listedRead on Supabase status -
Management API Postgres config updates overwriting previous updates
“We are actively correcting an issue with the Management API: • Postgres Config changes only save the latest values sent, past changes are not being saved For now please refrain from not making any Postgres Config changes via the [Management API](https://supabase.com/docs/reference/api/introduction) or in the [Database Settings Dashboard](https://supabase.com/dashboard/project/\_/database/settings)”
No components listedRead on Supabase status -
Storage uploads failing in us-east-1
“We are investigating an error with Storage uploads returning 5xx errors for us-east-1 users. We will be confirming more information shortly.”
No components listedRead on Supabase status - Oct 2026 · 17
-
PG15 -> PG17 Upgrade Failures
“We are actively investigating some reports of failed PG15 -> PG17 upgrades. We have identified an error in an AMI release from today and are rolling it back to unblock upgrades.”
No components listedRead on Supabase status -
Logs degraded in multiple regions
“We are currently investigating degraded Logs functionality in multiple regions. Some users may experience delayed, missing, or unavailable logs in the Dashboard and Logs API. Other services, including your database and APIs, are not affected at this time. Our team is actively investigating. We'll post another update as soon as we have one.”
No components listedRead on Supabase status -
Delayed Log Delivery from 14:10 - 15:30 UTC
“Between 14:10 - 15:30 UTC we have experienced an issue in delivering logs, leading to a delay of about 7–8 minutes. Most affected events have now been recovered - a small subset of events is still being re-inserted and we will confirm once completed.”
No components listedRead on Supabase status -
Log Drain Issues
“Customers using log drains in some regions may be missing some routed logs for a subset of components. We've rolled back changes and are continuing to investigate.”
No components listedRead on Supabase status -
Elevated Mgmt API Error Rates in Multiple Regions
“We have noticed issues with requests coming to our API gateway. We are investigating.”
No components listedRead on Supabase status -
Elevated Mgmt API Error Rates in Multiple Regions
“We are investigating elevated error rates and increased response times on the Management API across multiple regions. Some operations that depend on it, such as creating new projects, may fail or be slow.”
No components listedRead on Supabase status -
Project lifecycle operation errors in the EU region
“We identified increased error rates in project lifecycle operations (create, restore, pauses, etc.) in the EU region since 21 Oct 23:00 UTC. A mitigation has been put in place and error rates have reduced to normal levels. We are monitoring the situation and are working on fixing affected projects.”
No components listedRead on Supabase status -
Intermittent connection errors via the connection pooler in us-east-1
“Between 22:10 and 22:51 UTC on October 9, 2026, about 1% of new database connections made through the Shared Pooler (Supavisor) in us-east-1 failed with "Failed to connect to database" timeout errors. The cause of the failures was an incident at our cloud provider which affected network traffic between availability zones. Supabase Project databases were not affected, and connections that had already been open prior to the incident remained open. The issue was resolved at 22:51 UTC. Clients that retried on connection errors would have reconnected successfully.”
No components listedRead on Supabase status -
Project lifecycle operations such as project creation, pausing, and restoration, in all regions
“We are investigating an issue affecting project lifecycle operations such as project creation, pausing, and restoration, in all regions. We’ll provide further updates as more information becomes available.”
No components listedRead on Supabase status -
Projects stuck in restarting state
“Some projects in us-east-2 are stuck in restarting state. We are actively investigating this and will provide more updates as information becomes available.”
No components listedRead on Supabase status -
Support Form Errors
“We have identified an issue with support ticket creation for some customers, we have a fix in development.”
No components listedRead on Supabase status -
Project creation errors ap-ne1
“Due to an ongoing upstream provider outage, we are remediating project creation errors in apne-1. Customers may see errors in creating or unpausing a project from this region. We are working to re-direct traffic to non-impacted regions and awaiting updates from our dependant provider.”
No components listedRead on Supabase status -
Realtime latency
“We are experiencing increased latency with Realtime and are actively investigating.”
No components listedRead on Supabase status -
Edge Function Degradation
“We are experiencing significant degraded performance across edge functions, mainly affecting deploy and retrieving function body. We have identified the root cause and are working on the fix now.”
No components listedRead on Supabase status -
Log ingestion impaired
“Log ingestion is currently impaired. Logs may be delayed or unavailable. We are investigating the issue and working to restore normal functionality. We will provide further updates as more information becomes available.”
No components listedRead on Supabase status -
Upgrade Issues
“We have observed failures in attempted upgrades to 17.11.0.003. We are investigating.”
No components listedRead on Supabase status -
Increased errors on management api leading to project operation failures
“We are investigating an increase in errors on project update flows including creation, pausing/unpausing and upgrading across multiple regions.”
No components listedRead on Supabase status - Sep 2026 · 1
-
Intermittent latency in Eastern US
“We have identified an issue with increased latency for clients in the eastern US during spikes caused by bursty traffic. This is most noticeable during EDT working hours around the :00 and :30 hour marks. We are actively working on a fix. We will provide updates as the fix is implemented.”
No components listedRead on Supabase status
No updates of this kind.
From Supabase status’s public status history. UtiBox keeps the official updates it reads for 180 days.
Frequently asked questions
Is Supabase down right now?
At our last check from UtiBox server · Newark, US, Supabase was up and answering normally. The page refreshes the check automatically.
What does Supabase’s official status page say?
The official status page (status.supabase.com) reports “Operational” for Supabase. We read it every few minutes. It’s separate from our own check of the supabase.com website above, so the two can differ.
Why is Supabase not working for me?
If it’s up here but not for you, the problem is usually local: your connection, DNS, a browser extension, a VPN or a block on your network. Try the fixes on this page, then the Is It My Internet? check.
How do you check Supabase?
Our server requests supabase.com and looks at every layer: DNS, the connection, the TLS certificate, the HTTP answer, redirects and the page content. We also check it from up to 12 locations in other countries, using two free probe networks (Globalping and check-host.net), so a regional outage can show here too.
How often is this page updated?
A result is shared for 60 seconds when the site is up and 30 seconds when it has problems, then checked again. You can refresh it yourself after 30 seconds.
Can I get an alert when it’s back?
Yes. Use “Alert me when it’s back” and we’ll send one email when our check reaches it again. Guests confirm their address first.