FrameWork - Operational
FrameWork
FrameWork API - Operational
FrameWork API
FrameWork Auth - Operational
FrameWork Auth
Notice history
View current statusAug 2026
- Resolved · UTC
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/upgradingThank you again for your patience while we worked on resolving this issue.
- Update · UTC
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.
- Update · UTC
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.
- Update · UTC
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.
- Update · UTC
We continue to monitor progress and are slowly updating each region. Thank you for your patience on this issue.
- Update · UTC
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. - Update · UTC
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.
- Update · UTC
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.
- Update · UTC
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.
- Update · UTC
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. - Update · UTC
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-3We will continue rolling out this fix to the remaining regions throughout this week and provide updates as more regions are successful.
- Update · UTC
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.
- Update · UTC
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.
- Update · UTC
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.
- Update · UTC
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 · UTC
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.
Jul 2026
Jun 2026
- Resolved · UTC
Capacity availability and project creation, resize, and restart operations have returned to normal and have remained stable for an extended period of time. We are resolving this incident.
Out of an abundance of caution, and out of respect for the impact this incident had for our users, we held the incident open for a considerable amount of time after the observed impact was mitigated. We wanted to be certain any residual potential impact was fully cleared before formally resolving the statuspage.
- Update · UTC
We continue to monitor capacity across all regions.
The additional mitigations and machine types available to all Postgres versions are contributing to capacity stability. We continue to work to improve our resiliency.
We will continue monitoring closely to ensure ongoing work is effective and we don't have any re-occurrence of these or similar issues before we resolve this entirely.
- Update · UTC
We continue to monitor capacity recovery across all regions.
We have added additional mitigations and machine types available to all Postgres versions, and we are also seeing error rates for these users stabilize. While there is still ongoing work behind the scenes to continue to improve our resiliency, users should no longer be affected by capacity issues stemming from this incident. We are showing stable capacity across all regions on all machine sizes and types.
We will be monitoring this thru the rest of the week to ensure ongoing work is effective and we don't have any re-occurrence of these or similar issues before we resolve this entirely.
- Monitoring · UTC
Capacity has continued to recover across all regions, and the large majority of restart, resize, and project-creation operations are now completing normally. We are continuing to monitor the system.
We have added additional mitigations and machine types available to all Postgres versions, and we are also seeing error rates for these users stabilize. While there is still ongoing work behind the scenes to continue to improve our resiliency, users should no longer be affected by capacity issues stemming from this incident. We are showing stable capacity across all regions on all machine sizes and types.
We will be monitoring this for the next day or two at least just to ensure the ongoing work is effective and we don't have any re-occurrence of these or similar issues before we resolve this entirely.
If you continue to receive errors relating to capacity, please notify our support team via https://supabase.help and reference this status page.
- Update · UTC
Capacity has continued to recover across all regions, and the large majority of restart, resize, and project-creation operations are now completing normally. We are continuing to monitor the system.
The remaining impact is limited to projects running a Postgres version older than 17.6.1.121. These older versions can only run on a narrower set of instance types, which are the ones still under capacity pressure, so a restart or resize may fail or need a retry. Projects on 17.6.1.121 or newer can run on a wider set of instance types and are much less likely to be affected.
If a restart or resize is failing, upgrading to Postgres 17.6.1.121 or newer resolves it in most cases. You can check your current version and start an upgrade from your project's infrastructure settings here: https://supabase.com/dashboard/project/_/settings/infrastructure
If you're still unable to resize or restart after upgrading, our support team can help.We will update this page as the situation materially changes.
- Update · UTC
We are continuing to monitor available capacity in all regions.
If your project is on a version older than Postgres 17.6.1.121, upgrading to 17.6.1.121 and above will grant access to additional machine types, which improves the likelihood of a successful restart or resize. You can check your current version and start an upgrade from your project's infrastructure settings here: https://supabase.com/dashboard/project/_/settings/infrastructure
If your project is affected and you're unable to resize or restart, our support team can help.
We'll update this page as the situation materially changes.
- Update · UTC
Update - Availability for smaller compute sizes has improved across most regions, and error rates are trending down. We are continuing to monitor available capacity in all regions.
If your project is on a version older than Postgres 17.6.1.121, upgrading to 17.6.1.121 and above will grant access to additional machine types, which improves the likelihood of a successful restart or resize. You can check your current version and start an upgrade from your project's infrastructure settings here: https://supabase.com/dashboard/project/_/settings/infrastructure
If your project is affected and you're unable to resize or restart, our support team can help.
We'll update this page as the situation materially changes.
- Update · UTC
We're continuing to work through elevated capacity errors affecting some restart and resize operations. Availability for smaller compute sizes has improved across most regions, and error rates are trending down.
Capacity for some smaller compute sizes remains constrained in a number of regions, most notably Medium. We are actively adding capacity across all regions to relieve this.
If your project is on Postgres 17.6.1.121 or earlier, upgrading to 17.6.1.121 or higher gives it access to additional machine types, which improves the likelihood of a successful restart or resize in affected regions. You can check your current version and start an upgrade from your project's infrastructure settings: https://supabase.com/dashboard/project/_/settings/infrastructure
If your project is affected and you're unable to resize or restart, our support team can help.
We'll update this page as the situation materially changes.
- Update · UTC
Capacity is currently available across all regions, and we are continuing to progress the remaining mitigation work, including bringing additional capacity online. This remains our highest priority.
We have recovered most projects that were unavailable due to infrastructure compatibility constraints. Our team is continuing to restore the remaining affected projects and will provide further updates as this work progresses.
The remaining impact is primarily limited to Medium instances running PostgreSQL versions earlier than 17.6.1.121.
New project deployments should succeed, but restarts or resizes for projects matching this profile may fail.Existing projects are not affected unless they have been restarted or resized during this incident.
- Update · UTC
We currently have capacity available across all regions and are continuing to make progress on our remaining mitigation work, primarily by bringing additional capacity online. This is currently our top priority.
We are also recovering a subset of projects which are still down due to infrastructure compatibility constraints. Our team is continuing to restore these remaining affected projects and will provide further updates as this work progresses.
This issue does not affect existing projects or their availability unless the instance has undergone restarts or resizes while the incident has been in progress.
- Update · UTC
We continue to see capacity improvements across all regions and have implemented mitigation measures to sustain capacity. Project creation, resizing, restarts, and branch operations are continuing to recover, and we ask users to retry their database actions. Please reach out to our support if you continue to see failures.
We are working to recover subset of projects which are still down due to infrastructure compatibility constraints. Our team is actively working on solutions to restore these remaining affected projects and will provide further updates as this work progresses.
This issue does not affect existing projects or their availability unless the instance has undergone restarts or resizes while the incident has been in progress.
- Update · UTC
We continue to see capacity improvements across all regions and have implemented mitigation measures to sustain capacity. Project creation, resizing, restarts, branch revisioning, and restores are continuing to recover, and we ask users to retry their database actions. Please reach out to our support if you continue to see failures.
Our team is actively working to restore the remaining affected projects. We will provide further updates as this work progresses.
This issue does not affect existing projects or their availability unless the instance has undergone restarts with stores or database upgrades while the incident has been in progress
- Update · UTC
We are seeing capacity improvements across all regions, but are continuing to work on a full mitigation for all users. Project creation, project resizing, project restarts, branch provisioning, and restores are slowly recovering and we are asking users to re-try their database actions. Please reach out to our Support if you continue to fail.
Running projects are unaffected and stay available. The issue has only surfaced during a restart, restore, or database upgrade.
We are still addressing an issue with Read Replicas and continuing to increase capacity to restore normal service in full with highest priority.
- Update · UTC
We continue to experience widespread capacity constraints across most regions, affecting project creation, project resizing, project restarts, branch provisioning, and restores. As a result, some users may experience repeated failures when attempting these operations.
Our team is actively implementing mitigation measures to increase capacity and restore normal service.
We will provide further updates as the situation evolves.If you're attempting to create a new project, we recommend waiting until the incident has progressed and the status page indicates that additional capacity has been made available before retrying.
This issue does not affect existing projects or their availability unless the instance undergoes restarts, restores, or database upgrades.
- Update · UTC
We continue to experience widespread capacity constraints across most regions, affecting project creation, project resizing, project restarts, branch provisioning, and restores. As a result, some users may experience repeated failures when attempting these operations.
Our team is actively implementing mitigation measures to increase capacity and restore normal service.
We will provide further updates as the situation evolves.If you're attempting to create a new project, we recommend waiting until the incident has progressed and the status page indicates that additional capacity has been made available before retrying.
This issue does not affect existing running projects or their availability. - Update · UTC
We continue to experience intermittent capacity related issues across all regions, impacting operations such as project creation, project resizing, branch provisioning, and project restarts.
These operations may fail intermittently or require one or more retries to complete successfully.
Our team is actively investigating ways to improve the situation and is implementing a number of mitigation measures to reduce the impact on affected operations.
We will provide another update as soon as more information becomes available. - Update · UTC
We are continuing to remediate the capacity constraints affecting multiple regions (ap-northeast-1, ap-northeast-2, ap-south-1, ap-southeast-1, ap-southeast-2, eu-central-2, eu-north-1, sa-east-1, us-east-1, us-east-2).
Project operations that require capacity in these regions may continue to fail or require a re-try. We will provide another update as soon as more information is available.
- Update · UTC
We are continuing to investigate the remaining capacity constraints affecting ap-northeast-2, ap-south-1, and eu-north-1. Project operations that require capacity in these regions may continue to fail. We will provide another update as soon as more information is available.
- Update · UTC
We are continuing to investigate the remaining capacity constraints affecting ap-northeast-2, ap-south-1, and eu-north-1. Project operations that require capacity in these regions may continue to fail. We will provide another update as soon as more information is available.
- Update · UTC
Additional capacity has been made available in the majority of regions, and we're seeing reduced failure rates in terms of project creation, project resizing, branch provisioning, and project restarts.
We are still experiencing limited instance capacity in ap-northeast-2, ap-south-1, and eu-north-1.
As a result, project operations that require capacity in these regions, including project creation, resizing, branch provisioning, restarts, may continue to fail.
We are actively working to restore full capacity and will provide another update as soon as more information is available. - Update · UTC
We are still working to resolve the issue affecting project creation, project resizing, branch provisioning, and project restarts across multiple regions. We will continue to provide updates as our work progresses.
- Update · UTC
We are still working to resolve the issue affecting project creation, project resizing, branch provisioning, and project restarts across multiple regions. We will continue to provide updates as our work progresses.
- Update · UTC
We are continuing to work on a fix for the issue and will provide updates as more information is available.
- Identified · UTC
We have identified the issue and are working on a fix. Impact is currently affecting project creation, project resizing, branch provisioning, and project restarts across multiple regions. We will provide another update as soon as we have more information.
- Update · UTC
We have identified the issue and confirmed that impact extends beyond project creation. Project creation, project resizing, branch provisioning, and project restarts are currently affected across multiple regions. We will share another update as soon as we have more information.
- Update · UTC
Project creation is impacted across multiple regions, we are investigating the root cause.
- Investigating · UTC
We are currently investigating an issue affecting project creation in multiple regions.
