Supabase: 401 errors due to JWT rejections

Supabase · supabase.comImpact: minorResolved2026-09-29 18:46 UTC

Public — what happened

Summary

The latest Supabase version has been released. All users impacted by this issue can now upgrade from the dashboard to resolve this issue. Since this new version is released, we will resolve this issue. If you have any questions about upgrading, please refer to our documentation for more information: https://supabase.com/docs/guides/platform/upgrading Thank you again for your patience while we worked on resolving this issue.

Timeline

Started — 2026-08-14 02:23 UTC
Last update — 2026-09-29 18:46 UTC
Resolved — 2026-09-29 18:46 UTC

Source of record: provider status page. Mirrored as reported; times in UTC.

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 see

Customers 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 →

Related: Supabase status & history. SquidGrid is not affiliated with Supabase.