401 errors due to JWT rejections

Summary

401 errors due to JWT rejections

We are continuing to test and rollout the fixes for intermittent HTTP 401 errors. In most cases, waiting and refreshing is successful. We will monitor eu-central-2 over the weekend and are preparing for the fix to be pushed to all regions starting Monday. Thank you for your patience while we've worked on multiple fixes for this issue.

• Started

  Aug 14, 2026 · 2:23 AM

• Status

  Identified

• Duration

  Ongoing

• Severity

  Minor

• ◆

  Identified

  Aug 14 · 2:23 AM Supabase

  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

  Aug 14 · 7:53 AM Supabase

  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.

• ◆

  Identified

  Aug 18 · 6:38 PM Supabase

  Fixes for this issue are being sequentially rolled out. The impact of the issue is limited to a subset of new projects that can experience it upon some JWT renewals. We will update the status when all the fix rollouts have completed.

• ◆

  Identified

  Aug 20 · 4:37 PM Supabase

  As part of the incident remediation flow, we have separately identified "/lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found" error between 11:15 - 16:24 UTC today affecting PostgREST. This has been fixed and we can see the error rates have subsided.

• ◆

  Identified

  Aug 21 · 5:21 PM Supabase

  We are continuing to test and rollout the fixes for intermittent HTTP 401 errors. In most cases, waiting and refreshing is successful. We will monitor eu-central-2 over the weekend and are preparing for the fix to be pushed to all regions starting Monday. Thank you for your patience while we've worked on multiple fixes for this issue.