Supabase incident
401 errors due to JWT rejections
Started
August 14, 2026 at 02:23 AM UTC
Ongoing for
4h 44m
Latest update
August 14, 2026 at 02:23 AM UTC
Updates timeline
- Identified
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.
Get an email when Supabase recovers
One email when this incident resolves — and one the next time Supabase breaks. No account needed, unsubscribe in every email.
Watching more than one service? A free account covers 5 services + a daily digest — and Pro is currently free.
Live Supabase status
Current indicator + 24h latency
All incidents
Cross-service timeline
Subscribe via RSS
Atom feed for any reader