minorArchivedSupabasevlatest version released

Supabase: 401 errors due to JWT rejections

Investigating(done)
Trending(skipped)
Workaround available(skipped)
Resolved(done)
Archived

Executive summary

Users are experiencing 401 Unauthorized errors in Supabase applications. This issue is resolved with the latest version release, which users can upgrade from the dashboard.

No verified workaround yet

This incident was resolved upstream without a reported workaround.

Official fix

Technical root cause

Under active investigation. No report has identified a root cause yet.

Evidence

1 report · 1 StatusShow

[1]
Status First report1 month ago
401 errors due to JWT rejections(opens official status page in a new tab)
Status: Resolved 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.
by supabase status

Timeline

First report on status pageSep 29, 18:46 UTC
401 errors due to JWT rejections
Source
Official statementSep 29, 18:46 UTC
Status: Resolved The latest Supabase version has been released.
Source
Status changedSep 29, 18:46 UTC
Status changed: new → archived (resolved more than 14 days ago).