Live  /  Providers  /  Supabase

Supabase

supabase.comReporting incidents

Independent assessment — SquidGrid is not affiliated with Supabase. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

Cloud & hosting · SquidGrid tracks Supabase’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what Supabase is reporting

Current & recent incidents

identified

401 errors due to JWT rejections

Minor impact · 2026-09-25 16:23 UTC · still open per the provider’s page — may be stale

Resolved

Log Ingestion Degradation

Minor impact · 2026-09-28 14:36 UTC

Resolved

Project Lifecycle Issues in eu-west-1

Major impact · 2026-09-24 17:38 UTC

Resolved

Permission errors in the Supabase Dashboard

Critical impact · 2026-09-24 11:49 UTC

Resolved

Storage search failing for restored projects

Minor impact · 2026-09-24 10:01 UTC

Resolved

Supabase CLI CI workflow failures

Minor impact · 2026-09-23 23:41 UTC

Resolved

Increased error rate in project creation and project restore

Major impact · 2026-09-23 10:49 UTC

Resolved

Supavisor connection disruptions in EU West 1 (Ireland)

Minor impact · 2026-09-22 12:20 UTC

Mirrored from the provider’s own published status. Times in UTC.

Independent path health

A status page tells you what Supabase has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

Supabase runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of Supabase is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with Supabase.