Access Issues From Some Providers in Brazil
Update - 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, 2026 - 22:30 UTC
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.98 % 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.87 % 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.96 % 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
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Scheduled Maintenance

Upgrade Shared Pooler V1 to V2 for eu-central-1 region May 26, 2026 13:00-15:00 UTC

Update - We will be undergoing scheduled maintenance during this time.
May 23, 2026 - 04:39 UTC
Scheduled - There will be a scheduled maintenance on 2026-05-26 from 13:00-15:00 UTC on the Shared Pooler(V1) for the eu-central-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-eu-central-1-pooler.supabase.com, you can expect to see errors during the maintenance.

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

Please follow the status page for updates.
May 18, 2026 - 02:49 UTC

Upgrade Shared Pooler V1 to V2 for us-west-1 region May 28, 2026 16:00-18:00 UTC

Update - We will be undergoing scheduled maintenance during this time.
May 22, 2026 - 15:54 UTC
Scheduled - There will be scheduled maintenance on 2026-06-02 from 16:00-18:00 UTC (09:00-11:00 PDT) on the Shared Pooler(V1) for the us-west-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-us-west-1-pooler.supabase.com, you can expect to see errors during the maintenance.

Those using connection strings with the format: aws-us-west-1.pooler.supabase.comare not affected by this maintenance.

Please follow the status page for updates.
May 18, 2026 - 02:55 UTC

Upgrade Shared Pooler V1 to V2 for eu-west-1 region Jun 1, 2026 13:00-15:00 UTC

There will be a scheduled maintenance on 2026-06-01 from 13:00-15:00 UTC on the Shared Pooler(V1) for the eu-west-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-eu-west-1-pooler.supabase.com, you can expect to see errors during the maintenance.

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

Please follow the status page for updates.
Posted on May 18, 2026 - 02:52 UTC

Upgrade Shared Pooler V1 to V2 for us-east-1 region Jun 1, 2026 13:00-15:00 UTC

There will be scheduled maintenance on 2026-06-03 from 13:00-15:00 UTC (09:00-11:00 EDT) on the Shared Pooler(V1) for the us-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-us-east-1-pooler.supabase.com, you can expect to see errors during the maintenance.

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

Please follow the status page for updates.
Posted on May 18, 2026 - 02:57 UTC
System Metrics Month Week Day
REST API Latency (Singapore)
Fetching
REST API Latency (North Virginia)
Fetching
REST API Latency (Frankfurt)
Fetching
May 24, 2026

No incidents reported today.

May 23, 2026

No incidents reported.

May 22, 2026

No incidents reported.

May 21, 2026
Branch creation degradation
Resolved - Branch creation continues to be stable.
May 21, 19:26 UTC
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, 18:54 UTC
Update - We continue investigating different possible underlying causes and will provide updates as progress is made.
May 21, 17:45 UTC
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, 16:46 UTC
Login issues for SSO and Email accounts on Supabase Dashboard
Resolved - The issue affecting SSO logins has now been resolved.
Thank you for your patience while we worked through this issue.
May 21, 10:51 UTC
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, 09:43 UTC
Update - A fix has been implemented and is currently being rolled out. We will continue to provide updates as the deployment progresses.
May 21, 09:26 UTC
Identified - We have identified the issue as being related to a recent key rotation and are currently working on a fix.
May 21, 08:49 UTC
Update - 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, 08:33 UTC
Investigating - Users that are already logged in are not affected.
May 21, 08:30 UTC
Network restrictions preventing read replica communication
Resolved - Communication between read replicas and their primaries for impacted projects has been restored. This incident is now resolved.
May 21, 04:44 UTC
Monitoring - We have merged the fix and are monitoring for stability.
May 21, 04:23 UTC
Update - We have developed a fix and it is currently being validated. We will provide more updates soon.
May 21, 03:49 UTC
Update - Our team continues to work on implementing a fix for the issue. We will provide additional updates as progress is made.
May 21, 01:12 UTC
Update - 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, 23:41 UTC
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, 22:48 UTC
Update - 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, 21:46 UTC
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, 21:04 UTC
May 20, 2026
Paused Projects Showing Incorrect Resume Deadline
Resolved - The UI message incident has been resolved.
May 20, 19:41 UTC
Monitoring - This change has been reverted. We are monitoring to ensure things remain stable.
May 20, 19:11 UTC
Update - The revert of the change is in process.
May 20, 17:41 UTC
Identified - We’ve isolated the cause of the issue to a recent change and are working on reverting it now.
May 20, 16:17 UTC
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 be available for download.”

Please note this is a display issue only. Projects paused within the last 90 days can still be resumed successfully.
All project data, including backups and storage objects, remains safe and unaffected.
May 20, 15:40 UTC
May 19, 2026
Log ingestion issues
Resolved - This incident has been resolved, and log delivery has returned to normal.

During the incident, some logs may have been delayed or unavailable. While some upstream sources may retry delivery automatically, we cannot guarantee recovery of all missing logs from the affected period.

Thank you for your patience while we worked to resolve this.
May 19, 00:10 UTC
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, 23:58 UTC
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, 23:26 UTC
May 18, 2026
May 17, 2026

No incidents reported.

May 16, 2026

No incidents reported.

May 15, 2026
Auth Service Update
Resolved - All changes hav been applied.
May 15, 19:18 UTC
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, 18:47 UTC
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, 18:11 UTC
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.

← Incident History Powered by Atlassian Statuspage