Space for ads
Checked every 5 minutes · How we measure this
As of 18:30 EDT on 23 Oct 2026, supabase.com responded to our check in 284 ms, with 100.00% availability over the last 24 hours.
Checked every 5 minutes · last checked 5 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
Log Drain Issues
The rollback has restored log drains to normal operation. We will monitor for continued functionality.
Confirmed on the vendor status page
Elevated Mgmt API Error Rates in Multiple Regions
We have additional mitigations we will be deploying to reinforce the Management API. Updates will be forthcoming if anything changes that could impact customers.
Confirmed on the vendor status page
Elevated Mgmt API Error Rates in Multiple Regions
A mitigation has been applied. Error rates and latency have returned to normal levels. We’re continuing to monitor to ensure sustained stability before resolving this incident.
Confirmed on the vendor status page
Project lifecycle operation errors in the EU region
Error rates remain at normal levels. We’re continuing to monitor to confirm sustained stability before resolving this incident.
Confirmed on the vendor status page
Project lifecycle operations such as project creation, pausing, and restoration, in all regions
A fix has been applied, and we have observed a reduction in project lifecycle job failures. We are continuing to monitor the recovery to ensure normal operations remain stable.
Confirmed on the vendor status page
Projects stuck in restarting state
The fix has fully rolled out. Projects are no longer stuck in a restarting state. We will continue to monitor the situation.
Confirmed on the vendor status page
Support Form Errors
The fix has been deployed and ticket creation has returned to normal. We will continue to monitor.
Confirmed on the vendor status page
Project creation errors ap-ne1
Our upstream partner has confirmed the issue is resolved. We are working to restore project creation traffic back to the region and monitor for full recovery in ap-northeast-1.
Confirmed on the vendor status page
Realtime latency
We have stabilised impacted users and enabled improvements to our Realtime infrastructure. We will continue to monitor for full recovery.
Confirmed on the vendor status page
Edge Function Degradation
Edge Functions deployments have returned to normal levels. We will continue monitoring for full recovery.
Confirmed on the vendor status page
Log ingestion impaired
The fix has been implemented, and the system has returned to normal operation. Log ingestion is back to normal, and we are monitoring for stability.
Confirmed on the vendor status page
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
Supabase is responding normally. Our last automated check of supabase.com completed 5 minutes ago and succeeded in 284 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, 100.00% over 7 days, 100.00% over 30 days. We recorded 19 incidents in the last 30 days.
Supabase has averaged 301 ms across our successful checks in the past 24 hours, which is normal for a service of this kind. 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
