← Supabase status
INCIDENT IN PROGRESS
Supabase
✓401 errors due to JWT rejections
Updated
Confirmed disruption
09:49Started
1Timeline events
Confirmed by the official source.
Executive summary
-
Summary
Supabase has confirmed a disruption involving intermittent HTTP 401 errors caused by JWT rejections. The issue affects a subset of new projects during some JWT renewals, and the latest update reported positive testing with an expanded rollout planned.
What users experienced
- User impact
Affected sessions may receive intermittent HTTP 401 errors when newly refreshed JWTs are rejected by the API.
◷
Started
09:497 Sep 2026Timeline of the incident
-
Detection
Confirmed by an official service source.
What we know
- ✓The affected component is the API Gateway.
- ✓Supabase described the impact as limited to a subset of new projects experiencing errors during some JWT renewals.
- ✓Supabase reported that fixes were being rolled out sequentially and later planned to expand the rollout after positive testing.
- ✓The latest evidence does not indicate that the incident has been resolved.