Live / Supabase / Incident
Supabase: 401 errors due to JWT rejections
Supabase · supabase.comMinor incidentResolved2026-09-29 18:46 UTC
Public — what happened
Summary
Supabase reported a minor incident in which some requests were failing with 401 errors because JWTs were being rejected, beginning on 2026-08-14 at 02:23 UTC. The company did not say how many users were affected or explain what caused the rejections. Supabase said a new version had been released and that affected users could fix the problem by upgrading through the dashboard. It marked the incident resolved on 2026-09-29 at 18:46.
Timeline
- Started — 2026-08-14 02:23 UTC
- Resolved — 2026-09-29 18:46 UTC · 47 days after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Supabase against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Supabase: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Supabase report →
More from Supabase