Space for ads
Checked every 5 minutes · How we measure this
As of 02:55 EDT on 8 Oct 2026, supabase.com responded to our check in 219 ms, with 100.00% availability over the last 24 hours.
Checked every 5 minutes · last checked 9 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.
0 problem reports
Upgrade Issues
The fix has been implemented. Upgrade operation has been restored. We will monitor for stability.
Confirmed on the vendor status page
Supabase degraded performance
DownBits detected degraded performance on Supabase between 6 Oct 2026, 13:35 – 14:40 IST, lasting ongoing. Detected across 13 consecutive automated checks of supabase.com.
Detected by DownBits probe
Increased errors on management api leading to project operation failures
We have identified a rollout causing error increase on management api dependant services, which is causing project operation failures and FGA Authentication errors across multiple functions. We have implementing a fix and observing recovery. Our teams are continuing to monitor for full resolution.
Confirmed on the vendor status page
Supabase degraded performance
DownBits detected degraded performance on Supabase between 30 Sep 2026, 20:40 – 00:25 IST, lasting ongoing. Detected across 1485 consecutive automated checks of supabase.com.
Detected by DownBits probe
Intermittent latency in Eastern US
A fix for this issue has been implemented and our data shows recovery for users on projects that have previously been affected. We expect this situation to be resolved, but will keep monitoring for a while until fully resolving this incident.
Confirmed on the vendor status page
Log Ingestion Degradation
Log ingestion has recovered. We are monitoring for continued stability.
Confirmed on the vendor status page
Project Lifecycle Issues in eu-west-1
We are continuing to monitor to ensure ongoing stability.
Confirmed on the vendor status page
Permission errors in the Supabase Dashboard
We have applied a fix, and administrative operations in the Supabase Dashboard are now completing as expected. We are monitoring the results to ensure the issue is fully resolved.
Confirmed on the vendor status page
Supabase CLI CI workflow failures
We are no longer seeing rate limiting issues affecting Supabase CLI CI workflows. We're continuing to monitor the service for stability while we roll out a fallback patch to improve resilience and help prevent the issue from recurring.
Confirmed on the vendor status page
Storage search failing for restored projects
A fix has been implemented for the affected tenants and we are monitoring the results. We will continue to monitor the situation and will provide further updates as more information becomes available.
Confirmed on the vendor status page
Increased error rate in project creation and project restore
A fix has been implemented and we are monitoring the results.
Confirmed on the vendor status page
Supavisor connection disruptions in EU West 1 (Ireland)
The affected Supavisor node has been restarted, and error rates have returned to normal levels. We’ll continue to monitor the service to ensure stability.
Confirmed on the vendor status page
Project creations are degraded in multiple regions
We have identified increased latency in Project creations in these regions from 0730 UTC to 0805 UTC: ap-northeast-1 ap-northeast-2 eu-central-1 eu-central-2 eu-north-1 eu-west-1 eu-west-3 us-west-1 The latency has since recovered and our teams are monitoring for full recovery. Existing project availability has not been impacted.
Confirmed on the vendor status page
Project Lifecycle Activity Degradation
Project lifecycle operations have remained stable. We will continue to monitor the platform.
Confirmed on the vendor status page
Query slowness for projects running Postgres version 14 in us-east-1 and ap-northeast-2
The fix has been rolled out to us-east-1. We will continue to monitor both regions for stability.
Confirmed on the vendor status page
Supabase is responding normally. Our last automated check of supabase.com completed 9 minutes ago and succeeded in 219 ms. Over the past 24 hours the service answered 100.00% of our checks.
Measured from our automated checks, Supabase has been available 100.00% over 24 hours, 99.85% over 7 days, 99.86% over 30 days. We recorded 19 incidents in the last 30 days.
Supabase has averaged 208 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.
The most recent incident DownBits recorded for Supabase began on 6 October 2026 at 13:35 IST and lasted 1 hr 5 min. It was logged as degraded performance. Detected by DownBits probe.
Our probe is reaching supabase.com normally right now, so the problem is more likely to be local to you than a full outage. 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
