Is Supabase down right now?

Partly: degraded performance

Degraded performance

Checked 5 min ago. In this state since 4 Nov 2026, 03:50 UTC. Source: status.supabase.com

Active incidents

Intermittent errors on Supavisor Shared Pooler in us-east-2

minormonitoring · started 4 Nov 2026, 03:48 UTC (31 min ago)

monitoring · 4 Nov 2026, 03:48 UTC

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"

Official update from status.supabase.com

Components

  • Connection Pooler · us-east-2Degraded performance
Show all 189 components
  • Branching · ap-east-1Operational
  • Branching · ap-northeast-1Operational
  • Branching · ap-northeast-2Operational
  • Branching · ap-south-1Operational
  • Branching · ap-southeast-1Operational
  • Branching · ap-southeast-2Operational
  • Branching · ca-central-1Operational
  • Branching · eu-central-1Operational
  • Branching · eu-central-2Operational
  • Branching · eu-north-1Operational
  • Branching · eu-west-1Operational
  • Branching · eu-west-2Operational
  • Branching · eu-west-3Operational
  • Branching · sa-east-1Operational
  • Branching · us-east-1Operational
  • Branching · us-east-2Operational
  • Branching · us-west-1Operational
  • Branching · us-west-2Operational
  • Connection Pooler · ap-east-1Operational
  • Connection Pooler · ap-northeast-1Operational
  • Connection Pooler · ap-northeast-2Operational
  • Connection Pooler · ap-south-1Operational
  • Connection Pooler · ap-southeast-1Operational
  • Connection Pooler · ap-southeast-2Operational
  • Connection Pooler · ca-central-1Operational
  • Connection Pooler · eu-central-1Operational
  • Connection Pooler · eu-central-2Operational
  • Connection Pooler · eu-north-1Operational
  • Connection Pooler · eu-west-1Operational
  • Connection Pooler · eu-west-2Operational
  • Connection Pooler · eu-west-3Operational
  • Connection Pooler · sa-east-1Operational
  • Connection Pooler · us-east-1Operational
  • Connection Pooler · us-east-2Degraded performance
  • Connection Pooler · us-west-1Operational
  • Connection Pooler · us-west-2Operational
  • Data APIs · ap-east-1Operational
  • Data APIs · ap-northeast-1Operational
  • Data APIs · ap-northeast-2Operational
  • Data APIs · ap-south-1Operational
  • Data APIs · ap-southeast-1Operational
  • Data APIs · ap-southeast-2Operational
  • Data APIs · ca-central-1Operational
  • Data APIs · eu-central-1Operational
  • Data APIs · eu-central-2Operational
  • Data APIs · eu-north-1Operational
  • Data APIs · eu-west-1Operational
  • Data APIs · eu-west-2Operational
  • Data APIs · eu-west-3Operational
  • Data APIs · sa-east-1Operational
  • Data APIs · us-east-1Operational
  • Data APIs · us-east-2Operational
  • Data APIs · us-west-1Operational
  • Data APIs · us-west-2Operational
  • Functions · ap-east-1Operational
  • Functions · ap-northeast-1Operational
  • Functions · ap-northeast-2Operational
  • Functions · ap-south-1Operational
  • Functions · ap-southeast-1Operational
  • Functions · ap-southeast-2Operational
  • Functions · ca-central-1Operational
  • Functions · eu-central-1Operational
  • Functions · eu-central-2Operational
  • Functions · eu-north-1Operational
  • Functions · eu-west-1Operational
  • Functions · eu-west-2Operational
  • Functions · eu-west-3Operational
  • Functions · sa-east-1Operational
  • Functions · us-east-1Operational
  • Functions · us-east-2Operational
  • Functions · us-west-1Operational
  • Functions · us-west-2Operational
  • Management API · ap-southeast-1Operational
  • Management API · eu-west-1Operational
  • Management API · us-east-1Operational
  • Management API · us-west-1Operational
  • Postgres · ap-east-1Operational
  • Postgres · ap-northeast-1Operational
  • Postgres · ap-northeast-2Operational
  • Postgres · ap-south-1Operational
  • Postgres · ap-southeast-1Operational
  • Postgres · ap-southeast-2Operational
  • Postgres · ca-central-1Operational
  • Postgres · eu-central-1Operational
  • Postgres · eu-central-2Operational
  • Postgres · eu-north-1Operational
  • Postgres · eu-west-1Operational
  • Postgres · eu-west-2Operational
  • Postgres · eu-west-3Operational
  • Postgres · sa-east-1Operational
  • Postgres · us-east-1Operational
  • Postgres · us-east-2Operational
  • Postgres · us-west-1Operational
  • Postgres · us-west-2Operational
  • Project Creation · ap-east-1Operational
  • Project Creation · ap-northeast-1Operational
  • Project Creation · ap-northeast-2Operational
  • Project Creation · ap-south-1Operational
  • Project Creation · ap-southeast-1Operational
  • Project Creation · ap-southeast-2Operational
  • Project Creation · ca-central-1Operational
  • Project Creation · eu-central-1Operational
  • Project Creation · eu-central-2Operational
  • Project Creation · eu-north-1Operational
  • Project Creation · eu-west-1Operational
  • Project Creation · eu-west-2Operational
  • Project Creation · eu-west-3Operational
  • Project Creation · sa-east-1Operational
  • Project Creation · us-east-1Operational
  • Project Creation · us-east-2Operational
  • Project Creation · us-west-1Operational
  • Project Creation · us-west-2Operational
  • Project Resize · ap-east-1Operational
  • Project Resize · ap-northeast-1Operational
  • Project Resize · ap-northeast-2Operational
  • Project Resize · ap-south-1Operational
  • Project Resize · ap-southeast-1Operational
  • Project Resize · ap-southeast-2Operational
  • Project Resize · ca-central-1Operational
  • Project Resize · eu-central-1Operational
  • Project Resize · eu-central-2Operational
  • Project Resize · eu-north-1Operational
  • Project Resize · eu-west-1Operational
  • Project Resize · eu-west-2Operational
  • Project Resize · eu-west-3Operational
  • Project Resize · sa-east-1Operational
  • Project Resize · us-east-1Operational
  • Project Resize · us-east-2Operational
  • Project Resize · us-west-1Operational
  • Project Resize · us-west-2Operational
  • Project Restore · ap-east-1Operational
  • Project Restore · ap-northeast-1Operational
  • Project Restore · ap-northeast-2Operational
  • Project Restore · ap-south-1Operational
  • Project Restore · ap-southeast-1Operational
  • Project Restore · ap-southeast-2Operational
  • Project Restore · ca-central-1Operational
  • Project Restore · eu-central-1Operational
  • Project Restore · eu-central-2Operational
  • Project Restore · eu-north-1Operational
  • Project Restore · eu-west-1Operational
  • Project Restore · eu-west-2Operational
  • Project Restore · eu-west-3Operational
  • Project Restore · sa-east-1Operational
  • Project Restore · us-east-1Operational
  • Project Restore · us-east-2Operational
  • Project Restore · us-west-1Operational
  • Project Restore · us-west-2Operational
  • Project Upgrades · ap-east-1Operational
  • Project Upgrades · ap-northeast-1Operational
  • Project Upgrades · ap-northeast-2Operational
  • Project Upgrades · ap-south-1Operational
  • Project Upgrades · ap-southeast-1Operational
  • Project Upgrades · ap-southeast-2Operational
  • Project Upgrades · ca-central-1Operational
  • Project Upgrades · eu-central-1Operational
  • Project Upgrades · eu-central-2Operational
  • Project Upgrades · eu-north-1Operational
  • Project Upgrades · eu-west-1Operational
  • Project Upgrades · eu-west-2Operational
  • Project Upgrades · eu-west-3Operational
  • Project Upgrades · sa-east-1Operational
  • Project Upgrades · us-east-1Operational
  • Project Upgrades · us-east-2Operational
  • Project Upgrades · us-west-1Operational
  • Project Upgrades · us-west-2Operational
  • Storage · ap-east-1Operational
  • Storage · ap-northeast-1Operational
  • Storage · ap-northeast-2Operational
  • Storage · ap-south-1Operational
  • Storage · ap-southeast-1Operational
  • Storage · ap-southeast-2Operational
  • Storage · ca-central-1Operational
  • Storage · eu-central-1Operational
  • Storage · eu-central-2Operational
  • Storage · eu-north-1Operational
  • Storage · eu-west-1Operational
  • Storage · eu-west-2Operational
  • Storage · eu-west-3Operational
  • Storage · sa-east-1Operational
  • Storage · us-east-1Operational
  • Storage · us-east-2Operational
  • Storage · us-west-1Operational
  • Storage · us-west-2Operational
  • AuthOperational
  • Billing & PaymentsOperational
  • DashboardOperational
  • Logging & ObservabilityOperational
  • RealtimeOperational

User reports

Having trouble with Supabase? Reports are anonymous and only counted, no cookies.

24 h ago0 reports in the last 24 hNow

Supabase uptime, last 90 days

2026-08-07: no data 2026-08-08: no data 2026-08-09: no data 2026-08-10: no data 2026-08-11: no data 2026-08-12: no data 2026-08-13: no data 2026-08-14: no data 2026-08-15: no data 2026-08-16: no data 2026-08-17: no data 2026-08-18: no data 2026-08-19: no data 2026-08-20: no data 2026-08-21: no data 2026-08-22: no data 2026-08-23: no data 2026-08-24: no data 2026-08-25: no data 2026-08-26: no data 2026-08-27: no data 2026-08-28: no data 2026-08-29: no data 2026-08-30: no data 2026-08-31: no data 2026-09-01: no data 2026-09-02: no data 2026-09-03: no data 2026-09-04: no data 2026-09-05: no data 2026-09-06: no data 2026-09-07: no data 2026-09-08: no data 2026-09-09: no data 2026-09-10: no data 2026-09-11: no data 2026-09-12: no data 2026-09-13: no data 2026-09-14: no data 2026-09-15: no data 2026-09-16: no data 2026-09-17: no data 2026-09-18: no data 2026-09-19: no data 2026-09-20: no data 2026-09-21: no data 2026-09-22: no data 2026-09-23: no data 2026-09-24: no data 2026-09-25: no data 2026-09-26: no data 2026-09-27: no data 2026-09-28: no data 2026-09-29: no data 2026-09-30: no data 2026-10-01: no data 2026-10-02: no data 2026-10-03: no data 2026-10-04: no data 2026-10-05: no data 2026-10-06: no data 2026-10-07: no data 2026-10-08: no data 2026-10-09: no data 2026-10-10: no data 2026-10-11: no data 2026-10-12: no data 2026-10-13: no data 2026-10-14: no data 2026-10-15: no data 2026-10-16: no data 2026-10-17: no data 2026-10-18: no data 2026-10-19: no data 2026-10-20: no data 2026-10-21: no data 2026-10-22: no data 2026-10-23: no data 2026-10-24: no data 2026-10-25: no data 2026-10-26: no data 2026-10-27: no data 2026-10-28: no data 2026-10-29: no data 2026-10-30: no data 2026-10-31: no data 2026-11-01: no data 2026-11-02: no data 2026-11-03: no data 2026-11-04: Degraded performance, ~30 min with issues
90 days ago97.92% uptime over 1 tracked dayToday

Each bar is one UTC day, coloured by the worst state we saw on the official status page.

Recent Supabase incidents

  • Management API Postgres config updates overwriting previous updates · 3 Nov 2026, 04:56 UTC · 2 h 8 min

    resolved · 3 Nov 2026, 07:04 UTC

    Connection Logging feature is working fine for all customers now.

    monitoring · 3 Nov 2026, 06:24 UTC

    A fix has been deployed, and the Connection Logging setting that was temporarily disabled on the dashboard is available again.

    monitoring · 3 Nov 2026, 06:17 UTC

    We have identified the cause and are deploying a fix. The dashboard setting that was temporarily disabled will soon be enabled again.

    investigating · 3 Nov 2026, 05:16 UTC

    We are actively correcting an issue with the Management API: • Postgres Config changes only save the latest values sent. Past changes are being overwritten For now, we have disabled making certain Postgres config changes on the dashboard until the issue is resolved.

    investigating · 3 Nov 2026, 04:56 UTC

    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)

    Read on status.supabase.com

  • Storage uploads failing in us-east-1 · 2 Nov 2026, 21:34 UTC · 1 h 14 min · minor

    resolved · 2 Nov 2026, 22:48 UTC

    Storage uploads have remained stable, and this issue is now resolved.

    monitoring · 2 Nov 2026, 22:23 UTC

    The fix has been implemented, and we are seeing Storage uploads return to normal. We will continue monitoring to ensure stability.

    identified · 2 Nov 2026, 21:48 UTC

    We have identified the issue causing Storage uploads to fail and are working on a fix. We will provide more updates as things progress.

    investigating · 2 Nov 2026, 21:34 UTC

    We are investigating an error with Storage uploads returning 5xx errors for us-east-1 users. We will be confirming more information shortly.

    Read on status.supabase.com

  • PG15 -> PG17 Upgrade Failures · 31 Oct 2026, 20:06 UTC · 1 h 8 min

    resolved · 31 Oct 2026, 21:14 UTC

    This issue is now resolved.

    monitoring · 31 Oct 2026, 20:42 UTC

    We are seeing successful upgrades again, and error rates have returned to normal levels. We will continue to monitor to ensure continued stability.

    identified · 31 Oct 2026, 20:06 UTC

    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.

    Read on status.supabase.com

  • Logs degraded in multiple regions · 30 Oct 2026, 11:38 UTC · 51 min

    resolved · 30 Oct 2026, 12:29 UTC

    We have deployed the fix for degraded logs, and smoke tests completed successfully at 12:20 UTC. Service is now operating normally. We apologise for the disruption

    monitoring · 30 Oct 2026, 12:11 UTC

    A fix has been deployed and we are now monitoring the log service. We'll post another update as soon as we have one.

    identified · 30 Oct 2026, 11:56 UTC

    We have identified the cause of the Logs degradation and a fix is being prepared. Other services remain unaffected. We'll post another update as soon as we have one.

    investigating · 30 Oct 2026, 11:38 UTC

    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.

    Read on status.supabase.com

  • Delayed Log Delivery from 14:10 - 15:30 UTC · 28 Oct 2026, 16:21 UTC · 53 min · minor

    resolved · 28 Oct 2026, 17:13 UTC

    This issue has been resolved and log delivery is operational again.

    monitoring · 28 Oct 2026, 16:21 UTC

    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.

    Read on status.supabase.com

  • Log Drain Issues · 22 Oct 2026, 18:03 UTC · 47 min · minor

    resolved · 22 Oct 2026, 18:50 UTC

    This issue is now resolved.

    monitoring · 22 Oct 2026, 18:22 UTC

    The rollback has restored log drains to normal operation. We will monitor for continued functionality.

    investigating · 22 Oct 2026, 18:03 UTC

    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.

    Read on status.supabase.com

  • Elevated Mgmt API Error Rates in Multiple Regions · 22 Oct 2026, 17:01 UTC · 4 days · minor

    resolved · 26 Oct 2026, 10:16 UTC

    This issue has been resolved and our response times are back to operational.

    monitoring · 23 Oct 2026, 10:54 UTC

    We have additional mitigations we will be deploying to reinforce the Management API. Updates will be forthcoming if anything changes that could impact customers.

    monitoring · 22 Oct 2026, 18:17 UTC

    We have additional mitigations we will be deploying to reinforce our backplane. We will leave this statuspage up and in Monitoring status until all mitigations are deployed. Updates will be forthcoming if anything changes that could impact customers.

    monitoring · 22 Oct 2026, 17:57 UTC

    The mitigations have managed the demand spike. We are monitoring for continued stability.

    identified · 22 Oct 2026, 17:28 UTC

    We have identified the issue as related to the demand on our backplane. We are implementing mitigations to scale and manage that demand.

    investigating · 22 Oct 2026, 17:01 UTC

    We have noticed issues with requests coming to our API gateway. We are investigating.

    Read on status.supabase.com

  • Elevated Mgmt API Error Rates in Multiple Regions · 22 Oct 2026, 11:29 UTC · 2 h 13 min · major

    resolved · 22 Oct 2026, 13:42 UTC

    Error rates and latency have remained at normal levels following the mitigation. This incident is now resolved.

    monitoring · 22 Oct 2026, 12:07 UTC

    A mitigation has been applied. Error rates and latency have returned to normal levels. We’re continuing to monitor to ensure sustained stability before resolving this incident.

    investigating · 22 Oct 2026, 11:32 UTC

    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. This is also causing logins to supabase.com to timeout.

    investigating · 22 Oct 2026, 11:29 UTC

    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.

    Read on status.supabase.com

  • Project lifecycle operation errors in the EU region · 22 Oct 2026, 03:53 UTC · 12 h 3 min · major

    resolved · 22 Oct 2026, 15:56 UTC

    Error rates have remained at normal levels following the mitigation. This incident is now resolved.

    monitoring · 22 Oct 2026, 09:15 UTC

    Error rates remain at normal levels. We’re continuing to monitor to confirm sustained stability before resolving this incident.

    monitoring · 22 Oct 2026, 03:53 UTC

    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.

    Read on status.supabase.com

  • Intermittent connection errors via the connection pooler in us-east-1 · 21 Oct 2026, 16:27 UTC

    resolved · 10 Oct 2026, 02:10 UTC

    Between 22:10 and 22:51 UTC on October 9, 2026, about 1% of new database connections made through the Shared Pooler (Supavisor) in us-east-1 failed with "Failed to connect to database" timeout errors. The cause of the failures was an incident at our cloud provider which affected network traffic between availability zones. Supabase Project databases were not affected, and connections that had already been open prior to the incident remained open. The issue was resolved at 22:51 UTC. Clients that retried on connection errors would have reconnected successfully.

    Read on status.supabase.com

  • Project lifecycle operations such as project creation, pausing, and restoration, in all regions · 21 Oct 2026, 15:36 UTC · 1 h 16 min · major

    resolved · 21 Oct 2026, 16:51 UTC

    The issue affecting project lifecycle operations, including project creation, pausing, and restoration, has been resolved. We have observed a reduction in project lifecycle job failures following the fix and confirmed that operations have returned to normal.

    monitoring · 21 Oct 2026, 16:12 UTC

    A fix has been applied, and we have observed a reduction in project lifecycle job failures. We are continuing to monitor the recovery to ensure normal operations remain stable.

    investigating · 21 Oct 2026, 15:36 UTC

    We are investigating an issue affecting project lifecycle operations such as project creation, pausing, and restoration, in all regions. We’ll provide further updates as more information becomes available.

    Read on status.supabase.com

  • Projects stuck in restarting state · 20 Oct 2026, 21:59 UTC · 7 h 41 min

    resolved · 21 Oct 2026, 05:39 UTC

    All affected projects have be fixed. We have not seen recurrence of the issue and we are resolving the incident.

    monitoring · 21 Oct 2026, 04:47 UTC

    The fix has fully rolled out. Projects are no longer stuck in a restarting state. We will continue to monitor the situation.

    identified · 21 Oct 2026, 02:48 UTC

    We continue with rolling out the fix to affected projects. No new projects are affected and we will provide further updates as the rollout progresses. Our next update will be in 2 hours.

    identified · 21 Oct 2026, 01:38 UTC

    We continue with rolling out the fix to affected projects. We will provide further updates as the rollout progresses.

    identified · 21 Oct 2026, 00:39 UTC

    We continue with rolling out the fix to affected projects. We will provide further updates as the rollout progresses.

    identified · 20 Oct 2026, 23:48 UTC

    We are rolling out a fix to affected projects. We will provide further updates as the rollout progresses.

    identified · 20 Oct 2026, 23:06 UTC

    We've identified the root cause of this issue and are working on a fix. We will continue to provide updates as things progress.

    investigating · 20 Oct 2026, 21:59 UTC

    Some projects in us-east-2 are stuck in restarting state. We are actively investigating this and will provide more updates as information becomes available.

    Read on status.supabase.com

  • Support Form Errors · 19 Oct 2026, 17:13 UTC · 1 h · minor

    resolved · 19 Oct 2026, 18:13 UTC

    Ticket creation has remained normal. We re resolving this incident.

    monitoring · 19 Oct 2026, 17:36 UTC

    The fix has been deployed and ticket creation has returned to normal. We will continue to monitor.

    identified · 19 Oct 2026, 17:13 UTC

    We have identified an issue with support ticket creation for some customers, we have a fix in development.

    Read on status.supabase.com

  • Project creation errors ap-ne1 · 17 Oct 2026, 06:27 UTC · 1 h 22 min · minor

    resolved · 17 Oct 2026, 07:49 UTC

    Service is fully restored and project creation and unpausing has been re-enabled in the ap-northeast-1 region.

    monitoring · 17 Oct 2026, 07:16 UTC

    Our upstream partner has confirmed the issue is resolved. We are working to restore project creation traffic back to the region and monitor for full recovery in ap-northeast-1.

    identified · 17 Oct 2026, 06:27 UTC

    Due to an ongoing upstream provider outage, we are remediating project creation errors in apne-1. Customers may see errors in creating or unpausing a project from this region. We are working to re-direct traffic to non-impacted regions and awaiting updates from our dependant provider.

    Read on status.supabase.com

  • Realtime latency · 12 Oct 2026, 22:59 UTC · 45 h 26 min · minor

    resolved · 14 Oct 2026, 20:25 UTC

    Realtime has fully recovered.

    monitoring · 14 Oct 2026, 03:00 UTC

    We have stabilised impacted users and enabled improvements to our Realtime infrastructure. We will continue to monitor for full recovery.

    identified · 13 Oct 2026, 23:27 UTC

    We’re seeing recovery for a large percentage of affected customers, though some issues remain in certain regions. We’re continuing to work on resolving the remaining issues and will share further updates as more information becomes available.

    identified · 13 Oct 2026, 21:15 UTC

    We’ve added extra capacity to the system and are currently testing it. We expect to begin stabilizing the affected clusters shortly. We’ll continue to share further updates as more information becomes available.

    identified · 13 Oct 2026, 17:34 UTC

    We are continuing to investigate increased Realtime latency and instability affecting the presence feature, which may impact join rates. Our team is actively working on mitigation and we will share another update as soon as more information becomes available.

    identified · 13 Oct 2026, 13:49 UTC

    We’re seeing increased Realtime latency and instability affecting the presence feature, which may impact join rates. This recurrence comes as we continue work on the remaining preventative measures. We are actively investigating and taking steps to mitigate the impact. We’ll share another update as soon as we have more information.

    monitoring · 13 Oct 2026, 06:38 UTC

    We have taken preventative steps to expand our realtime cluster capacity and are continuing to monitor our system stability for full recovery.

    monitoring · 13 Oct 2026, 00:02 UTC

    We have identified the cause and taken actions to remediate the high latency issues. We will continue to monitor.

    Read on status.supabase.com

Supabase is listed under Infrastructure. Status data comes from the official status page and is checked every 5 minutes.All AI service statuses

Updated