Skip to content

Supabase status

Checked

Review Supabase platform status across core backend services and recent incidents.

Degraded 3 tracked services 87 incidents on record

Partially Degraded Service

Supabase reports partially degraded service. No mapped tracked service currently shows direct impact.

Get alerted when Supabase goes down

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Supabase uptime history

Daily Supabase uptime measured by OutageDeck's own independent checks of the official status source, rolled up per UTC day. Days without monitoring data stay empty rather than counting as uptime.

100%free of major outages · last 90 days

Last 30 days: 100%. No full-platform outages observed. Partial or regional impact totaled 4h 28m across 59 monitored days, usually a single region or service rather than the whole platform.

Tracking since Jul 5, 2026

30 days agoToday
  • Operational
  • Degraded
  • Partial outage
  • Major outage
  • Maintenance
  • No data

Long-open incidents are skewing this window

  • 401 errors due to JWT rejections has been open on Supabase's own status page since , 21 days now. Time under an open incident shows in the strip above as whatever status Supabase reported; an entry this old usually means the vendor never closed it, not a 21-day outage.
  • Network access issues affecting a limited number of users in Myanmar has been open on Supabase's own status page since , 16 days now. Time under an open incident shows in the strip above as whatever status Supabase reported; an entry this old usually means the vendor never closed it, not a 16-day outage.

Put Supabase status in your README

Choose OutageDeck's native SVG or the official Shields.io route. Both show the current Supabase status and link back to this live page.

Supabase native status badgeSupabase Shields.io status badge

The native badge is served directly by OutageDeck with no account or rate limit. The Shields.io badge fits the same customization options as the other badges in your README.

Watching more than one vendor? Build a multi-provider status wall.

Markdown

[![Supabase status](https://outagedeck.com/api/v1/badges/supabase)](https://outagedeck.com/providers/supabase)

Shields.io Markdown

[![Supabase status](https://img.shields.io/outagedeck/status/supabase)](https://outagedeck.com/providers/supabase?utm_source=shields&utm_medium=badge&utm_campaign=shields_provider_status)

HTML

<a href="https://outagedeck.com/providers/supabase"><img src="https://outagedeck.com/api/v1/badges/supabase" alt="Supabase status" /></a>

Service status for Supabase

Service cards show which parts of the provider are healthy, degraded, or under maintenance. Each carries its own uptime history, so a single-service event reads as that service's record rather than the whole platform's.

Active incidents affecting Supabase

Current and recent incidents stay linked to the affected services and official status source.

Weekly recap of outages like these

One short email every Monday covering the week's incidents across every tracked provider, Supabase included. Unsubscribe anytime.

What users ask about Supabase

The quick answers, written from Supabase's current official status rather than a generic template.

Is Supabase down right now?
As of the latest check, Supabase is reporting degraded performance with 2 active incidents. The incident activity on this page tracks the scope, affected services, and the latest official updates.
Where does the Supabase status data come from?
The Supabase page links to the official status source at https://status.supabase.com, and OutageDeck records source provenance alongside the rendered incident history.
What does OutageDeck track for Supabase?
Supabase pages include the current overall platform status, tracked service-level summaries, recent incidents, and links to deeper incident timelines when they exist.