WhatBrokeToday
GTA 6FAQ
Is Supabase down right now?

Supabase outage history

Supabase had 63 incidents in the last 12 months, fixed in 1 min on median.

Incidents, 12 months
63
4 critical or high
Median time to fix
1 min
63 resolved
Longest
26 h
Never on the status page
0
posted after 1 min (median)

Supabase incidents per month

View as table
Supabase incidents per month
MonthIncidents
2026-1114
2026-1017
2026-0919
2026-0813
2026-070
2026-060
2026-050
2026-040
2026-030
2026-020
2026-010
2025-120
2025-110

Every Supabase incident in the last 12 months

Every Supabase incident in the last 12 months, newest first
DateIncidentSeverityTime to fixStatus page
Supabase: Edge Function Issues in ap-northeast-1medium3 hfirst
Supabase: ‘Project not specified’ errors reported for users in ap-northeast-2medium19 minfirst
Supabase: Projects in sa-east-1 experiencing delayed event ingestion

Cause: EC2 scheduled events are timing out for projects in sa-east-1.

minor9 hfirst
Supabase: Elevated Error rates for All Supabase project APIsmedium1 hfirst
Supabase: Database Connection Errors in sa-east-1 and ap-southeast-1medium3 hfirst
Supabase: Storage request degradation in eu-west-1medium8 minfirst
Supabase: Project Lifecycle Issues in ap-northeast-1medium5 hfirst
Supabase: Interruption in connections to Supavisor in eu-west-2minor26 hfirst
Supabase: Increased Errors with Project Lifecycle Operations in US-West-2

Cause: An upstream provider incident affecting EC2 instances in the US-West-2 region.

medium3 hfirst
Supabase: Intermittent 502/503 errors for pg_net calls to Edge Functionsmedium1 minfirst
Supabase: Storage issues in us-east-1 and eu-central-1medium1 minfirst
Supabase: Intermittent errors on Supavisor Shared Pooler in us-east-2medium1 minfirst
Supabase: Management API Postgres config updates overwriting previous updatesminor1 minfirst
Supabase: Storage uploads failing in us-east-1medium1 minfirst
Supabase: PG15 -> PG17 Upgrade Failuresminor1 minfirst
Supabase: Logs degraded in multiple regionsminor1 minfirst
Supabase: Delayed Log Delivery from 14:10 - 15:30 UTCmedium1 minfirst
Supabase: Elevated Mgmt API Error Rates in Multiple Regionsmedium1 minfirst
Supabase: Log Drain Issuesmedium1 minfirst
Supabase: Project lifecycle operation errors in the EU regionhigh1 minfirst
Supabase: Elevated Mgmt API Error Rates in Multiple Regionshigh1 minfirst
Supabase: Project lifecycle operations such as project creation, pausing, and restoration, in all regionshigh1 minfirst
Supabase: Projects stuck in restarting state

Cause: A bug in the project restarting process caused all affected projects to be stuck in a restarting state.

minor1 minfirst
Supabase: Support Form Errorsmedium1 minfirst
Supabase: Project creation errors ap-ne1medium1 minfirst
Supabase: Realtime latencymedium1 minfirst
Supabase: Edge Function Degradationmedium1 minfirst
Supabase: Log ingestion impairedmedium1 minfirst
Supabase: Intermittent connection errors via the connection pooler in us-east-1minor1 minfirst
Supabase: Upgrade Issuesminor1 minfirst
Supabase: Increased errors on management api leading to project operation failuresmedium1 minfirst
Supabase: 401 errors due to JWT rejectionsminor1 minfirst
Supabase: Log Ingestion Degradationminor1 minfirst
Supabase: Project Lifecycle Issues in eu-west-1minor1 minfirst
Supabase: Permission errors in the Supabase Dashboardminor1 minfirst
Supabase: Storage search failing for restored projectsminor1 minfirst
Supabase CLI CI workflow failuresminor1 minfirst
Supabase: Increased error rate in project creation and project restoreminor1 minfirst
Supabase: Supavisor connection disruptions in EU West 1 (Ireland)minor1 minfirst
Supabase: Project creations are degraded in multiple regionsminor1 minfirst
Supabase: Project Lifecycle Activity Degradationminor1 minfirst
Supabase: Myanmar Network Connectivityminor1 minfirst
Supabase: Query slowness for projects running Postgres version 14 in us-east-1 and ap-northeast-2minor1 minfirst
Supabase: Edge Function Latencyminor1 minfirst
Supabase: Auth Service Outageminor1 minfirst
Supabase: Unresponsive Projectsminor1 minfirst
Supabase: Latency issues resulting in 504 errorsminor1 minfirst
Supabase: Brief connection disruptions in us-east-1 (N. Virginia)

Cause: Unexpected restart of Supabase instances

minor1 minfirst
Supabase: Project Lifecycle Actions Showing increased error rates across all regionsminor1 minfirst
Supabase: User unable to log in to Supabase Dashboardminor1 minfirst
Supabase: Project Creation Failuresminor1 minfirst
Supabase: Increased response times for requestsminor1 minfirst
Supabase: Projects failing to load Supautils in multiple regions

Cause: GLIBC_2.33 is unavailable on affected hosts

minor1 minfirst
Supabase: pgBouncer issues on some older projectsminor1 minfirst
Supabase: Increased rates of Pooler connection timeouts in us-east-1medium1 minfirst
Supabase: Issues affecting automatic disk resizingmedium1 minfirst
Supabase: Error spikes in one of the ap-northeast-2 Supavisor clustersmedium1 minfirst
Supabase: Error spikes in one of the eu-east-1 Supavisor clusters

Cause: ClientHandler experienced ECHECKOUTTIMEOUT errors, being unable to check out connections from the pool after 15000ms in Transaction mode.

medium1 minfirst
Supabase: Delays in project provisioningmedium1 minfirst
Supabase: Sign-in failures for `signInWithIdToken` (OIDC) logins on free-tier projectsmedium1 minfirst
Supabase: Project creation failing in selected regionsmedium1 minfirst
Supabase: Project access, updating and creation impacted in us-east-2high1 minfirst
Supabase: MCP connection error to branch environmentsmedium1 minfirst

Compare Supabase's reliability

Questions

How often does Supabase go down?
Supabase had 63 incidents in the last 12 months, fixed in 1 min on median.
How long do Supabase outages last?
Half of Supabase's resolved incidents in the last 12 months were fixed within 1 min; the longest took 26 h.
Does Supabase report every outage on its status page?
Every Supabase incident tracked in the last 12 months also appeared on its status page.