UptimeProject

Supabase

Operational

Supabase · Cloud / IaaS

Updated

24h availability

100.00%

0 min down

7d availability

100.00%

0 min down

30d availability

100.00%

0 min down

90d availability

100.00%

0 min down

Period:
Avg response time 54ms
0% 50% 100% 2026-10-23 00:00 UTC Status: up Availability: 100.00% p50 latency: 48ms 2026-10-24 00:00 UTC Status: up Availability: 100.00% p50 latency: 53ms 2026-10-25 00:00 UTC Status: up Availability: 100.00% p50 latency: 54ms 2026-10-26 00:00 UTC Status: up Availability: 100.00% p50 latency: 56ms 2026-10-27 00:00 UTC Status: up Availability: 100.00% p50 latency: 55ms 2026-10-28 00:00 UTC Status: up Availability: 100.00% p50 latency: 55ms 2026-10-29 00:00 UTC Status: up Availability: 100.00% p50 latency: 55ms 2026-10-30 00:00 UTC Status: up Availability: 100.00% p50 latency: 54ms 2026-10-31 00:00 UTC Status: up Availability: 100.00% p50 latency: 53ms 2026-11-01 00:00 UTC Status: up Availability: 100.00% p50 latency: 52ms 2026-11-02 00:00 UTC Status: up Availability: 100.00% p50 latency: 54ms 2026-11-03 00:00 UTC Status: up Availability: 100.00% p50 latency: 54ms 2026-11-04 00:00 UTC Status: up Availability: 100.00% p50 latency: 54ms 2026-11-05 00:00 UTC Status: up Availability: 100.00% p50 latency: 55ms 2026-11-06 00:00 UTC Status: up Availability: 100.00% p50 latency: 52ms 61ms 43ms 23 Oct 06 Nov 90d availability · latency (p50)

90d: 0 min down, 0 min degraded, 2 min unmeasured

Recent incidents

All incidents Atom feed

No incidents recorded in the lookback window.

Vantage points

Falkenstein, DE Hetzner
70ms Operational
Roubaix, FR OVH
80ms Operational
New York, US DigitalOcean
36ms Operational
Seattle, US Vultr
59ms Operational
Singapore Vultr
80ms Operational

What we monitor

2 active checks

Each row below is one probe-side measurement we run from every vantage point. The availability number on this page is the consensus across these checks, not a single endpoint hit.

  • HTTP https://api.supabase.com/v1/projects every minute
  • TLS api.supabase.com:443 every hour

About this data

Availability is measured independently by probes in five locations. Each probe runs the appropriate mix of HTTP, DNS, TLS, and storage checks at per-check cadences and records timing, status code, and any error. A probe votes "up" for a given minute if any of its checks for this service succeeded; the minute is then counted as "up" on the leaderboard only when a strict majority of reporting probes voted up. Minutes where fewer than three probes reported are excluded from the denominator. Full methodology

Embed a badge

Markdown for a README. The image is served by the public API and links back to this page.

          [![Supabase uptime](https://api.uptimeproject.org/v1/services/supabase/badge.svg)](https://uptimeproject.org/service/supabase/)
        
Back to Cloud / IaaS leaderboard