Space for ads
Checked every 5 minutes · How we measure this
As of 15:10 EDT on 8 Sep 2026, Supabase reports degraded or failing components on its own status page. Our probe still reached supabase.com in 275 ms, with 100.00% availability over the last 24 hours.
Checked every 5 minutes · last checked 8 minutes ago
The line is response time measured from our probe to supabase.com, which rises when the service slows down. Shaded red marks intervals where checks actually failed. It excludes your own connection and browser rendering.
Reported by Supabase on its own status page. Verify on their status page.
Supabase Analytics powers logs, metrics and reports for all users.
API Gateway for all Supabase Products
Authenticate and authorize users
Supavisor is a cloud-native, multi-tenant Postgres connection pooler.
The studio, docs and primary website at https://supabase.com
The Postgres database and the REST Data APIs powered by PostgREST
Globally deployed serverless functions
Manage Supabase projects programmatically.
Send and receive messages to connected clients.
Store and serve any type of digital content
0 problem reports
Supabase degraded performance
Detected by DownBits probe
Network access issues affecting a limited number of users in Myanmar
Supabase has taken the steps it can to address the blockage. We recommend customers contact their ISP for assistance: https://supabase.com/blog/navigating-regional-network-blocks
Confirmed on the vendor status page
401 errors due to JWT rejections
Testing results have been positive. Following some additional checks today, we plan to expand the rollout. We’ll continue to monitor progress and provide further updates as they become available.
Confirmed on the vendor status page
Supabase is reporting degraded or failing components on its own status page. Our probe is still reaching supabase.com normally — 24-hour availability from our checks is 100.00% — so the front door is up while something behind it is not. The component list on this page shows which parts Supabase says are affected. Last checked 8 minutes ago.
Measured from our automated checks, Supabase has been available 100.00% over 24 hours, 100.00% over 7 days, 100.00% over 30 days. We recorded 3 incidents in the last 30 days.
Supabase has averaged 239 ms across our successful checks in the past 24 hours, which is fast — comfortably within what a healthy service should return. Response time is measured from our probe to supabase.com and does not include rendering time in your browser.
Our probe is also failing to reach supabase.com normally, so this is not just you. Use the report button on this page to add your own signal — when several people report the same problem within a short window, it appears on the chart above.
A working marketing site does not mean a working API. Call the API host directly — curl -s -o /dev/null -w "%{http_code}" https://supabase.com/ — and check the vendor status page linked above for component-level detail, since one component can fail while the rest stay green.
HTTP 429 and 529 mean you are being throttled, not that the service is down. Inspect the response headers for a retry-after value and back off exponentially rather than retrying immediately.
A 401 or 403 is an authentication problem on your side. Rotated keys, an expired billing method, or a revoked token all present as sudden total failure.
Open any other site. If nothing loads, the issue is your network rather than Supabase. On Windows run ping supabase.com and nslookup supabase.com in Command Prompt; on macOS or Linux use Terminal. A DNS failure and a server failure look identical in a browser but are very different problems.
Load supabase.com in a private or incognito window. If it works there, clear cookies and site data for supabase.com in your normal browser rather than clearing everything.
Switch from Wi-Fi to mobile data, or vice versa. Regional ISP routing problems are common and often affect one carrier while others are unaffected.
We link the vendor status page so you can check our reading against theirs.
No comments received
