Supabase Status

Identified: A stale time cache has been identified as the cause of this issue. A targeted fix has been written and is undergoing internal testing. It will be rolled out when testing is complete. Thank you for your patience while we investigated this issue. We will update the status page when the fix is rolled out.

Identified: We have seen reports that the JWT rejection issue persisted with 14.17, and due to some unintended performance side effects, we have rolled back to Postgrest 14.5. The team continues to investigate the JWT issue and hopes to have a solution soon.

Identified: We continue to monitor the fixes introduced by this latest rollout. If you are continuing to see these errors, some customers have reported that restarting their project after the rollout resolved this issue.

To restart your project, go to the General settings page in the dashboard and select Restart project.

Please contact our support team if the issue persists after a restart.

Identified: PostgREST 14.17 has now been rolled out to all regions. Some customers have reported that restarting their project after the rollout resolved this issue. To restart your project, go to the General settings page in the dashboard and select Restart project. Please contact our support team if the issue persists after a restart.

Identified: We are continuing to rollout the fixes for intermittent HTTP 401 errors. In most cases, waiting and refreshing is successful.

This fix has been applied to the following regions: ap-east-1 ap-northeast-1 ap-northeast-2 ap-south-1 ap-southeast-1 ap-southeast-2 ca-central-1 eu-central-1 eu-central-2 eu-north-1 eu-west-2 eu-west-3

We will continue rolling out this fix to the remaining regions throughout this week and provide updates as more regions are successful.

Identified: 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.

Identified: 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: 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: 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: 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.

Resolved: Lifecycle operations have been re-enabled for 100% of users and error rates have returned to normal.

Monitoring: Lifecycle operations have been re-enabled for 100% of users and error rates have returned to normal.

We are going to monitor to ensure that things stay stable. The team is working through any remaining projects which did not automatically resolve.

Some users may also notice that backups will happen a bit later than usual, but these jobs are running and completing normally.

Identified: We've increased project lifecycle operations to 50% of users and things are holding steady. We're continuing to ramp this up until operations are restored for all users.

This is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc.

Running projects remain running, and the data APIs and direct postgres client connections are NOT affected.

Identified: Error rates have returned to normal, and the backlogs are draining well. We are beginning to slowly re-enable lifecycle operations for users.

We will be monitoring impact, and we hope to have this re-enabled everywhere soon. We will leave this in this state until lifecycle operations have been completely restored.

Running projects remain running, and the data APIs and direct postgres client connections are NOT affected.

Identified: We are seeing incremental improvements internally. There is a large backlog of actions that we are working through, but things are progressing. Once we make it through most of the backlog, we will re-enable lifecycle actions.

This is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc.

Running projects remain running, and the data APIs and direct postgres client connections are NOT affected.

Identified: The team is continuing to work on restoring project lifecycle operations. Out of caution, we have disabled lifecycle operations.

This is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc.

Running projects remain running, and the data APIs and direct postgres client connections are NOT affected.

We will provide additional updates as we have more information.

Identified: The team has applied a fix, but error rates remain high. We are continuing to work and will take other necessary steps to resolve this as soon as possible.

Running projects remain running, and the data APIs and direct postgres client connections are NOT affected.

Out of an abundance of caution, we would suggest against taking any of these actions until this incident is resolved: Creates, Configuration changes, Restarts, or Compute size changes. We will provide additional updates as we have more information.

Identified: We have identified the source of the errors with project lifecycle actions, and the team is currently working to resolve it.

This is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc.

Running projects remain running, and the data APIs and direct postgres client connections are NOT affected.

Out of an abundance of caution, we would suggest against taking any of these actions until this incident is resolved. We will provide additional updates as we have more information.

Investigating: We are seeing increased error rates in actions across all project lifecycle actions - Creations, Deletions, Restores, Configuration and Compute size upgrades. We are currently looking into the cause.

Out of an abundance of caution, we would suggest against taking any of these actions until this incident is resolved. We will provide additional updates as we have more information

Resolved: This incident has been resolved. Users should now be able to log in to the Supabase Dashboard normally. Projects and non-Dashboard traffic were unaffected throughout the incident.

Monitoring: A recent change affected users ability to log in to the Supabase Dashboard. We’ve reverted the change, and testing indicates that the issue is resolved. Please try logging in again. If you’re still unable to log in, perform a full browser refresh and retry. Projects and non-Dashboard traffic remained unaffected.

Investigating: We’re investigating an issue preventing users from logging in to the Supabase Dashboard. Users who were logged into the dashboard were logged out. Dashboard actions are currently not available.

Projects remain online and available. Non-Dashboard traffic is not impacted. We’ll share another update as soon as we have more information.

Investigating: We are currently investigating an issue where users are unable to login to the Supabase dashboard

Resolved: Project creation has returned to baseline consistently.

Monitoring: Project creation is reporting as recovered across the platform. We will monitor for stability in the near term.

Identified: We are seeing the mitigation steps having the desired effect. Project creation is recovering.

Investigating: While the first set of actions are taking effect, we are implementing a second set of likely mitigations to attempt to facilitate improvement in project creation.

Investigating: We continue to work this issue. The steps we have taken are addressing the hypothesized cause of the issue. We are implementing further related mitigations.

Investigating: We have a working hypothesis on the cause of the issue, and are implementing steps to try to improve project creation performance.

Investigating: Project creation is failing for new projects on the platform. We are investigating.