Supabase

✓

401 errors due to JWT rejections

Updated 29 Sep 2026, 20:50 UTC

Resolved 09:49Started 2Timeline events

Confirmed by the official source.

Executive summary

Summary
Supabase has confirmed an ongoing API Gateway disruption involving intermittent HTTP 401 errors from JWT rejections. Fix rollout and regional monitoring are continuing.

What users experienced

User impact
A subset of new projects may experience intermittent HTTP 401 errors during some JWT renewals. Supabase reports that waiting and refreshing is successful in most cases.

◷

Started

09:497 Sep 2026

▧

Timeline events

Timeline of the incident

9 Sep 2026, 13:40 UTC
Detection
Confirmed by an official service source.
29 Sep 2026, 20:50 UTC
Resolution
The service is no longer reporting this incident as active.

What we know

✓The affected component is Supabase API Gateway, listed with degraded performance.
✓The reported impact is limited to a subset of new projects and some JWT renewals.
✓Supabase has been progressively rolling out fixes and is continuing to update regions.
✓Supabase reports that restarting a project resolved the issue for some customers after rollout.