Supabase

Operational Infrastructure

Postgres + pgvector + auth — the default AI-app backend stack.

All Systems Operational · 5d ago

30-day uptime 97.39% approx.

Response time · 24h

Measured by Prismix probes — not the vendor's status feed.

217ms

p50

min
74ms
p50
217ms
p95
370ms
p99
370ms

Embed this live badge

Updates ~30s · append ?theme=dark for dark READMEs

Light

Supabase — light theme badge

Dark

Supabase — dark theme badge
Copy snippet ↓

Markdown · light

[![Supabase status](https://prismix.dev/api/badge/supabase.svg)](https://prismix.dev/service/supabase)

Markdown · dark

[![Supabase status](https://prismix.dev/api/badge/supabase.svg?theme=dark)](https://prismix.dev/service/supabase)

HTML

<a href="https://prismix.dev/service/supabase"><img src="https://prismix.dev/api/badge/supabase.svg" alt="Supabase status"></a>

Components (1)

  • ap-east-1 Operational

Resolved (last 30 days)

Full incident history →
  • Minor

    Edge Function Issues in ap-northeast-1

    Resolved 20h ago · lasted 3h 7m

  • Informational

    Projects in sa-east-1 experiencing delayed event ingestion

    Resolved 1d ago · lasted 8h 43m

  • Minor

    ‘Project not specified’ errors reported for users in ap-northeast-2

    Resolved 1d ago · lasted 3h 11m

  • Minor

    Database Connection Errors

    Resolved 5d ago · lasted 3h 4m

  • Minor

    Elevated Error rates for All Supabase project APIs

    Resolved 5d ago · lasted 1h 17m

  • Minor

    Storage request degradation in eu-west-1

    Resolved 6d ago · lasted 7m

  • Minor

    Project Lifecycle Issues in ap-northeast-1

    Resolved 6d ago · lasted 4h 48m

  • Informational

    Interruption in connections to Supavisor in eu-west-2

    Resolved 10d ago · lasted 1h 41m

  • Minor

    Increased Errors with Project Lifecycle Operations in US-West-2

    Resolved 11d ago · lasted 2h 27m

  • Minor

    Intermittent 502/503 errors for pg_net calls to Edge Functions

    Resolved 12d ago · lasted 42m

  • Minor

    Storage issues in us-east-1 and eu-central-1

    Resolved 13d ago · lasted 16h 18m

  • Minor

    Intermittent errors on Supavisor Shared Pooler in us-east-2

    Resolved 14d ago · lasted 28m

  • Informational

    Management API Postgres config updates overwriting previous updates

    Resolved 15d ago · lasted 2h 8m

  • Minor

    Storage uploads failing in us-east-1

    Resolved 15d ago · lasted 1h 13m

  • Informational

    PG15 -> PG17 Upgrade Failures

    Resolved 17d ago · lasted 1h 8m

  • Informational

    Logs degraded in multiple regions

    Resolved 19d ago · lasted 51m

  • Minor

    Delayed Log Delivery from 14:10 - 15:30 UTC

    Resolved 21d ago · lasted 52m

  • Minor

    Elevated Mgmt API Error Rates in Multiple Regions

    Resolved 23d ago · lasted 89h 15m

  • Minor

    Log Drain Issues

    Resolved 27d ago · lasted 46m

  • Major

    Project lifecycle operation errors in the EU region

    Resolved 27d ago · lasted 12h 3m

Common questions about Supabase

Is Supabase down right now?

Supabase is currently reporting operational. We last checked under 5 minutes ago.

Where does this status data come from?

Directly from Supabase's official Statuspage.io feed at https://status.supabase.com. We refresh every 5 minutes and persist 24 hours of probe history.

Can I get email or webhook alerts when Supabase breaks?

Yes — sign in, star Supabase on the status dashboard, then add an email or Discord/Slack webhook on /alerts. Free tier gets 1 destination per channel; Pro gets 5.

What does "Operational" mean?

All systems operating normally. No active incidents reported.

Guides for Supabase

Related infrastructures

Get notified when Supabase changes state

One-click email alerts for Supabase only. No account. No Pro tier. Unsubscribe in every email.

Want to subscribe to multiple services + control severity threshold + add quiet hours? Create a free account instead.

Last refreshed 33m ago · cached · data from https://status.supabase.com