New Multi-region uptime checks and custom-domain status pages

Supabase Outage History

Daily provider-status observations and published incident history for Supabase.

Operational

Supabase is operational. Verified . Official provider source.

Looking for an update now? Check the current status, or follow Supabase for future changes.

12.2% of 49 verified observed days had no reported provider issue

90-Day Trend

Jul 15Oct 12

Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.

Monthly Status Summary

Month Issue-free days Days Tracked Days with issues
September 2026 0% 30 30

This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.

Recorded Daily Status (Last 91 Days)

Jul 14 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

September 2026
Project creations are degraded in multiple regions
minor Observed active window 31m

View incident details and source

Started:

monitoring
We have identified increased latency in Project creations in these regions from 0730 UTC to 0805 UTC: ap-northeast-1 ap-northeast-2 eu-central-1 eu-central-2 eu-north-1 eu-west-1 eu-west-3 us-west-1 The latency has since recovered and our teams are monitoring for full recovery. Existing project availability has not been impacted.
Project Lifecycle Activity Degradation
major Observed active window 2h 2m

View incident details and source

Started:

Database Management API
monitoring
Project lifecycle operations have remained stable. We will continue to monitor the platform.
investigating
We are observing recovery in project lifecycle operations. Our team is investigating the root cause and actively working to prevent recurrence.
investigating
We are experiencing degradation of project lifecycle activities. We are investigating.
Query slowness for projects running Postgres version 14 in us-east-1 and ap-northeast-2
minor Observed active window 2h 46m

View incident details and source

Started:

monitoring
The fix has been rolled out to us-east-1. We will continue to monitor both regions for stability.
identified
The fix has been implemented for ap-northeast-2 and we're working on implementing the fix for us-east-1. We will continue to provide updates as progress is made.
identified
We are continuing to work on a fix and will provide updates as things progress.
identified
Projects running Postgres version 14 in us-east-1 and ap-northeast-2 may experience query slowness. We've identified the cause and are working on a fix.
Edge Function Latency
minor Observed active window 3h 5m

View incident details and source

Started:

monitoring
Error rates have returned to normal, and the service is operating as expected. The team continues to investigate the underlying cause of the latency and spike in 503 errors.
investigating
We are investigating reports of increased Edge Function latency and elevated rates of HTTP 503 responses, beginning at approximately 06:00 UTC. Our team is working to identify the cause and will provide further updates as they become available.
Auth Service Outage
minor Observed active window 2h 17m

View incident details and source

Started:

Auth
monitoring
We implemented a fix and are monitoring the system.
identified
We have identified a subset of projects with a failing Auth service. Our team is working to remediate the issue.
identified
We have identified an issue related to the Auth service on some projects. We are actively working on a fix.
Unresponsive Projects
major Observed active window 27h 43m

View incident details and source

Started:

Database
monitoring
We have rolled out a fix across all regions and are continuing to monitor over the next few hours. Due to this incident, impacted users who's project were compute constrained would have received a 'Your Supabase Project <Name> is running out of Disk IO Budget' email which is no longer valid. No further action is required and your project availability should be restored to normal.
monitoring
We have rolled out a fix across all regions and are continuing to monitor over the next few hours. Users still affected by project outages are encouraged to restart their projects which has shown to resolve lasting errors.
identified
We have rolled out a version of the fix across all regions that will prevent recurrence of the issue. Users still affected by project outages are encouraged to restart their projects.
identified
Fix rollouts have been successful in the initial regions, we are proceeding to roll out the fix globally.
identified
A refined fix is being rolled out to specific regions, we are assessing the impact of the fix.
identified
We have identified why projects are becoming unresponsive and are implementing a mitigation.
investigating
We are aware of Nano projects becoming unresponsive after a period of time, typically hours. We are investigating.
Project Lifecycle Actions Showing increased error rates across all regions
critical Observed active window 8h 4m

View incident details and source

Started:

Management API
monitoring
Lifecycle operations have been re-enabled for 100% of users and error rates have returned to normal. We are going to monitor to ensure that things stay stable. The team is working through any remaining projects which did not automatically resolve. Some users may also notice that backups will happen a bit later than usual, but these jobs are running and completing normally.
identified
We've increased project lifecycle operations to 50% of users and things are holding steady. We're continuing to ramp this up until operations are restored for all users. This is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc. Running projects remain running, and the data APIs and direct postgres client connections are NOT affected.
identified
Error rates have returned to normal, and the backlogs are draining well. We are beginning to slowly re-enable lifecycle operations for users. We will be monitoring impact, and we hope to have this re-enabled everywhere soon. We will leave this in this state until lifecycle operations have been completely restored. Running projects remain running, and the data APIs and direct postgres client connections are NOT affected.
identified
We are seeing incremental improvements internally. There is a large backlog of actions that we are working through, but things are progressing. Once we make it through most of the backlog, we will re-enable lifecycle actions. This is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc. Running projects remain running, and the data APIs and direct postgres client connections are NOT affected.
identified
The team is continuing to work on restoring project lifecycle operations. Out of caution, we have disabled lifecycle operations. This is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc. Running projects remain running, and the data APIs and direct postgres client connections are NOT affected. We will provide additional updates as we have more information.
identified
The team has applied a fix, but error rates remain high. We are continuing to work and will take other necessary steps to resolve this as soon as possible. Running projects remain running, and the data APIs and direct postgres client connections are NOT affected. Out of an abundance of caution, we would suggest against taking any of these actions until this incident is resolved: Creates, Configuration changes, Restarts, or Compute size changes. We will provide additional updates as we have ...
identified
We have identified the source of the errors with project lifecycle actions, and the team is currently working to resolve it. This is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc. Running projects remain running, and the data APIs and direct postgres client connections are NOT affected. Out of an abundance of caution, we would suggest against taking any of these actions until this incident is resolved. We will provid...
investigating
We are seeing increased error rates in actions across all project lifecycle actions - Creations, Deletions, Restores, Configuration and Compute size upgrades. We are currently looking into the cause. Out of an abundance of caution, we would suggest against taking any of these actions until this incident is resolved. We will provide additional updates as we have more information
User unable to log in to Supabase Dashboard
critical Observed active window 1h 49m

View incident details and source

Started:

Dashboard
monitoring
A recent change affected users ability to log in to the Supabase Dashboard. We’ve reverted the change, and testing indicates that the issue is resolved. Please try logging in again. If you’re still unable to log in, perform a full browser refresh and retry. Projects and non-Dashboard traffic remained unaffected.
investigating
We’re investigating an issue preventing users from logging in to the Supabase Dashboard. Users who were logged into the dashboard were logged out. Dashboard actions are currently not available. Projects remain online and available. Non-Dashboard traffic is not impacted. We’ll share another update as soon as we have more information.
investigating
We are currently investigating an issue where users are unable to login to the Supabase dashboard
August 2026
Project Creation Failures
major Observed active window 2h 41m

View incident details and source

Started:

Database
monitoring
Project creation is reporting as recovered across the platform. We will monitor for stability in the near term.
identified
We are seeing the mitigation steps having the desired effect. Project creation is recovering.
investigating
While the first set of actions are taking effect, we are implementing a second set of likely mitigations to attempt to facilitate improvement in project creation.
investigating
We continue to work this issue. The steps we have taken are addressing the hypothesized cause of the issue. We are implementing further related mitigations.
investigating
We have a working hypothesis on the cause of the issue, and are implementing steps to try to improve project creation performance.
investigating
Project creation is failing for new projects on the platform. We are investigating.
Increased response times for requests
major Observed active window 94h 39m

View incident details and source

Started:

monitoring
Response times have recovered in all regions. We will continue to monitor throughout the weekend.
monitoring
The rollout has been completed in all regions. We will continue to monitor.
identified
The roll out has also been completed for us-east-1.
identified
PostgREST 14.5 has been deployed since 12:00pm UTC to all AP regions: ap-east-1, ap-northeast-1, ap-northeast-2, ap-south-1, ap-southeast-1, and ap-southeast-2 as well as sa-east-1 and ca-central-1, eu-central-1, eu-central-2, eu-north-1, eu-west-2, and eu-west-3, us-west-1 We'll continue to provide updates as we roll out the change for the remaining impacted regions.
identified
We are continuing to work through the remediation plan for the latency issues. We will provide a further update as soon as more information is available.
identified
The team has identified the change which resulted in additional latency and error rates for some data API Requests. They are preparing to roll this change back. This rollout will take some time, and we will update again as there is news on the progress of the fix.
investigating
We are continuing to investigate this issue and we’ll share more information as soon as it becomes available.
investigating
We are continuing to investigate this issue and we’ll share more information as soon as it becomes available.
investigating
We’re continuing to investigate the issue causing increased response times for requests and 525 errors. Our team remains actively engaged in the investigation, we’ll provide another update as soon as we have more details.
investigating
We’re currently investigating latency issue that may cause increased response times for a small percentage of requests. In some cases, this may also result in 525 errors. Our team is actively working to resolve the issue. We’ll share another update as soon as we have more information.

Legacy Incident Archive

80 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.

May 2026
Network restrictions preventing read replica communication
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
We have merged the fix and are monitoring for stability.
identified
We have developed a fix and it is currently being validated. We will provide more updates soon.
identified
Our team continues to work on implementing a fix for the issue. We will provide additional updates as progress is made.
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.
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.
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.
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.
Paused Projects Showing Incorrect Resume Deadline
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
This change has been reverted. We are monitoring to ensure things remain stable.
identified
The revert of the change is in process.
identified
We’ve isolated the cause of the issue to a recent change and are working on reverting it now.
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...
Log ingestion issues
minor Source not attested
Last archived state: resolved
View archived record details
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.
investigating
Customers may experience delayed log ingestion or periods where logs are unavailable. We will provide updates while we work to resolve the issue.
Auth Service Update
Source not attested
Last archived state: resolved
View archived record details
monitoring
The update has been implemented. Service changes can be made. We will monitor the effect for the next 30 minutes to ensure stability.
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.
Access Issues From Some Providers in Brazil
Source not attested
Last archived state: resolved
View archived record details
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.
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.
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.
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.
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.
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.
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.
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.
investigating
We are investigating reports of some access issues to Supabase IP addresses from a network provider in Brazil.
Reports of issues connecting to API Endpoints
minor Source not attested
Last archived state: resolved
View archived record details
investigating
We are investigating reports of connectivity issues to project API endpoints.
Edge Traffic Issues
minor Source not attested
Last archived state: resolved
View archived record details
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.
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.
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.
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.
Customer Projects Experiencing Upgrade Issues
minor Source not attested
Last archived state: resolved
View archived record details
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.
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...
identified
We are continuing to work on a fix for this issue.
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.
Network connectivity in us-east-1-az4
major Source not attested
Last archived state: resolved
View archived record details
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.
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...
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...
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...
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.
identified
Affected projects are continuing to recover. We are monitoring the recovery of the AZ and will provide regular updates until full recovery.
identified
Affected projects are continuing to recover. We are monitoring the recovery of the AZ and will provide regular updates until full recovery.
identified
Affected projects are continuing to recover. We are monitoring the recovery of the AZ and will provide regular updates until full recovery.
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.
identified
We are continuing to work on a fix for this issue.
identified
We are continuing to work on a fix for this issue.
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.
identified
We have disabled project creation in us-east-1. We will provide another update in an hour, if not sooner.
identified
We are waiting on a resolution from our upstream provider. We will provide an update in an hour.
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.
investigating
Increased connection times for Supavisor since about 00:10 UTC is affecting a limited number of projects in us-east-1
April 2026
403 errors for PostgREST requests
major Source not attested
Last archived state: resolved
View archived record details
monitoring
The exceptions fix has been rolled out, and we are monitoring for continued stability.
identified
We are continuing to work on a fix. We’ll share further updates as progress is made.
identified
We are continuing to work on a fix for this issue.
identified
The issue has been identified and we are working on a fix.
investigating
We are investigating 403 errors for PostgREST requests across multiple regions.
Get alerts for Supabase Subscribe to the provider incident feed Browse all services