Supabase

Degraded Infrastructure

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

Partially Degraded Service · 25m ago

30-day uptime 93.97% approx.

Response time · 24h

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

367ms

p50

min
202ms
p50
367ms
p95
871ms
p99
1029ms

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>

Active incidents

Network access issues affecting a limited number of users in Myanmar

Started 8h ago · current status: Investigating

Informational
  1. Investigating 8h ago

    We are investigating reports that a limited number of users in Myanmar are unable to access Supabase. We will provide additional updates as information becomes available.

  2. Investigating 7h ago

    The connectivity issues appear to be limited to a subset of ISPs in Myanmar. Impacted users could try alternative ISPs to restore connectivity while we work to address this issue.

Upstream incident ↗

401 errors due to JWT rejections

Started 5d ago · current status: Identified

Minor
  1. Identified 5d ago

    We have identified the root cause of newly refreshed JWTs being rejected by the API, resulting in HTTP 401 errors for affected sessions. We are working on a fix and will provide updates as things progress.

  2. Identified 5d ago

    Our teams are continuing to work on the fix and rollout is underway for selected customers. We will provide another update as we are applying the fix to all impacted users.

  3. Identified 1d ago

    Fixes for this issue are being sequentially rolled out. The impact of the issue is limited to a subset of new projects that can experience it upon some JWT renewals. We will update the status when all the fix rollouts have completed.

Upstream incident ↗

Components (28)

  • Compute capacity Operational
  • Analytics Operational
  • ap-northeast-1 Operational
  • API Gateway Degraded
  • ap-northeast-2 Operational
  • Auth Operational
  • ap-south-1 Operational
  • Connection Pooler Operational
  • ap-southeast-1 Operational
  • Dashboard Operational
  • ap-southeast-2 Operational
  • Database Operational
  • ca-central-1 Operational
  • Edge Functions Operational
  • eu-central-1 Operational
  • Management API Operational
  • eu-central-2 Operational
  • Realtime Operational
  • eu-north-1 Operational
  • Storage Operational
  • eu-west-1 Operational
  • eu-west-2 Operational
  • eu-west-3 Operational
  • sa-east-1 Operational
  • us-east-1 Operational
  • us-east-2 Operational
  • us-west-1 Operational
  • us-west-2 Operational

Resolved (last 30 days)

Full incident history →
  • Minor

    Sign-in failures for `signInWithIdToken` (OIDC) logins on free-tier projects

    Resolved 8h ago · lasted 3h 9m

    Details ↗
  • Minor

    Project creation failing in selected regions

    Resolved 2d ago · lasted 8m

    Details ↗
  • Critical

    Project access, updating and creation impacted in us-east-2

    Resolved 5d ago · lasted 1h 13m

    Details ↗
  • Informational

    MCP connection error to branch environments

    Resolved 8d ago · lasted 3h 52m

    Details ↗
  • Minor

    Project Upgrade Delays

    Resolved 14d ago · lasted 50h 5m

    Details ↗
  • Minor

    Management API Performance Degradation

    Resolved 15d ago · lasted 97h 23m

    Details ↗
  • Minor

    DNS creation delays

    Resolved 19d ago · lasted 58m

    Details ↗
  • Major

    Issues with Edge Function Deployment

    Resolved 19d ago · lasted 19h 42m

    Details ↗
  • Minor

    Management API Performance Degradation

    Resolved 19d ago · lasted 5h 51m

    Details ↗
  • Minor

    Log Ingestion Issues

    Resolved 20d ago · lasted 52m

    Details ↗
  • Minor

    SSO login failures in us-east-1

    Resolved 22d ago · lasted 42m

    Details ↗
  • Minor

    Documents Search Unavailable

    Resolved 22d ago · lasted 6m

    Details ↗
  • Minor

    Delays in creation of DNS records

    Resolved 23d ago · lasted 2h 1m

    Details ↗
  • Major

    Project Resize Problems in US-West-2

    Resolved 23d ago · lasted 3h 4m

    Details ↗
  • Minor

    Authentication issues for some projects

    Resolved 25d ago · lasted 34m

    Details ↗
  • Informational

    Between 11:34 and 11:43 UTC, some projects in the us-east-2 (Ohio) region experienced degraded connectivity during a connection pooler maintenance upgrade

    Resolved 27d ago

    Details ↗
  • Minor

    Log Ingestion Problems

    Resolved 28d ago · lasted 3h 40m

    Details ↗

Common questions about Supabase

Is Supabase down right now?

Supabase has 2 active incidents as of 2026-08-20. The "Active incidents" section above lists details.

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 "Degraded" mean?

Some users may notice slowness or intermittent errors. Core functionality intact.

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 0s ago · live · data from https://status.supabase.com