Status: investigating
EC2 scheduled events are timing out for projects in sa-east-1, leading to a subset of projects being reported as unhealthy in the Dashboard.
As a workaround, impacted users can re-start their project while we are working on providing a fix.
Status: investigating
We are currently seeing slightly increased error rates for API requests to the Data APIs, Auth, Storage, and other HTTP API routes across all regions
The team is currently investigating.
Status: monitoring
Between 14:14-14:18 UTC and 14:25-14:29, Storage requests may have been slow or aborted in the eu-west-1 region. This issue has been resolved and we do not expect recurrence. We are monitoring the region.
Status: investigating
Project lifecycle operations have been impacted by an issue in ap-northeast-1. We are investigating along with our upstream provider.
Status: monitoring
We detected an interruption in connections to Supavisor in eu-west-2 between 09:42 and 09:52 GMT which may have affected connections for some users. This has since been resolved and we are monitoring to ensure all systems have fully recovered.
Status: identified
All Project Lifecycle operations are currently impacted by an upstream provider incident affecting EC2 instances in US-West-2.
Currently up and active projects are unaffected and remain healthy. New project creation, unpauses, restore actions, project size changes, restarts and other lifecycle operations may encounter errors.
We advise against taking these actions in US-West-2 at this time while we work with our provider to resolve this issue.
Status: investigating
We are seeing intermittent 502 and 503 errors affecting Edge Functions requests in ap-southeast-1. We will provide updates and more information becomes available.
Status: investigating
We have identified some customers in us-east-1 are experiencing 5XX errors when interacting with our Storage components. We are investigating.
Status: monitoring
Between 2026-11-04 00:02 and 00:50 UTC there were elevated errors on Supavisor Shared Pooler in the us-east-2 region. Errors have subsided and things are back to normal.
Example errors were
```
ClientHandler: (ECHECKOUTFAILED) checkout failed due to %{"C" => "08006", "M" => "Failed to connect to database: {:error, :timeout}
DbHandler: Connection failed {:error, :timeout} to ~c".......us-east-2.compute.internal"
```
Status: investigating
We are actively correcting an issue with the Management API:
• Postgres Config changes only save the latest values sent, past changes are not being saved
For now please refrain from not making any Postgres Config changes via the [Management API](https://supabase.com/docs/reference/api/introduction) or in the [Database Settings Dashboard](https://supabase.com/dashboard/project/\_/database/settings)
Status: investigating
We are investigating an error with Storage uploads returning 5xx errors for us-east-1 users. We will be confirming more information shortly.
Status: identified
We are actively investigating some reports of failed PG15 -> PG17 upgrades. We have identified an error in an AMI release from today and are rolling it back to unblock upgrades.
Status: investigating
We are currently investigating degraded Logs functionality in multiple regions. Some users may experience delayed, missing, or unavailable logs in the Dashboard and Logs API.
Other services, including your database and APIs, are not affected at this time.
Our team is actively investigating. We'll post another update as soon as we have one.
Status: monitoring
Between 14:10 - 15:30 UTC we have experienced an issue in delivering logs, leading to a delay of about 7–8 minutes. Most affected events have now been recovered - a small subset of events is still being re-inserted and we will confirm once completed.
Status: investigating
Customers using log drains in some regions may be missing some routed logs for a subset of components. We've rolled back changes and are continuing to investigate.
Status: investigating
We are investigating elevated error rates and increased response times on the Management API across multiple regions. Some operations that depend on it, such as creating new projects, may fail or be slow.
Status: monitoring
We identified increased error rates in project lifecycle operations (create, restore, pauses, etc.) in the EU region since 21 Oct 23:00 UTC. A mitigation has been put in place and error rates have reduced to normal levels. We are monitoring the situation and are working on fixing affected projects.
Duration: 12h 3mVendor update 28 days ago
Incident community checkThis incident
21 incidents visible (ongoing and monitoring). A free account unlocks resolved history and filters.