Supabase
Database
Resolving…
401 errors due to JWT rejections
IdentifiedAs 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.
Location:
—
Started:
2026-08-14 02:23 UTC
(6d ago)
Updated:
2026-08-20 16:37 UTC
(49m ago)
Resolved:
N/A
2026-08-18 18:38 UTC
(1d ago)
:
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.
2026-08-14 07:53 UTC
(6d ago)
:
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.
2026-08-14 02:23 UTC
(6d ago)
:
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.
Network access issues affecting a limited number of users in Myanmar
IdentifiedWe have reached out to the ISPs that have been involved in the connectivity challenges for users in Myanmar. We are continuing to work to address the issue.
Location:
—
Started:
2026-08-19 15:52 UTC
(1d ago)
Updated:
2026-08-20 12:18 UTC
(5h ago)
Resolved:
N/A
2026-08-19 17:08 UTC
(1d ago)
:
The connectivity issues appear to be limited to a subset of ISPs in Myanmar. Impacted users could try alternative ISPs to restore connectivity while we work to address this issue.
2026-08-19 15:52 UTC
(1d ago)
:
We are investigating reports that a limited number of users in Myanmar are unable to access Supabase. We will provide additional updates as information becomes available.