Supabase Status

Access Issues From Some Providers in Brazil

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, 2026 - 22:23 UTC

Update - 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, 2026 - 16:37 UTC

Update - 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, 2026 - 15:54 UTC

Investigating - We are investigating reports of some access issues to Supabase IP addresses from a network provider in Brazil.
May 14, 2026 - 15:34 UTC

Uptime over the past 90 days. View historical uptime.

Compute capacity Operational

ap-northeast-1 Operational

ap-northeast-2 Operational

ap-south-1 Operational

ap-southeast-1 Operational

ap-southeast-2 Operational

ca-central-1 Operational

eu-central-1 Operational

eu-central-2 Operational

eu-north-1 Operational

eu-west-1 Operational

eu-west-2 Operational

eu-west-3 Operational

sa-east-1 Operational

us-east-1 Operational

us-east-2 Operational

us-west-1 Operational

Analytics Operational

90 days ago

99.95 % uptime

Today

API Gateway Operational

90 days ago

99.9 % uptime

Today

Auth Operational

90 days ago

99.84 % uptime

Today

Connection Pooler Operational

90 days ago

99.98 % uptime

Today

Dashboard Operational

90 days ago

99.83 % uptime

Today

Database Operational

90 days ago

99.8 % uptime

Today

Edge Functions Operational

90 days ago

99.85 % uptime

Today

Management API Operational

90 days ago

99.93 % uptime

Today

Realtime Operational

90 days ago

99.92 % uptime

Today

Storage Operational

90 days ago

99.92 % uptime

Today

Operational

Degraded Performance

Partial Outage

Major Outage

Maintenance

System Metrics Month Week Day

REST API Latency (Singapore)

Fetching

REST API Latency (North Virginia)

Fetching

REST API Latency (Frankfurt)

Fetching

Past Incidents

May 15, 2026

No incidents reported today.

May 14, 2026

Shared Pooler scheduled maintenance in sa-east-1

Completed - The scheduled maintenance has been completed.
May 14, 20:00 UTC

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 14, 18:00 UTC

Scheduled - There will be scheduled maintenance on May 14 from 18:00-20:00 UTC (15:00-17:00 BRT) on the Shared Pooler(V1) for the sa-east-1 region.

This maintenance upgrades the Shared Pooler to a new version (V2) that provides better scalability and uptime.

The Shared Pooler will be unavailable during this time period for anyone connecting to their projects using it. Your projects remain available and connections via the Dedicated Pooler and Direct Connections will continue to work.

How to determine whether you are affected:

Only projects connecting to V1 of the Shared Pooler are affected. If your connection string has the format:

aws-0-sa-east-1.pooler.supabase.com, you can expect to see errors during the maintenance.

Those using connection strings with the format: aws-1-sa-east-1.pooler.supabase.com are not affected by this maintenance.

Please follow the status page for updates.
May 7, 22:16 UTC

May 13, 2026

Edge Traffic Issues

Resolved - We've determined that the connectivity issues are isolated to users accessing Supabase through Mullvad VPN and potentially other VPN providers. The root cause appears to be network disruptions involving a specific colocation/transit provider used by Mullvad, rather than an issue with Supabase or Cloudflare infrastructure.

We've reached out to Mullvad support, but as this is dependent on external providers, there are no further mitigation steps we can take internally. Users experiencing issues are advised to avoid affected VPN networks or contact their VPN provider directly for support.

The incident is now resolved
May 13, 20:35 UTC

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, 19:50 UTC

Update - 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, 17:31 UTC

Update - 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, 16:46 UTC

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, 16:15 UTC

Shared Pooler scheduled maintenance in ap-southeast-1

Completed - The scheduled maintenance has been completed.
May 13, 09:00 UTC

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 13, 07:00 UTC

Scheduled - There will be scheduled maintenance on May 13 from 7:00-9:00 UTC (15:00-17:00 SGT) on the Shared Pooler(V1) for the ap-southeast-1 region.

This maintenance upgrades the Shared Pooler to a new version (V2) that provides better scalability and uptime.

The Shared Pooler will be unavailable during this time period for anyone connecting to their projects using it. Your projects remain available and connections via the Dedicated Pooler and Direct Connections will continue to work.

How to determine whether you are affected:

Only projects connecting to V1 of the Shared Pooler are affected. If your connection string has the format:

aws-0-ap-southeast-1.pooler.supabase.com, you can expect to see errors during the maintenance.

Those using connection strings with the format: aws-1-ap-southeast-1.pooler.supabase.com are not affected by this maintenance.

Please follow the status page for updates.
May 7, 22:13 UTC

May 12, 2026

No incidents reported.

May 11, 2026

No incidents reported.

May 10, 2026

No incidents reported.

May 9, 2026

Network connectivity in us-east-1-az4

Resolved - Recovery efforts are completed and this incident is now resolved. Thank you for your patience throughout this incident.
May 9, 04:49 UTC

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, 04:34 UTC

Update - 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 progresses.
May 9, 04:10 UTC

Update - 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 updates as more information becomes available.
May 9, 01:32 UTC

Update - 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 UTC

Update - 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 UTC

Update - Affected projects are continuing to recover. We are monitoring the recovery of the AZ and will provide regular updates until full recovery.
May 8, 07:59 UTC

Update - Affected projects are continuing to recover. We are monitoring the recovery of the AZ and will provide regular updates until full recovery.
May 8, 06:44 UTC

Update - 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, 05:31 UTC

Update - We are continuing to work on a fix for this issue.
May 8, 05:30 UTC

Update - We are continuing to work on a fix for this issue.
May 8, 04:21 UTC

Update - 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, 03:11 UTC

Update - We have disabled project creation in us-east-1. We will provide another update in an hour, if not sooner.
May 8, 02:30 UTC

Update - We are waiting on a resolution from our upstream provider. We will provide an update in an hour.
May 8, 02:05 UTC

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, 01:06 UTC

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

May 8, 2026

Customer Projects Experiencing Upgrade Issues

Resolved - Upgrade operations have returned to normal.
May 8, 16:13 UTC

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, 14:39 UTC

Update - 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 resolved.
We will continue to provide updates as information becomes available.
May 8, 13:46 UTC

Update - We are continuing to work on a fix for this issue.
May 8, 13:26 UTC

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, 13:25 UTC

May 7, 2026

No incidents reported.

May 6, 2026

No incidents reported.

May 5, 2026

Dashboard and Management API maintenance

Completed - The scheduled maintenance has now been completed.
May 5, 14:56 UTC

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 5, 14:00 UTC

Update - We have postponed this maintenance to Tuesday, May 5 1400-1500 UTC.
Apr 29, 13:27 UTC

Scheduled - We will be carrying out scheduled database migrations on our Management API on Wednesday, April 29, 2026 between 14:00 to 15:00 UTC.

Existing customer projects will not be affected and will continue to operate normally. During the maintenance period, all write activity from our API, Dashboard and CLI, such as project creation or configuration updates, will be delayed and may time out. You can retry on timeout. Read activity across our Management API will remain unaffected.
Apr 28, 09:27 UTC

May 4, 2026

Edge Functions scheduled maintenance in eu-central-1 and us-east-1

Completed - The scheduled maintenance has been completed.
May 4, 05:00 UTC

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 4, 04:00 UTC

Scheduled - Upstream provider regular scheduled maintenance on instances in us-east-1 and eu-central-1. We do not expect downtime or impact to Edge Functions invocations or deploys during this window. We will monitor and update its progress.
May 1, 17:18 UTC

May 3, 2026

Supavisor connectivity in eu-central-1

Resolved - From 15:30 to 7:00 UTC, for projects in eu-central-1, a Supavisor node experienced connectivity issues and was not able to connect to customer databases, causing checkout timeouts and auth query failed errors.

This has been resolved and Supavisor is fully available.
May 3, 22:30 UTC

May 2, 2026

No incidents reported.

May 1, 2026

No incidents reported.

Related

Past Incidents