Provider
SupabaseIncident detail
401 errors due to JWT rejections
Active incidentMinor
Timeline window
Started
Outage alerts
Get alerted the next time Supabase breaks
Free email alerts for up to 5 providers. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update Supabase posted, oldest to newest, exactly as it appeared on their official status page.
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.
Identified
Our teams are continuing to work on the fix and rollout is underway for selected customers. We will provide another update as we are applying the fix to all impacted users.
Keep exploring
More from Supabase
Neighboring incidents on Supabase's timeline and the rest of their record on OutageDeck.