Supabase Status

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: We've identified the issue affecting project creation and are implementing a fix. Users may experience delays when creating new projects while we work to resolve this.

Investigating: We are currently investigating this issue

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: We've identified the issue affecting project creation and are implementing a fix. Users may experience delays when creating new projects while we work to resolve this.

Investigating: We are currently investigating this issue

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: We've identified the issue affecting project creation and are implementing a fix. Users may experience delays when creating new projects while we work to resolve this.

Investigating: We are currently investigating this issue

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: We've identified the issue affecting project creation and are implementing a fix. Users may experience delays when creating new projects while we work to resolve this.

Investigating: We are currently investigating this issue

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: We've identified the issue affecting project creation and are implementing a fix. Users may experience delays when creating new projects while we work to resolve this.

Investigating: We are currently investigating this issue

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: We've identified the issue affecting project creation and are implementing a fix. Users may experience delays when creating new projects while we work to resolve this.

Investigating: We are currently investigating this issue

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: We've identified the issue affecting project creation and are implementing a fix. Users may experience delays when creating new projects while we work to resolve this.

Investigating: We are currently investigating this issue

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: We've identified the issue affecting project creation and are implementing a fix. Users may experience delays when creating new projects while we work to resolve this.

Investigating: We are currently investigating this issue

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: We've identified the issue affecting project creation and are implementing a fix. Users may experience delays when creating new projects while we work to resolve this.

Investigating: We are currently investigating this issue

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: We've identified the issue affecting project creation and are implementing a fix. Users may experience delays when creating new projects while we work to resolve this.

Investigating: We are currently investigating this issue

Resolved: This incident has been resolved.

Monitoring: We are continuing to monitor to ensure ongoing stability.

Identified: The remaining projects have now been brought back up, and we have no projects remaining on the unhealthy underlying hardware in the upstream infrastructure. We are monitoring to ensure ongoing stability.

Identified: Most projects have been brought back up, and the team is working on the remaining projects, which should be completed soon.

This issue was related to specific underlying hardware in the region, so this was isolated to only projects on that hardware. Project lifecycle operations (restarts, upgrades, etc) broadly across the region remain available.

Identified: All projects affected by the upstream infrastructure issues, and mitigation efforts are underway internally. These affected projects will be brought back up on new hardware as quickly as possible.

Identified: We have isolated the scope of the problem to a specific upstream incident. We are working to address the upstream incident and determine mitigations.

Investigating: We are investigating project lifecycle operation issues in eu-west-1.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: We've identified the issue affecting project creation and are implementing a fix. Users may experience delays when creating new projects while we work to resolve this.

Investigating: We are currently investigating this issue

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: We've identified the issue affecting project creation and are implementing a fix. Users may experience delays when creating new projects while we work to resolve this.

Investigating: We are currently investigating this issue

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: We've identified the issue affecting project creation and are implementing a fix. Users may experience delays when creating new projects while we work to resolve this.

Investigating: We are currently investigating this issue

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: We've identified the issue affecting project creation and are implementing a fix. Users may experience delays when creating new projects while we work to resolve this.

Investigating: We are currently investigating this issue

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: We've identified the issue affecting project creation and are implementing a fix. Users may experience delays when creating new projects while we work to resolve this.

Investigating: We are currently investigating this issue

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: We've identified the issue affecting project creation and are implementing a fix. Users may experience delays when creating new projects while we work to resolve this.

Investigating: We are currently investigating this issue

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: We've identified the issue affecting project creation and are implementing a fix. Users may experience delays when creating new projects while we work to resolve this.

Investigating: We are currently investigating this issue

Identified: The deployment process changes have been rolled out across all regions. We will monitor throughout the weekend.

The new Supabase version will be released early next week. Once it is released, impacted users can upgrade to from their dashboard to resolve this issue.

Thank you again for your patience while we worked through this. We will provide an update once the new version is available and users can upgrade.

Identified: We have rolled out the deployment process changes to eu-central-2 and continue to monitor. We will provide additional updates as we make this change to other regions.

Once this change is implemented across all regions, we will release a new Supabase version that impacted users can upgrade to from their dashboard. Completing that upgrade will resolve this issue.

Identified: To resolve this issue, our fleet requires a change to our deploy process. We have spent this week making these changes and will be implementing them throughout this weekend, starting on Friday, September 18. Once this change is implemented, we will release a new Supabase version that impacted users can upgrade to from their dashboard. Completing that upgrade will resolve this issue.

We recognize that this is added work for our customers. This issue has been open for over a month, as we tried to make this change on each project's behalf. In an effort to resolve this sooner, we have opted to make this deployment process change and ask users to upgrade.

Identified: We continue to monitor progress and are slowly updating each region. Thank you for your patience on this issue.

Identified: Testing results have been positive. Following some additional checks today, we plan to expand the rollout. We’ll continue to monitor progress and provide further updates as they become available.

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: This incident has been resolved. Following the restart of the affected Supavisor node, error rates returned to normal and no further disruptions have been observed during the monitoring period. All services are operating normally.

Monitoring: The affected Supavisor node has been restarted, and error rates have returned to normal levels. We’ll continue to monitor the service to ensure stability.

Investigating: Some projects in the EU West 1 (Ireland) region may experience disruptions to Supavisor connections. Our team is aware of the issue and actively working on a resolution. We’ll share further updates as they become available.

Resolved: This incident has been resolved. Administrative operations in the Supabase Dashboard are completing as expected, and we have observed no further permission related errors following the fix.

Monitoring: We have applied a fix, and administrative operations in the Supabase Dashboard are now completing as expected. We are monitoring the results to ensure the issue is fully resolved.

Identified: We have identified the issue causing some users to encounter permission-related errors, such as “You need additional permissions,” when performing administrative actions in the Supabase Dashboard. We are working on a fix and will provide another update once it has been implemented.

Investigating: We are investigating reports of users encountering permission-related errors, such as “You need additional permissions,” when performing administrative actions in the Supabase Dashboard. This may prevent some users from managing their projects through the Dashboard. We are working to identify the cause and will provide further updates as they become available.

Resolved: Project lifecycle operations are behaving normally.

Monitoring: Project lifecycle operations have remained stable. We will continue to monitor the platform.

Investigating: We are observing recovery in project lifecycle operations. Our team is investigating the root cause and actively working to prevent recurrence.

Investigating: We are experiencing degradation of project lifecycle activities. We are investigating.

Resolved: This incident has been resolved.

Monitoring: We are continuing to monitor to ensure ongoing stability.

Identified: The remaining projects have now been brought back up, and we have no projects remaining on the unhealthy underlying hardware in the upstream infrastructure. We are monitoring to ensure ongoing stability.

Identified: Most projects have been brought back up, and the team is working on the remaining projects, which should be completed soon.

This issue was related to specific underlying hardware in the region, so this was isolated to only projects on that hardware. Project lifecycle operations (restarts, upgrades, etc) broadly across the region remain available.

Identified: All projects affected by the upstream infrastructure issues, and mitigation efforts are underway internally. These affected projects will be brought back up on new hardware as quickly as possible.

Identified: We have isolated the scope of the problem to a specific upstream incident. We are working to address the upstream incident and determine mitigations.

Investigating: We are investigating project lifecycle operation issues in eu-west-1.

Resolved: Project lifecycle operations are behaving normally.

Monitoring: Project lifecycle operations have remained stable. We will continue to monitor the platform.

Investigating: We are observing recovery in project lifecycle operations. Our team is investigating the root cause and actively working to prevent recurrence.

Investigating: We are experiencing degradation of project lifecycle activities. We are investigating.

Resolved: This incident has been resolved.

Monitoring: We are continuing to monitor to ensure ongoing stability.

Identified: The remaining projects have now been brought back up, and we have no projects remaining on the unhealthy underlying hardware in the upstream infrastructure. We are monitoring to ensure ongoing stability.

Identified: Most projects have been brought back up, and the team is working on the remaining projects, which should be completed soon.

This issue was related to specific underlying hardware in the region, so this was isolated to only projects on that hardware. Project lifecycle operations (restarts, upgrades, etc) broadly across the region remain available.

Identified: All projects affected by the upstream infrastructure issues, and mitigation efforts are underway internally. These affected projects will be brought back up on new hardware as quickly as possible.

Identified: We have isolated the scope of the problem to a specific upstream incident. We are working to address the upstream incident and determine mitigations.

Investigating: We are investigating project lifecycle operation issues in eu-west-1.

Resolved: Storage is now operating normally. We apologise for the disruption.

Hardening measures are being put in place to prevent recurrence and will be communicated upon completion.

Monitoring: A fix has been implemented for the affected tenants and we are monitoring the results. We will continue to monitor the situation and will provide further updates as more information becomes available.

Investigating: We have identified an issue with Storage for projects are restoring from backups. Users may experience increased 500 errors.

We are working to identify the root cause and will notify for any progress as soon as we have an update