Supabase Status
Real-time updates of Supabase issues and outages
Supabase status is Operational
ap-northeast-1
ap-northeast-2
ap-south-1
ap-southeast-1
ap-southeast-2
ca-central-1
eu-central-1
You're checking on Supabase - but is your own site converting?
Outages aren't the only thing that costs you visitors.
Get a visual audit that shows exactly where your site loses conversions.
Free, takes 2 minutes.
Active Incidents
No active incidents
Recently Resolved Incidents
Certain project actions are failing. We are actively investigating to determine the regions impacted and source of the issue.
Resolved: Project actions have been sustained at normal performance. This incident is resolved.
Monitoring: The mitigation has returned project activity to normal performance. Project actions that failed during the outage are being requeued to run. We will continue to monitor to ensure project functionality.
Identified: We have identified a problem with a specific job in us-east-1, we have mitigated the job and are observing the results.
Investigating: We are testing mitigation options to attempt to restore project action performance.
Investigating: We have determined that there are four main project actions impacted in the identified regions: Pause/unpause failures, Restore/PITR failures, PITR configuration failures and Backup problems. We are pursuing root cause and mitigation options in parallel.
Investigating: Project actions in us-east-1, us-east-2, sa-east-1, ca-central-1 are experiencing significant increases in error rates. We are exploring the best options for restoring performance.
Investigating: Certain project actions are failing. We are actively investigating to determine the regions impacted and source of the issue.
We have identified an issue where S3 endpoints for keys with special characters will be broken. We are actively investigating the correct mitigation for this issue.
Resolved: This incident has been resolved. A recent API Gateway deployment altered how certain special characters in S3 object key paths were encoded before reaching storage, causing signature verification failures (403) for affected requests.
The change has been reverted and issue is now fixed.
Identified: We have implemented a PR rollback to mitigate this issue. We will actively monitor its progress
Identified: A likely mitigation has been identified and we are discussing the proper implementation method.
Identified: We have identified an issue where S3 endpoints for keys with special characters will be broken. We are actively investigating the correct mitigation for this issue.
We are currently investigating an issue affecting the ability to view and manage authentication providers in the Supabase dashboard.
Resolved: This issue has been resolved.
Monitoring: A fix has been deployed for the issue that affects configuring Authentication Providers. We are monitoring the results to confirm the issue has been fully resolved.
Identified: We have identified the issue and are actively working on a fix. We will share another update as soon as we have more information.
Investigating: We are currently investigating an issue affecting the ability to view and manage authentication providers in the Supabase dashboard.
We are currently investigating an issue affecting project creation in multiple regions.
Resolved: 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.
Monitoring: 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.
Monitoring: 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: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: We are continuing to work on a fix for the issue and will provide updates as more information is available.
Identified: 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.
Investigating: 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.
Investigating: Project creation is impacted across multiple regions, we are investigating the root cause.
Investigating: We are currently investigating an issue affecting project creation in multiple regions.
Supabase Outage Survival Guide
Supabase Components
Supabase Compute capacity
ap-northeast-1
We are currently investigating an issue affecting project creation in multiple regions.
Resolved: 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.
Monitoring: 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.
Monitoring: 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: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: We are continuing to work on a fix for the issue and will provide updates as more information is available.
Identified: 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.
Investigating: 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.
Investigating: Project creation is impacted across multiple regions, we are investigating the root cause.
Investigating: We are currently investigating an issue affecting project creation in multiple regions.
ap-northeast-2
We are currently investigating an issue affecting project creation in multiple regions.
Resolved: 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.
Monitoring: 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.
Monitoring: 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: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: We are continuing to work on a fix for the issue and will provide updates as more information is available.
Identified: 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.
Investigating: 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.
Investigating: Project creation is impacted across multiple regions, we are investigating the root cause.
Investigating: We are currently investigating an issue affecting project creation in multiple regions.
ap-south-1
We are currently investigating an issue affecting project creation in multiple regions.
Resolved: 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.
Monitoring: 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.
Monitoring: 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: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: We are continuing to work on a fix for the issue and will provide updates as more information is available.
Identified: 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.
Investigating: 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.
Investigating: Project creation is impacted across multiple regions, we are investigating the root cause.
Investigating: We are currently investigating an issue affecting project creation in multiple regions.
ap-southeast-1
We are currently investigating an issue affecting project creation in multiple regions.
Resolved: 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.
Monitoring: 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.
Monitoring: 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: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: We are continuing to work on a fix for the issue and will provide updates as more information is available.
Identified: 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.
Investigating: 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.
Investigating: Project creation is impacted across multiple regions, we are investigating the root cause.
Investigating: We are currently investigating an issue affecting project creation in multiple regions.
ap-southeast-2
We are currently investigating an issue affecting project creation in multiple regions.
Resolved: 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.
Monitoring: 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.
Monitoring: 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: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: We are continuing to work on a fix for the issue and will provide updates as more information is available.
Identified: 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.
Investigating: 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.
Investigating: Project creation is impacted across multiple regions, we are investigating the root cause.
Investigating: We are currently investigating an issue affecting project creation in multiple regions.
ca-central-1
We are currently investigating an issue affecting project creation in multiple regions.
Resolved: 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.
Monitoring: 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.
Monitoring: 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: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: We are continuing to work on a fix for the issue and will provide updates as more information is available.
Identified: 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.
Investigating: 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.
Investigating: Project creation is impacted across multiple regions, we are investigating the root cause.
Investigating: We are currently investigating an issue affecting project creation in multiple regions.
eu-central-1
We are currently investigating an issue affecting project creation in multiple regions.
Resolved: 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.
Monitoring: 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.
Monitoring: 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: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: We are continuing to work on a fix for the issue and will provide updates as more information is available.
Identified: 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.
Investigating: 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.
Investigating: Project creation is impacted across multiple regions, we are investigating the root cause.
Investigating: We are currently investigating an issue affecting project creation in multiple regions.
eu-central-2
We are currently investigating an issue affecting project creation in multiple regions.
Resolved: 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.
Monitoring: 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.
Monitoring: 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: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: We are continuing to work on a fix for the issue and will provide updates as more information is available.
Identified: 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.
Investigating: 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.
Investigating: Project creation is impacted across multiple regions, we are investigating the root cause.
Investigating: We are currently investigating an issue affecting project creation in multiple regions.
eu-north-1
We are currently investigating an issue affecting project creation in multiple regions.
Resolved: 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.
Monitoring: 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.
Monitoring: 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: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: We are continuing to work on a fix for the issue and will provide updates as more information is available.
Identified: 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.
Investigating: 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.
Investigating: Project creation is impacted across multiple regions, we are investigating the root cause.
Investigating: We are currently investigating an issue affecting project creation in multiple regions.
eu-west-1
We are currently investigating an issue affecting project creation in multiple regions.
Resolved: 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.
Monitoring: 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.
Monitoring: 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: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: We are continuing to work on a fix for the issue and will provide updates as more information is available.
Identified: 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.
Investigating: 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.
Investigating: Project creation is impacted across multiple regions, we are investigating the root cause.
Investigating: We are currently investigating an issue affecting project creation in multiple regions.
eu-west-2
We are currently investigating an issue affecting project creation in multiple regions.
Resolved: 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.
Monitoring: 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.
Monitoring: 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: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: We are continuing to work on a fix for the issue and will provide updates as more information is available.
Identified: 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.
Investigating: 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.
Investigating: Project creation is impacted across multiple regions, we are investigating the root cause.
Investigating: We are currently investigating an issue affecting project creation in multiple regions.
eu-west-3
We are currently investigating an issue affecting project creation in multiple regions.
Resolved: 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.
Monitoring: 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.
Monitoring: 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: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: We are continuing to work on a fix for the issue and will provide updates as more information is available.
Identified: 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.
Investigating: 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.
Investigating: Project creation is impacted across multiple regions, we are investigating the root cause.
Investigating: We are currently investigating an issue affecting project creation in multiple regions.
sa-east-1
We are currently investigating an issue affecting project creation in multiple regions.
Resolved: 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.
Monitoring: 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.
Monitoring: 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: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: We are continuing to work on a fix for the issue and will provide updates as more information is available.
Identified: 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.
Investigating: 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.
Investigating: Project creation is impacted across multiple regions, we are investigating the root cause.
Investigating: We are currently investigating an issue affecting project creation in multiple regions.
us-east-1
We are currently investigating an issue affecting project creation in multiple regions.
Resolved: 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.
Monitoring: 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.
Monitoring: 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: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: We are continuing to work on a fix for the issue and will provide updates as more information is available.
Identified: 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.
Investigating: 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.
Investigating: Project creation is impacted across multiple regions, we are investigating the root cause.
Investigating: We are currently investigating an issue affecting project creation in multiple regions.
us-east-2
We are currently investigating an issue affecting project creation in multiple regions.
Resolved: 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.
Monitoring: 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.
Monitoring: 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: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: We are continuing to work on a fix for the issue and will provide updates as more information is available.
Identified: 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.
Investigating: 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.
Investigating: Project creation is impacted across multiple regions, we are investigating the root cause.
Investigating: We are currently investigating an issue affecting project creation in multiple regions.
us-west-1
We are currently investigating an issue affecting project creation in multiple regions.
Resolved: 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.
Monitoring: 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.
Monitoring: 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: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: 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.
Identified: We are continuing to work on a fix for the issue and will provide updates as more information is available.
Identified: 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.
Investigating: 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.
Investigating: Project creation is impacted across multiple regions, we are investigating the root cause.
Investigating: We are currently investigating an issue affecting project creation in multiple regions.
Supabase Analytics
Supabase API Gateway
Supabase Auth
Supabase Connection Pooler
Supabase Dashboard
We are currently investigating an issue affecting the ability to view and manage authentication providers in the Supabase dashboard.
Resolved: This issue has been resolved.
Monitoring: A fix has been deployed for the issue that affects configuring Authentication Providers. We are monitoring the results to confirm the issue has been fully resolved.
Identified: We have identified the issue and are actively working on a fix. We will share another update as soon as we have more information.
Investigating: We are currently investigating an issue affecting the ability to view and manage authentication providers in the Supabase dashboard.
Supabase Database
Certain project actions are failing. We are actively investigating to determine the regions impacted and source of the issue.
Resolved: Project actions have been sustained at normal performance. This incident is resolved.
Monitoring: The mitigation has returned project activity to normal performance. Project actions that failed during the outage are being requeued to run. We will continue to monitor to ensure project functionality.
Identified: We have identified a problem with a specific job in us-east-1, we have mitigated the job and are observing the results.
Investigating: We are testing mitigation options to attempt to restore project action performance.
Investigating: We have determined that there are four main project actions impacted in the identified regions: Pause/unpause failures, Restore/PITR failures, PITR configuration failures and Backup problems. We are pursuing root cause and mitigation options in parallel.
Investigating: Project actions in us-east-1, us-east-2, sa-east-1, ca-central-1 are experiencing significant increases in error rates. We are exploring the best options for restoring performance.
Investigating: Certain project actions are failing. We are actively investigating to determine the regions impacted and source of the issue.
Supabase Edge Functions
Supabase Management API
Certain project actions are failing. We are actively investigating to determine the regions impacted and source of the issue.
Resolved: Project actions have been sustained at normal performance. This incident is resolved.
Monitoring: The mitigation has returned project activity to normal performance. Project actions that failed during the outage are being requeued to run. We will continue to monitor to ensure project functionality.
Identified: We have identified a problem with a specific job in us-east-1, we have mitigated the job and are observing the results.
Investigating: We are testing mitigation options to attempt to restore project action performance.
Investigating: We have determined that there are four main project actions impacted in the identified regions: Pause/unpause failures, Restore/PITR failures, PITR configuration failures and Backup problems. We are pursuing root cause and mitigation options in parallel.
Investigating: Project actions in us-east-1, us-east-2, sa-east-1, ca-central-1 are experiencing significant increases in error rates. We are exploring the best options for restoring performance.
Investigating: Certain project actions are failing. We are actively investigating to determine the regions impacted and source of the issue.
Supabase Realtime
Supabase Storage
We have identified an issue where S3 endpoints for keys with special characters will be broken. We are actively investigating the correct mitigation for this issue.
Resolved: This incident has been resolved. A recent API Gateway deployment altered how certain special characters in S3 object key paths were encoded before reaching storage, causing signature verification failures (403) for affected requests.
The change has been reverted and issue is now fixed.
Identified: We have implemented a PR rollback to mitigate this issue. We will actively monitor its progress
Identified: A likely mitigation has been identified and we are discussing the proper implementation method.
Identified: We have identified an issue where S3 endpoints for keys with special characters will be broken. We are actively investigating the correct mitigation for this issue.