Supabase Outage History

Uptime record, past incidents, and downtime history for Supabase.

Checking current status...

90-Day Trend

Monthly Uptime

Month	Uptime	Days Tracked	Days with Issues
July 2026	0%	10	10
June 2026	20%	30	24
May 2026	25.8%	31	23
April 2026	65%	20	7

Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.

Daily Status (Last 91 Days)

Apr 11 Today

Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

July 2026

Degraded log ingestion

minor

Started: Jul 9, 11:34 PM

investigating

We are currently investigating an issue affecting log ingestion across all regions. During this time, some logs may be delayed or unavailable.

Jul 9, 11:34 PM

Elevated JWT authorization errors

minor

Started: Jul 8, 6:37 PM

monitoring

A rollback mitigation implemented by our team has addressed the problem. Edge functions have returned to normal. We will continue to monitor performance.

Jul 8, 7:28 PM

identified

We have identified likely reasons for the problem and are investigating options for resolution. We advise all customers to ensure they are using valid JWT keys with their projects.

Jul 8, 7:16 PM

investigating

We are aware of reports of elevated legacy JWT authorization errors on edge functions in some regions

Jul 8, 6:37 PM

Project creation delays in AP regions

minor

Started: Jul 8, 4:52 PM

monitoring

Recovery has continued and project creation in the relevant region has returned to normal. We will continue to monitor this for another 30 minutes.

Jul 8, 6:59 PM

identified

Project creation is recovering. We are actively tracking recovery.

Jul 8, 6:42 PM

identified

We have identified options for mitigation and are discussing the best implementation methods for them.

Jul 8, 6:12 PM

identified

We continue our investigation into how to mitigate the project creation delays. We are examining relevant data paths in detail.

Jul 8, 5:44 PM

identified

We have identified the cause of the creation delays and are actively working to address the problem.

Jul 8, 5:17 PM

investigating

We are aware of project creation taking longer than normal in AP regions. A retry should enable completion of creation for those impacted. NOTE: This incident is not related to the ongoing capacity issues incident we are monitoring.

Jul 8, 4:52 PM

Endpoints in Americas regions returning 500 Internal server error

major

Started: Jul 6, 2:45 PM

monitoring

The fix has been applied and there are improvements to the error rates. We are continuing to work on ensuring the underlying issue does not recur.

Jul 6, 3:42 PM

identified

We have identified the cause of the 500 errors and are implementing a fix.

Jul 6, 3:15 PM

investigating

The scope of the errors is across regions in the Americas. We are narrowing down the likely causal chains.

Jul 6, 3:10 PM

investigating

The 500 errors are limited to us-east-1, we are actively exploring causes.

Jul 6, 2:47 PM

investigating

Multiple endpoints are returning 500 Internal server errors across our platform. We are investigating what has caused these errors.

Jul 6, 2:45 PM

Degraded project creation success rates in the ca-central-1 region

minor

Started: Jul 2, 10:59 PM

monitoring

We have restored project creation startup time in ca-central-1 and are monitoring the situation for full recovery.

Jul 3, 2:56 AM

identified

We are redirecting project creation to more healthy regions and working to continue to increase the success rate in ca-central-1. A longer startup time is expected while project creation is recovering in ca-central-1.

Jul 3, 2:13 AM

identified

We are continuing to work on a fix for the issue and will provide another update as soon as we have more information to share.

Jul 3, 12:26 AM

identified

We have identified the root cause and are working on a fix.

Jul 2, 11:35 PM

investigating

We are seeing degraded project creation success rates in the ca-central-1 region. We are currently investigating the issue, and will provide an update soon.

Jul 2, 10:59 PM

Errors when attempting to view advisor results in the Supabase dashboard

minor

Started: Jul 2, 2:26 PM

monitoring

We've deployed the fix and are now monitoring the issue.

Jul 2, 4:53 PM

identified

We continue to work on a fix for advisor results in the Dashboard. Affected users may be unable to run Performance Advisors and may see an error when attempting to view advisor results in the Dashboard.

Jul 2, 3:42 PM

identified

We are investigating an issue affecting the Performance Advisors feature for some projects. Affected users may be unable to run Performance Advisors and may see an error when attempting to view advisor results in the Dashboard. Our team has identified the cause and is working to implement a fix. We will provide another update as soon as more information becomes available.

Jul 2, 2:26 PM

Delays in newly created project setup

minor

Started: Jul 1, 5:39 PM

monitoring

Provisioning times and project lifecycle operations have returned normal. We will continue to monitor.

Jul 1, 6:40 PM

identified

We are currently seeing delays affecting the setup of Realtime, Storage, and shared pooler services for newly created projects. Customers may experience longer than expected provisioning times after creating a new project, and some project lifecycle operations may also be delayed while setup completes. Our team is has identified the issue and are working to restore normal provisioning times. We will provide another update as soon as we have more information.

Jul 1, 5:39 PM

Issues with Restore to New Project

Started: Jul 1, 3:16 PM

identified

We have identified an issue with the Restore to New Project beta feature and we are implementing a fix. The Restore to New Project beta feature will be temporarily unavailable while we fix this issue. We will update this page when the fix has been rolled out.

Jul 1, 3:16 PM

Functions management API is returning 500s for multiple function operations

major

Started: Jul 1, 2:40 PM

monitoring

We have implemented a fix, and error rates have returned to expected levels. We are continuing to monitor the platform closely to ensure the issue is fully resolved.

Jul 1, 3:30 PM

identified

The team has identified the root cause of the issue and is currently rolling out a fix across the platform. We will continue to monitor the rollout and provide another update once it has been completed.

Jul 1, 2:59 PM

investigating

We are currently investigating an issue affecting the Edge Function API requests. Our team is working on a fix, and we will provide another update as soon as more information becomes available.

Jul 1, 2:40 PM

June 2026

Connection issues in Supavisor us-east-1 cluster

Started: Jun 30, 4:56 PM

monitoring

We believe the issue has resolved. We are monitoring for any recurrence.

Jun 30, 5:06 PM

investigating

We have detected increased rates of connection issues in a us-east-1 Supavisor cluster starting at 14:10 UTC. Our team is currently investigating.

Jun 30, 4:56 PM

Project status change failures in multiple regions

major

Started: Jun 30, 3:08 AM

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 th...

Jul 8, 4:41 PM

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

Jul 6, 4:36 PM

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 c...

Jul 6, 11:32 AM

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 r...

Jul 4, 10:40 PM

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

Jul 4, 4:34 AM

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 add...

Jul 3, 7:57 PM

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

Jul 3, 4:03 PM

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 projec...

Jul 3, 9:43 AM

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 thes...

Jul 2, 3:08 PM

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 exi...

Jul 2, 10:40 AM

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

Jul 2, 5:53 AM

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 waiti...

Jul 2, 1:30 AM

identified

Jul 1, 4:58 PM

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

Jul 1, 10:12 AM

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.

Jul 1, 3:23 AM

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.

Jun 30, 10:22 PM

identified

Jun 30, 6:58 PM

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 resto...

Jun 30, 11:20 AM

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.

Jun 30, 6:49 AM

identified

Jun 30, 5:11 AM

identified

We are continuing to work on a fix for the issue and will provide updates as more information is available.

Jun 30, 4:32 AM

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.

Jun 30, 3:38 AM

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.

Jun 30, 3:08 AM

investigating

Project creation is impacted across multiple regions, we are investigating the root cause.

Jun 30, 2:43 AM

investigating

We are currently investigating an issue affecting project creation in multiple regions.

Jun 30, 2:38 AM

Upgrade Failures

minor

Started: Jun 25, 2:20 PM

monitoring

We have implemented all necessary mitigations and the project upgrade rates have returned to normal across the fleet. We will continue to monitor these flows for any irregularities or recurring degradation. If you are still experiencing delayed or blocked upgrades on your Project, please contact Support.

Jun 25, 6:08 PM

identified

We are starting to notice improvements as a result of our mitigation efforts, and expect that project upgrades should start to become less delayed. We’ll continue monitoring and will update as we observe improvements across the fleet.

Jun 25, 5:46 PM

identified

We are continuing our operational and investigative work to improve upgrade flow performance and mitigate further problems.

Jun 25, 5:03 PM

identified

We are implementing operational mitigations to try to improve upgrade performance.

Jun 25, 4:27 PM

identified

We are continuing to work through a variety of options for improving upgrade performance. This includes working with our upstream provider and adjusting operational parameters.

Jun 25, 4:03 PM

identified

We are aware that upgrades continue to be delayed. We are exploring other factors that are contributing to the slow upgrades.

Jun 25, 3:32 PM

identified

The upgrade delays have been caused by resource capacity limits. We are taking actions to increase the appropriate resources.

Jun 25, 3:01 PM

investigating

Upgrades are taking longer than usual, but generally will complete if allowed to proceed. We are investigating the cause of the delays.

Jun 25, 2:41 PM

investigating

We are investigating potential upgrade issues in multiple regions. We are working to confirm impact and determine next steps.

Jun 25, 2:20 PM

Elevated errors on Postgres change subscriptions

minor

Started: Jun 24, 11:52 PM

monitoring

We have applied a fix and are monitoring the results to ensure the issue is fully resolved.

Jun 25, 12:49 AM

identified

We have identified the cause of the elevated errors affecting Postgres change subscriptions and are actively working on a fix. We will provide another update as soon as we have additional information or progress to share.

Jun 24, 11:58 PM

investigating

We are investigating an issue causing elevated errors for some customers using Postgres change subscriptions. Our team has identified the affected component and is actively working to determine the root cause and implement a fix. We will provide another update as soon as more information is available.

Jun 24, 11:52 PM

Degraded performance of the Shared Pooler cluster in ap-southeast-1

minor

Started: Jun 24, 3:59 PM

investigating

We are aware of a period of degraded performance of the Shared Pooler cluster in ap-southeast-1. Affected projects experienced increased ECHECKOUTTIMEOUT errors when running queries. The window of the incident was between 14:48 to 15:25 UTC. The issue appears to be resolved. We are investigating the cause of this incident and will continue monitoring the cluster.

Jun 24, 3:59 PM

Project create and unpause errors in eu-west-1

minor

Started: Jun 23, 3:16 PM

monitoring

Key updates and other mitigations have been fully deployed and project creation and unpause functionality is returning to normal. We will continue to monitor this region for stability for the next 30 minutes.

Jun 23, 4:01 PM

identified

During this incident, postgres upgrade functionality has also been affected. The key updates are being deployed and other mitigations continue to take effect.

Jun 23, 3:46 PM

identified

Multiple mitigations have been deployed and project create performance is improving.

Jun 23, 3:43 PM

identified

We have identified the issue is related to keys and are preparing a mitigation.

Jun 23, 3:26 PM

investigating

We are investigating errors in creating and unpausing projects in the eu-west-1 region.

Jun 23, 3:16 PM

Increased latency for Management API requests

minor

Started: Jun 23, 1:21 PM

monitoring

Latency has returned to normal levels, and we are seeing greatly improved stability across the management API. We are monitoring for any further issues.

Jun 23, 1:39 PM

identified

We are seeing increased latency on management API requests, which results in slower-than-usual Dashboard performance, project creation and configuration changes may also be delayed. This is primarily affecting US-East-1; however, we are seeing additional latency in other regions as well. The team has identified the issue and is working on resolution.

Jun 23, 1:21 PM

Failed to apply network restrictions

minor

Started: Jun 19, 9:55 PM

monitoring

We have now deployed a fix for this issue across all regions, and we believe this issue to be resolved. We are continuing to monitor for any remaining issues. Please contact Support if you are experiencing any problems with your network restrictions list.

Jun 20, 12:48 AM

monitoring

We have started deploying a fix for the issue and are validating the results as the rollout progresses. We will continue to provide updates as we move toward full resolution.

Jun 19, 11:39 PM

identified

We have identified the root cause of the issue and are actively working on implementing a fix.

Jun 19, 10:25 PM

investigating

We are aware of some users reporting issues adding new entries to their network restriction lists, and we are currently investigating this issue.

Jun 19, 9:55 PM

DNS record creation failures impacting project creation, restore, pause

major

Started: Jun 18, 6:39 AM

monitoring

We have deployed a fix and are monitoring for full recovery. Project creation, pause and unpause are gradually restored within the next minutes.

Jun 18, 8:05 AM

identified

We have identified a fix and working on recovering the impacted system. Project creation, pause and unpause functions will be restored on confirmed service recovery.

Jun 18, 7:37 AM

investigating

We've identified an issue with DNS record creation returning 500 failures, preventing new project creation, pause and unpause. We have temporarily disabled new project creation while the issue is under review.

Jun 18, 7:09 AM

investigating

We are investigating DNS Api outage impacting project creation. Impact and details are under review.

Jun 18, 6:39 AM

Hardware failure in us-east

minor

Started: Jun 17, 3:12 PM

monitoring

All the identified affected projects in us-east-2 are now healthy. If your project is in us-east and not responsive, please open a ticket to let us know.

Jun 17, 4:13 PM

identified

We have identified projects specifically impacted by this issue and are recovering affected projects.

Jun 17, 3:44 PM

investigating

Some projects in US-East-2 are impacted by compute failures in that region. We are actively investigating the issue.

Jun 17, 3:12 PM

Degraded Management API performance affecting payments and Supabase Studio

major

Started: Jun 17, 12:31 PM

monitoring

We have resolved the degraded performance affecting our Management API in the impacted regions. All systems are now fully operational. All payment features have been re-enabled. Customers should no longer experience failed payments or failed project creations. We are continuing to monitor the system closely and will provide a final update once we have confirmed full stability.

Jun 17, 1:15 PM

investigating

We are currently experiencing degraded performance with our Management API in the following regions: ca-central-1, sa-east-1, us-east-1, and us-east-2. Customers may experience failed payments, failed project creations, and degraded performance in Supabase Studio. As a precautionary measure, we have temporarily disabled the following features while we investigate: - Top up Credits - Update Billing Information - Redeem Credits To reduce impact, we have redirected traffic to healthy regions...

Jun 17, 12:51 PM

investigating

We are currently investigating the issue

Jun 17, 12:31 PM

Project usage analytics API endpoints breakage

minor

Started: Jun 16, 3:47 PM

monitoring

The mitigation has been successful and analytics endpoints are all responsive. We will continue to monitor for stability.

Jun 16, 4:27 PM

identified

The component at issue has been identified and we are implementing mitigations. Analytics responsiveness on the impacted endpoint is begining to recover.

Jun 16, 4:22 PM

investigating

We are investigating the components involved in analytics endpoints updates to isolate any changes that could have caused this problem. The issue is limited to the usage.api-requests-count endpoint.

Jun 16, 4:18 PM

investigating

We are investigating a breakage in project usage analytics data propagation.

Jun 16, 3:47 PM

Degraded Log Explorer in the dashboard

minor

Started: Jun 16, 11:26 AM

monitoring

We are seeing things have stabilized across the fleet after further optimization work, and we are monitoring to ensure no further issues arise.

Jun 16, 1:30 PM

identified

The mitigations rolled out have resulted in a great reduction in errors and most users should now see fully-functional logging and usage charts; however, some users may still see erroneously empty usage charts on the project home page. The team is continuing to work on this issue.

Jun 16, 1:01 PM

monitoring

Some users are seeing errors or degraded performance on usage reportss and logs in the Supabase dashboard. The team has already rolled out mitigations and are seeing improvements. We are continuing to monitor the results.

Jun 16, 11:26 AM

Storage users in US-West-2 experiencing increased latency on storage requests

minor

Started: Jun 12, 4:00 PM

monitoring

Job queues continue to drain. We will actively monitor until they are complete.

Jun 12, 11:57 PM

monitoring

Backlog is being effectively processed and operations have returned to normal. We continue to monitor the performance in us-west-2.

Jun 12, 8:26 PM

identified

We are seeing improvement in the performance of us-west-2 after implementation of our mitigation strategies. Storage operation is returning to normal. We will continue to monitor performance in this region.

Jun 12, 7:30 PM

identified

We have implemented further mitigations and are tracking their progress. We continue to actively work this issue.

Jun 12, 6:28 PM

identified

The team is still working on a solution, and mitigation work is underway.

Jun 12, 5:29 PM

identified

We are implementing load mitigation strategies to improve the performance of storage requests in US-West-2.

Jun 12, 4:30 PM

identified

Users in US-West-2 are seeing increased latency on storage requests. The team has identified the issue and is working on a solution.

Jun 12, 4:00 PM

DNS Resolution Failures for TLD .co users

Started: Jun 8, 3:39 AM

monitoring

The top-level domain provider has fixed the underlying problem that was causing this issue. Name resolution has returned to normal. We will monitor this for continued functionality.

Jun 15, 4:52 PM

monitoring

Our upstream TLD provider is continuing to make changes to its network routing policies to address this issue. These changes are intended to improve regional traffic routing and reduce DNS resolution failures. We have already begun to see improvements as these changes take effect, but the issue has not yet been fully resolved. We are continuing to monitor the situation closely and work with the provider toward a complete resolution. We will provide another update as soon as more information...

Jun 12, 11:09 AM

monitoring

Our upstream TLD provider believes they have identified the underlying issue, and we are continuing to coordinate with them to review their findings and potential remediation options. In parallel, we are investigating other factors that may be contributing to the ongoing resolution problems affecting a subset of customers. VPNs continue to provide a workaround for impacted end users while our investigation remains ongoing.

Jun 10, 11:24 PM

monitoring

We have opened a follow-up issue with our provider to address the continued problems a subset of our customers in the Americas are experiencing with top-level ".co" domain resolution. We will continue to pursue this issue until it is resolved and customers who have reported the issue are able to correctly resolve the domain name.

Jun 8, 5:32 PM

monitoring

Our testing has observed that the issue is related to selected ISP resolvers to .co domains. The clients impacted are mainly located in us-east-1, us-east-2 region. We continue to review this issue for resolution with our third party network partner.

Jun 8, 12:38 PM

monitoring

The third-party has confirmed a fix has been implemented and we are validating the results with our impacted users.

Jun 8, 6:37 AM

identified

We are investigating reports of DNS resolution failures affecting a subset of customers connecting to Supabase project endpoints. This appears to be related to a third-party issue with .co TLD resolution impacting multiple DNS providers. Customers may be able to bypass this issue by using a VPN while we work towards resolution. We will update the statuspage when we have more information to share.

Jun 8, 3:39 AM

Errors impacting pause, restore, and backup operations in us-east-2 (Ohio)

critical

Started: Jun 2, 1:36 PM

monitoring

The redeployment has returned pause, restore and backup operations in the affected region to normal. We will continue to monitor for any residual impact.

Jun 2, 2:12 PM

identified

We have identified the cause is related to a recent deployment. We have initiated a redeploy to address the issue.

Jun 2, 2:05 PM

investigating

We are currently investigating an issue affecting pause, restore, and backup operations for projects in us-east-2 (Ohio) We will provide further updates as more information becomes available.

Jun 2, 1:36 PM

May 2026

Branch creation degradation

minor

Started: May 21, 4:46 PM

monitoring

Branch creation has returned to normal. We are investigating a set of factors that likely contributed to the degradation, including cluster load, lock contention, and service start-up sequencing to identify areas for improvement going forward. We will monitor our platform for another 30 minutes to ensure the problem has fully resolved before resolving the incident.

May 21, 6:54 PM

investigating

We continue investigating different possible underlying causes and will provide updates as progress is made.

May 21, 5:45 PM

investigating

We are seeing degradation in branch creation linked to database migration locks. We are investigating and will share further updates as progress is made.

May 21, 4:46 PM

minor

Started: May 21, 8:30 AM

monitoring

We have applied a fix and are seeing login services return to normal. We will continue to monitor authentication success rates over the next 60 minutes to ensure stability.

May 21, 9:43 AM

identified

A fix has been implemented and is currently being rolled out. We will continue to provide updates as the deployment progresses.

May 21, 9:26 AM

identified

We have identified the issue as being related to a recent key rotation and are currently working on a fix.

May 21, 8:49 AM

investigating

We are currently investigating an issue causing login failures for some users attempting to authenticate to the Supabase dashboard via SSO or email/password login flows. Affected users may see an error similar to: “captcha protection: request disallowed (sitekey-secret-mismatch)” Currently logged-in users are not affected, and GitHub authentication continues to operate normally. We will continue to provide updates as more information becomes available.

May 21, 8:33 AM

investigating

Users that are already logged in are not affected.

May 21, 8:30 AM

Network restrictions preventing read replica communication

minor

Started: May 20, 9:04 PM

monitoring

We have merged the fix and are monitoring for stability.

May 21, 4:23 AM

identified

We have developed a fix and it is currently being validated. We will provide more updates soon.

May 21, 3:49 AM

identified

Our team continues to work on implementing a fix for the issue. We will provide additional updates as progress is made.

May 21, 1:12 AM

identified

Our team continues to work on implementing a fix for the issue. We are continuing to monitor the impact and will provide additional updates as progress is made.

May 20, 11:41 PM

identified

We have identified the cause of the issue impacting read replica communication for projects. Our team is actively working on a fix and continuing to assess the impact to affected projects.

May 20, 10:48 PM

investigating

We are reviewing the impact of this issue, which is limited to projects with read replicas and network restrictions. We continue to both investigate mitigation options for the issue and identify projects that may be impacted.

May 20, 9:46 PM

investigating

Network restrictions are preventing read replicas from communicating with their primaries for a limited number of customer projects. We are actively investigating this issue.

May 20, 9:04 PM

Paused Projects Showing Incorrect Resume Deadline

minor

Started: May 20, 3:40 PM

monitoring

This change has been reverted. We are monitoring to ensure things remain stable.

May 20, 7:11 PM

identified

The revert of the change is in process.

May 20, 5:41 PM

identified

We’ve isolated the cause of the issue to a recent change and are working on reverting it now.

May 20, 4:17 PM

investigating

We are currently investigating a UI issue affecting paused projects, where an incorrect resume deadline is displayed in the dashboard. The message incorrectly states that projects can be resumed within 90 days while also displaying today’s date as the expiry date. For example: “All data, including backups and storage objects, remains safe. You can resume this project from the dashboard within 90 days (until 20 May 2026). After that, this project will not be resumable, but data will still...

May 20, 3:40 PM

Log ingestion issues

minor

Started: May 18, 11:26 PM

monitoring

Logging systems have returned to normal operation. During the incident, some logs may have been delayed or unavailable. While certain upstream log sources may retry delivery automatically, we cannot guarantee recovery of all missing logs generated during the affected time period. We will continue monitoring closely to ensure ongoing stability.

May 18, 11:58 PM

investigating

Customers may experience delayed log ingestion or periods where logs are unavailable. We will provide updates while we work to resolve the issue.

May 18, 11:26 PM

Auth Service Update

Started: May 15, 6:11 PM

monitoring

The update has been implemented. Service changes can be made. We will monitor the effect for the next 30 minutes to ensure stability.

May 15, 6:47 PM

identified

We need to implement a time-sensitive update to our Auth service. Please do not make any changes to your Auth service until we have completed this update.

May 15, 6:11 PM

Access Issues From Some Providers in Brazil

Started: May 14, 3:34 PM

monitoring

The top-level domain provider has fixed the underlying problem that was causing this issue. Name resolution has returned to normal. We will monitor this for continued functionality.

Jun 15, 4:52 PM

monitoring

We continue to work with the relevant provider and have seen improvements. We are monitoring the progress that has been made to ensure it continues.

Jun 12, 2:42 PM

identified

We are engaged with senior networking team members at the impacted provider. They are actively investigating the domain name resolution issues we have reported. If you are continuing to experience .co name resolution issues in Brazil, please update your ticket or open a new ticket to let us know so we can add that information to the investigation.

Jun 9, 1:26 PM

identified

We continue to work with the service provider to resolve the residual access issues. We have scheduled direct consultations with the provider to attempt to resolve the issue.

Jun 3, 9:32 PM

identified

We are continuing to contact the ISP in Brazil to work through this issue: however they have remained unresponsive to outreach. We are exploring other options to get in touch with them. Customers may be able to bypass this issue by using a VPN or alternative network while we work towards resolution. Thank you for your patience. We will provide an update when we have more information to share.

May 19, 10:30 PM

identified

We are continuing to contact the ISP in Brazil to work through this issue. Customers may be able to bypass this issue by using a VPN or alternative network while we work towards resolution. Thank you for your patience. We will provide an update when we have more information to share.

May 14, 10:23 PM

investigating

We have made contact with the ISP in Brazil and are working through their support process for this issue. Customers may be able to bypass the problem by using a VPN or alternative network while we work towards resolution.

May 14, 4:37 PM

investigating

We have isolated the issue to a specific Internet provider in Brazil and are working to contact that provider to resolve the issue. We will update the statuspage when we have more information to share.

May 14, 3:54 PM

investigating

We are investigating reports of some access issues to Supabase IP addresses from a network provider in Brazil.

May 14, 3:34 PM

Reports of issues connecting to API Endpoints

minor

Started: May 14, 2:56 PM

investigating

We are investigating reports of connectivity issues to project API endpoints.

May 14, 2:56 PM

Edge Traffic Issues

minor

Started: May 13, 4:15 PM

identified

Our investigation has identified traffic loss along a specific network path associated with a VPN exit point located in Western Europe. Some customers are experiencing connectivity issues that impact a subset of users connecting through certain VPN providers, including Mullvad. Customers impacted while using Mullvad can contact Mullvad support directly to help raise visibility into the issue from their side.

May 13, 7:50 PM

investigating

We are continuing to actively investigate the connectivity issues impacting access to Supabase APIs for some users. Our team remains engaged in identifying the underlying cause and validating the scope of impact. We will continue to provide updates as our investigation progresses.

May 13, 5:31 PM

investigating

We are continuing to investigate connectivity issues impacting access to Supabase APIs, which may result in connection timeout errors or rejected connections for some users. At this time, we have narrowed the issue down to traffic originating from at least one VPN provider (Mullvad VPN). However, we cannot yet confirm whether additional VPN providers may also be impacted. We are actively working to identify the root cause and will continue to provide updates as we learn more.

May 13, 4:46 PM

investigating

We've observed traffic from upstream providers of a VPN provider is no longer reaching our servers. We're investigating the cause and will keep you updated.

May 13, 4:15 PM

Customer Projects Experiencing Upgrade Issues

minor

Started: May 8, 1:25 PM

monitoring

We have identified the root cause and developed a fix, which has been applied in production. Projects which have failed to upgrade will be automatically recovered and returned to ACTIVE_HEALTHY without manual intervention. Any future upgrades should complete successfully. We are continuing to monitor recovery and system stability closely.

May 8, 2:39 PM

identified

We are continuing to investigate issues impacting project upgrades. We have observed that the majority of affected projects are successfully returning to a healthy state on their previous PostgreSQL version following failed upgrade attempts. Our engineering team is actively working to manually restore the remaining projects that are still stuck during the upgrade process. As a precaution, we recommend that customers do not attempt to upgrade their projects until this incident has been fully r...

May 8, 1:46 PM

identified

We are continuing to work on a fix for this issue.

May 8, 1:26 PM

identified

Our engineering team are investigating issues with customer projects being stuck when upgrading Postgres version. We advise that you do not upgrade your project until the incident is resolved.

May 8, 1:25 PM

Network connectivity in us-east-1-az4

major

Started: May 8, 12:50 AM

monitoring

Our infrastructure provider has resolved the underlying incident, and impacted services have recovered. We have completed recovery efforts for affected projects, re-enabled project creation, pausing, and compute resizes in the us-east-1 region, and are now monitoring the platform to ensure continued stability.

May 9, 4:34 AM

identified

Our infrastructure provider has resolved the underlying incident, and the majority of impacted projects have now recovered. Our team is currently working through the remaining projects that did not automatically self-heal during recovery and is actively restoring them manually where needed. We have also re-enabled project creation, pausing, and compute resizes in the us-east-1 region. We are continuing to monitor platform stability closely and will provide additional updates as recovery progr...

May 9, 4:10 AM

identified

Our team continues to make progress restoring impacted projects safely and as quickly as possible. To support recovery efforts, project pausing and new project creation in the us-east-1-a4 region continue to be disabled. While recovery efforts are moving forward, full resolution is still expected to take several more hours based on the latest guidance from our infrastructure provider. We understand the impact this is having and appreciate your continued patience. We’ll continue to share upd...

May 9, 1:32 AM

identified

May 8, 4:34 PM

identified

Our team is actively working to bring impacted projects back online as quickly and safely as possible. While we are seeing progress, full recovery may still take several hours based on the latest guidance from our infrastructure provider. We appreciate your patience and will continue to share updates as more information becomes available.

May 8, 12:09 PM

identified

Affected projects are continuing to recover. We are monitoring the recovery of the AZ and will provide regular updates until full recovery.

May 8, 10:52 AM

identified

Affected projects are continuing to recover. We are monitoring the recovery of the AZ and will provide regular updates until full recovery.

May 8, 7:59 AM

identified

Affected projects are continuing to recover. We are monitoring the recovery of the AZ and will provide regular updates until full recovery.

May 8, 6:44 AM

identified

We're starting to see a number of affected projects starting to recover. We're still working with our upstream providers on a full recovery of all affected projects.

May 8, 5:31 AM

identified

We are continuing to work on a fix for this issue.

May 8, 5:30 AM

identified

We are continuing to work on a fix for this issue.

May 8, 4:21 AM

identified

We've disabled pausing projects in us-east-1. We recommend not changing project configurations at this time. Users cannot access their databases or run any authentication-dependent services. We are continuing to monitor this situation with our upstream provider.

May 8, 3:11 AM

identified

We have disabled project creation in us-east-1. We will provide another update in an hour, if not sooner.

May 8, 2:30 AM

identified

We are waiting on a resolution from our upstream provider. We will provide an update in an hour.

May 8, 2:05 AM

identified

We have identified the root cause of the connection issues as an outage with an upstream provider affecting a single availability zone (us-east-1a). All affected projects are located in this zone.

May 8, 1:06 AM

investigating

Increased connection times for Supavisor since about 00:10 UTC is affecting a limited number of projects in us-east-1

May 8, 12:50 AM

April 2026

403 errors for PostgREST requests

major

Started: Apr 28, 9:26 PM

monitoring

The exceptions fix has been rolled out, and we are monitoring for continued stability.

Apr 28, 11:03 PM

identified

We are continuing to work on a fix. We’ll share further updates as progress is made.

Apr 28, 10:24 PM

identified

We are continuing to work on a fix for this issue.

Apr 28, 9:40 PM

identified

The issue has been identified and we are working on a fix.

Apr 28, 9:36 PM

investigating

We are investigating 403 errors for PostgREST requests across multiple regions.

Apr 28, 9:26 PM

Some projects unavailable across multiple regions

major

Started: Apr 27, 12:39 PM

monitoring

We believe all users affected by this particular issue have been resolved. The team is going to keep an eye on these error rates to ensure we catch any that didn't originally appear, or that no new issues arise. We appreciate your patience as we worked through this issue.

Apr 27, 6:34 PM

identified

The team is continuing their mitigation efforts. We've fixed and restarted most of the affected projects. We're continuously looking for any others that are affected so we can be sure to get them all fixed.

Apr 27, 4:22 PM

identified

The team is still working to bring these back online, and have a fix under way. Many users can also resolve this on their own via a project restart. This can be performed from the <a href="https://supabase.com/dashboard/project/_/settings/general">dashboard</a> for your own projects at any time. But for those who are still seeing issues after a restart, we will be pushing a fix soon.

Apr 27, 3:00 PM

identified

We have identified this issue across multiple regions, not just eu-west-3 as originally suspected. We are expanding the scope of efforts to bring affected projects back online. Users can also resolve this, in most cases, on their own via a project restart. This can be performed from the <a href="https://supabase.com/dashboard/project/_/settings/general">dashboard</a> for your own projects at any time.

Apr 27, 1:38 PM

identified

The team is continuing to work through affected projects; however, a project restart is also effective. This can be performed from the <a href="https://supabase.com/dashboard/project/_/settings/general">dashboard</a> for your own projects at any time.

Apr 27, 1:31 PM

identified

We are seeing an increase in projects unavailable in eu-west-3 following an upstream issue with EC2 instances in the region. The team is working on restoring access to these projects

Apr 27, 12:39 PM

Some Projects Unreachable following Project Restart

major

Started: Apr 27, 10:54 AM

monitoring

The fix has been rolled out, and we are monitoring for continued stability. Any remaining impacted projects are being manually patched.

Apr 27, 5:31 PM

identified

The permanent fix has now been rolled out across the fleet. We are continuing to manually patch any remaining impacted projects to restore service.

Apr 27, 4:05 PM

identified

We’ve identified additional impacted projects and are currently working to manually patch and restore them. We are also continuing to roll out a fix across the fleet to prevent further impact.

Apr 27, 2:21 PM

monitoring

All impacted projects with open support tickets have now been manually patched and restored. We are currently rolling out a fix across the fleet to prevent further impact. We will continue to monitor progress and provide updates.

Apr 27, 1:12 PM

identified

Our team is actively working on a fix and is manually patching impacted projects to restore service as quickly as possible. If you are running a version of Postgres older than 15.1.1.57, please avoid restarting your project until this issue is resolved.

Apr 27, 11:40 AM

identified

We’ve identified that a recent change to the Postgres systemd service has a dependency on a prestart script. This script is not present on some older projects, and when those projects restart, Postgres may fail to start successfully. This can result in projects remaining offline. We are working on a fix to restore service. If you are running a version of Postgres older than 15.1.1.57, please avoid restarting your project until this issue is resolved.

Apr 27, 11:11 AM

identified

Apr 27, 10:54 AM

Increased errors in project creation and configuration changes in US-East-2 and AP-Northeast-1

major

Started: Apr 25, 4:16 AM

monitoring

Projects have recovered and capacity has been restored. All previously affected regions have been re-enabled, and we will continue to monitor to ensure stability.

Apr 25, 5:14 AM

identified

Capacity has been freed, and the regions have been re-enabled. The team is currently working on resolving any failed project starts, resizes, restarts, or other configuration changes during this event.

Apr 25, 4:38 AM

identified

US-East-2 and AP-Northeast-1 have been disabled for project creation and configuration change actions, and the team is currently working to free additional capacity in these regions.

Apr 25, 4:26 AM

identified

We are seeing new project creation, resize requests, and project restart failures due to capacity issues in us-east-1. We are disabling project creation, project resize actions, and project restarts in these regions. We have already reached out to our provider for additional capacity, and will update here as we have additional information.

Apr 25, 4:16 AM

Newly created projects may be unreachable

major

Started: Apr 24, 11:21 AM

monitoring

A fix has been implemented, and we are seeing improvements in DNS resolution. We’re closely monitoring to ensure the issue is fully resolved and services remain stable.

Apr 24, 12:43 PM

identified

We are currently experiencing an issue propagating new DNS records for our zone. We are working closely with our upstream network providers technical team to implement a fix and will share updates as we learn more.

Apr 24, 11:56 AM

investigating

We are currently investigating reports that newly created projects may be unreachable. Initial findings indicate DNS resolution failures. We will provide an update as soon as more information is available.

Apr 24, 11:21 AM

Increased Errors on HTTP Endpoints

major

Started: Apr 17, 2:53 PM

monitoring

We've received confirmation from our networking provider that there is recovery across all regions. We are able to corroborate this with our own metrics collections. We will continue to monitor for a bit, but we believe this to be resolved at this time. We apologize for the trouble, and we appreciate your patience.

Apr 18, 12:37 AM

identified

We've seen a marked improvement in error rates across all regions in the last few minutes. We are still waiting on confirmation from our provider on status, but we believe things to be improved at the moment. We'll keep working on this until we have for sure reached a resolution.

Apr 17, 11:08 PM

identified

We recognize that some of our users, especially in parts of North and South America, are continuing to experience DNS and 5XX errors when trying to connect to their projects. We have escalated this issue with our network provider and will work with them continuously until the problems are resolved.

Apr 17, 9:31 PM

identified

Some users continue to experience errors. We are raising the issue with our provider.

Apr 17, 8:35 PM

monitoring

Our upstream provider has reported their incident resolved. We will continue to monitor for any errors our customers may be experiencing for another 30 minutes.

Apr 17, 8:10 PM

identified

The fix that our upstream provider implemented has taken effect. Service has significantly improved across all previously impacted regions. There are still residual elevated error rates in a handful of regions and we will continue to work with our provider to eliminate them.

Apr 17, 7:33 PM

identified

Our upstream provider has rolled the fix out to most regions. While we are seeing improvement, we are still seeing increased error rates in Mexico and Brazil and are continuing to work with them until this is fully resolved.

Apr 17, 6:34 PM

identified

Upstream provider mitigations are still under way, and we are seeing improvements incrementally as routing regions have the mitigations applied. We are still seeing particular impact in South America, but some users in North America may still be affected as well. We anticipate continued incremental improvements and will update as we get more information.

Apr 17, 5:44 PM

identified

Our upstream networking provider has identified a fix and is currently implementing a fix. We are seeing preliminary improvements to error rates for users in North America, but are still following this issue closely with our provider.

Apr 17, 4:31 PM

identified

Our upstream networking partner is continuing their investigation. We will continue to post regular updates as we have more information.

Apr 17, 3:41 PM

identified

Our upstream networking provider has discovered an issue and has declared an incident on their side. They are currently working toward resolution. We are actively working with them and will provide updates on progress as more information is available.

Apr 17, 3:09 PM

investigating

We continue to have active lines of investigation going with our upstream network provider partners, and are still working toward a resolution. This issue affects the network-level access to projects. The projects themselves and the data in them are safe and unaffected. Users are seeing two separate symptoms of these networking issues: 1. DNS Lookup failures for supabase project URLs 2. 530 responses to HTTP requests to supabase project API Endpoints

Apr 17, 2:53 PM

investigating

We continue to work with partners and investigate.

Apr 17, 2:30 PM

investigating

We have further clarified the scope and impact of the issues currently affecting users. A subset of users across North and South America are experiencing DNS resolution failures and HTTP 530 errors. These symptoms indicate a networking-related issue impacting the availability of Supabase projects. We are actively working with both internal teams and external network providers to isolate the root cause and determine the most effective path to resolution. We will continue to provide updates as ...

Apr 17, 2:16 PM

investigating

We are actively investigating this issue and working with relevant partner organizations. At this time, we do not believe this issue is specific to any particular network provider. A subset of users continue to be impacted in both South and North America.

Apr 17, 1:51 PM

investigating

We are currently investigating reports of users experiencing login issues when using Supabase Auth. At this time, the impact appears to be limited to a subset of users, primarily in North and South America. The exact cause and scope are still being determined. Our team is actively working to identify the root of the issue and will provide updates as more information becomes available. We appreciate your patience while we investigate.

Apr 17, 1:31 PM

investigating

We are currently investigating reports of users experiencing login issues when using Supabase Auth. At this time, the impact appears to be limited to a subset of users, primarily in South America. The exact cause and scope are still being determined. Our team is actively working to identify the root of the issue and will provide updates as more information becomes available. We appreciate your patience while we investigate.

Apr 17, 1:02 PM

Transactional Email Delivery Delays

Started: Apr 16, 7:05 PM

monitoring

Customers will continue to see these delayed transactional emails while we clear the backlog. We will provide another update once these queued emails are sent.

Apr 16, 8:51 PM

monitoring

We have made progress investigating the specific causes of the email spike and are determining appropriate next steps to improve clearance of the backlog.

Apr 16, 7:37 PM

monitoring

We are experiencing delays in delivery of some of our email to customers related to transactions, including new welcome, oauth-approved, project-shutdown, and payment-failure notifications. This has caused some customers to receive notifications after their issue has been resolved (for example, payment failure notifications after payment has been issued). We are actively monitoring the email delivery queue and expect the delays to be eliminated over time. We will update this status as appropr...

Apr 16, 7:05 PM

Project creation failures in some APAC regions

major

Started: Apr 12, 3:51 PM

investigating

We are currently investigating an issue affecting project creation in some APAC regions. Users may experience failures when attempting to create new projects in impacted regions. Existing projects are not impacted. Our team is actively working to mitigate the issue and restore normal availability. We will share further updates as more information becomes available.

Apr 12, 3:51 PM

Logs currently inaccessible via the Dashboard and Log Drains

critical

Started: Apr 8, 7:10 PM

monitoring

All log sources have been restored and logs should be available to users again now. We are keeping an eye on things to ensure ongoing stability.

Apr 8, 7:41 PM

identified

The underlying logging platform has stabilized, and some log sources have been restored and are successfully ingesting logs. The team is working to restore the rest of the log sources now.

Apr 8, 7:24 PM

identified

Users may see errors when attempting to retrieve logs via the Supabase dashboard or may not see new logs arriving via log drains. The team has identified the issue and is working on a fix. Underlying projects are unaffected, this is only affecting the logging service.

Apr 8, 7:11 PM

Increased error rates for plan upgrades

major

Started: Apr 2, 8:28 AM

monitoring

A fix has been applied, and we are monitoring to ensure stability.

Apr 2, 9:05 AM

identified

We have identified the cause of increased error rates affecting plan upgrades and are working on a fix. We will provide further updates as progress is made.

Apr 2, 8:40 AM

investigating

We are currently investigating increased error rates affecting plan upgrades. Our team is actively working to identify the root cause and restore normal functionality. We will provide updates as more information becomes available.

Apr 2, 8:28 AM

Degraded logs ingestion

major

Started: Apr 1, 12:13 AM

monitoring

We have identified the issue and a fix is in place. We will continue to monitor to ensure stability.

Apr 1, 12:47 AM

investigating

We are seeing degradation of logs and are currently investigating the cause of this issue.

Apr 1, 12:13 AM

March 2026

Project Creation Degradation

minor

Started: Mar 27, 5:58 PM

monitoring

Project creation has returned to normal. We continue to actively monitor and operate our platform for stability and consistency.

Mar 27, 6:18 PM

identified

We have experienced problems with project creation, the issue has been identified and mitigation steps have been implemented.

Mar 27, 5:58 PM

Degraded Log Ingestion

minor

Started: Mar 27, 3:13 PM

monitoring

Our capacity mitigations have taken effect and ingestion has returned to normal. Customers should see logs returning to normal.

Mar 27, 4:17 PM

identified

We continue to increase capacity in targeted areas to mitigate log ingestion degradation. It will take some time for the ingestion backlog to be eliminated.

Mar 27, 4:12 PM

identified

We have implemented increase capacity and logs are returning to normal. It will take some time for the ingestion backlog to be eliminated. Some services, such as realtime, storage, and api-gateway, will have lost logs during the ingestion incident.

Mar 27, 3:52 PM

identified

We have identified the issue with log ingestion. We are testing mitigation options, including bringing up additional capacity. We will continue to update this page with our progress.

Mar 27, 3:33 PM

investigating

We are investigating a problem with log ingestion. Users may experience delay in current log data.

Mar 27, 3:13 PM

Realtime services unavailable

major

Started: Mar 26, 11:41 PM

monitoring

The fix has been implemented and we’re monitoring to ensure stability.

Mar 27, 2:48 AM

identified

We appreciate your patience as we continue to work on a fix. We will provide updates as they become available.

Mar 27, 1:44 AM

identified

We are working on a fix and we’ll continue to provide updates as progress is made.

Mar 27, 1:13 AM

identified

We've identified the issue and are currently working on a fix, we will provide an update on our progress soon.

Mar 27, 12:46 AM

investigating

We're still investigating network connectivity issues with Realtime.

Mar 27, 12:20 AM

investigating

We are investigating network connectivity issues with Realtime.”

Mar 26, 11:41 PM

Branching access issues

minor

Started: Mar 24, 3:13 PM

monitoring

The fix has been implemented and branching access has returned to normal.

Mar 24, 3:27 PM

identified

We are aware of an issue affecting users creating/updating branches. A permission error in our branching workflow is causing failures for all branches. We have identified the root cause and a fix is being deployed. We will provide an update once resolved.

Mar 24, 3:13 PM

Degraded Logging Ingestion impacting all regions

minor

Started: Mar 23, 4:28 PM

monitoring

A fix has been implemented. The system is now operating normally, and we will continue to monitor.

Mar 23, 5:05 PM

identified

The cause of the issue has been identified. Our engineering team is working on a fix.

Mar 23, 4:38 PM

investigating

We are currently investigating an issue affecting Supabase Logs, resulting in partial log ingestion for some services. Users may experience delays or errors when accessing logs. In some cases, logs may be partially ingested or not ingested at all. Projects remain fully functional. This issue is limited to logging only. Our team is actively working to identify the root cause and restore normal performance as quickly as possible. We will provide further updates as more information becomes ava...

Mar 23, 4:28 PM

Elevated error rates affecting Edge Functions in the eu-central-1 (Frankfurt) region

minor

Started: Mar 23, 2:16 PM

monitoring

We carried out a controlled redeployment of the affected services to restore stability. The system is now operating normally, and we will continue to monitor.

Mar 23, 2:32 PM

investigating

We are currently investigating elevated error rates affecting Edge Functions in the eu-central-1 (Frankfurt) region

Mar 23, 2:16 PM

Project creation failures across multiple regions

major

Started: Mar 19, 8:55 PM

monitoring

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

Mar 19, 9:21 PM

identified

We have identified the issue and a fix is underway.

Mar 19, 9:08 PM

investigating

We are currently investigating project creation failures across multiple regions.

Mar 19, 8:55 PM

Elevated error rates affecting storage services in the ap-northeast-1 (Tokyo) region

minor

Started: Mar 18, 4:27 PM

identified

The root cause, involving task instances and batch sending events, has been identified. Our engineering team is working on a fix.

Mar 18, 5:53 PM

investigating

We are continuing to investigate elevated error rates affecting storage services in the ap-northeast-1 (Tokyo) region. While we are still observing a higher-than-normal level of errors, initial findings indicate that the overall impact is lower than first expected. Many affected requests are succeeding upon retry. Our team is actively working to determine the root cause and will provide further updates as more information becomes available.

Mar 18, 5:30 PM

investigating

We are continuing to investigate elevated error rates affecting storage services in the ap-northeast-1 (Tokyo) region. Newly created projects may still experience issues connecting to storage, while existing projects remain unaffected at this time. Our team is actively working to determine the root cause and assess the full impact. We will provide further updates as more information becomes available.

Mar 18, 4:58 PM

investigating

We are currently investigating elevated error rates affecting storage services in the ap-northeast-1 (Tokyo) region. Newly created projects may experience issues connecting to storage, while existing projects remain unaffected at this time. We are actively working to understand the full scope of the impact and will provide further updates as more information becomes available.

Mar 18, 4:27 PM

Issues propagating Postgres configuration updates

minor

Started: Mar 17, 4:50 AM

monitoring

A fix has been implemented and we are monitoring.

Mar 17, 7:07 AM

identified

We have identified the root cause and are currently working on a fix.

Mar 17, 5:11 AM

investigating

Some custom Postgres configurations applied through the Supabase CLI are not currently taking effect for projects running Postgres version 17.6.1.084. Projects that do not use CLI-managed Postgres configurations, or that are running earlier Postgres versions, are not affected.

Mar 17, 4:50 AM

Increased error rate related to Connection Pooler in ap-northeast-2 (South Korea)

minor

Started: Mar 13, 8:54 AM

monitoring

A fix has been implemented and error rates have reduced. Our team is actively monitoring the system to ensure stability.

Mar 13, 9:40 AM

investigating

We continue to investigate increased error rates relating to the connection pooler in ap-northeast-2 (South Korea) We will provide further updates as information becomes available.

Mar 13, 9:25 AM

investigating

We are currently investigating increased error rates relating to the connection pooler in ap-northeast-2 (South Korea) We will provide further updates as information becomes available.

Mar 13, 8:54 AM

Degraded Logging Ingestion impacting all regions

minor

Started: Mar 12, 12:51 PM

monitoring

A fix has been implemented and log ingestion is now stabilising. We are seeing recovery across the affected services. Our team is actively monitoring the system to ensure ingestion fully returns to normal.

Mar 12, 12:54 PM

investigating

We are currently investigating an issue affecting Supabase Logs that is causing partial log ingestion for some services. Users may experience delays or errors when accessing logs related to Realtime, Storage, or Edge Functions logs. The logs for these services may only be partially ingested. The services remain fully functional, this is only impacting logs. Postgres Logs are not impacted. Our team is actively working to identify the root cause and restore normal performance as quickly as...

Mar 12, 12:51 PM

View live status for Supabase Browse all services