Service status

Supabase status

Is Supabase down? This is Supabase’s current status, its components and its recent incidents, read from Supabase’s official status page and refreshed every 2 minutes.

All Systems Operational

As reported by Supabase’s status page, read Nov 15, 2026, 08:05 UTC.

Scheduled maintenance

  • Scheduled maintenance: Shared Pooler (Supavisor), eu-central-2 · Nov 13, 2026, 13:36 UTC · scheduled, maintenance impact

Components

Supabase components and their status
ComponentStatus
ap-east-1Operational

What a degraded performance status means, and how much downtime an SLA allows: the uptime calculator.

Recent Supabase incidents

  • Database Connection Errors · Nov 12, 2026, 20:35 UTC · resolved, minor impact, lasted 3 h 4 min

    The issue has been resolved, and services across all affected regions have recovered. We are no longer observing elevated connection errors and will close this incident.

  • Elevated Error rates for All Supabase project APIs · Nov 12, 2026, 22:13 UTC · resolved, minor impact, lasted 1 h 18 min

    This issue has been resolved. All API routes are operating normally, and we are no longer observing elevated error rates.

  • Storage request degradation in eu-west-1 · Nov 12, 2026, 14:48 UTC · resolved, minor impact, lasted 8 min

    We have mitigated the issue with the Storage service and we have not observed any further issues during our monitoring period. We consider this incident to be resolved.

  • Project Lifecycle Issues in ap-northeast-1 · Nov 11, 2026, 16:44 UTC · resolved, minor impact, lasted 4 h 48 min

    All operations have returned to normal and have remained stable.

  • Interruption in connections to Supavisor in eu-west-2 · Nov 8, 2026, 10:53 UTC · resolved, lasted 1 h 42 min

    The interruption to Supavisor connections in eu-west-2 has been resolved. Monitoring has confirmed that systems have recovered and connections are operating normally.

  • Increased Errors with Project Lifecycle Operations in US-West-2 · Nov 6, 2026, 23:49 UTC · resolved, minor impact, lasted 2 h 28 min

    The upstream provider incident has been resolved, and Project Lifecycle operations in US-West-2 have recovered. All operations are functioning normally, and we are marking this incident as resolved.

  • Intermittent 502/503 errors for pg_net calls to Edge Functions · Nov 5, 2026, 23:12 UTC · resolved, minor impact, lasted 42 min

    The issue has been resolved, and pg_net calls to Edge Functions in ap-southeast-1 are now operating normally.

  • Storage issues in us-east-1 and eu-central-1 · Nov 4, 2026, 18:43 UTC · resolved, minor impact, lasted 16 h 18 min

    The incident has been resolved.

  • Intermittent errors on Supavisor Shared Pooler in us-east-2 · Nov 4, 2026, 03:48 UTC · resolved, minor impact, lasted 29 min

    Errors have subsided and connections are back to normal.

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

    Connection Logging feature is working fine for all customers now.

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

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

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

    This issue is now resolved.

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

    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

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

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

  • Elevated Mgmt API Error Rates in Multiple Regions · Oct 22, 2026, 17:01 UTC · resolved, minor impact, lasted 89 h 15 min

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

Source: Supabase, Supabase’s public status page, read Nov 15, 2026, 08:05 UTC. Uptimely is not affiliated with Supabase; incident text is Supabase’s own.

Is it down for you, or for everyone?

A status page shows what the vendor has confirmed, which often lags what users see. Run a live check of supabase.com to see whether it answers right now.

Get alerted when Supabase has an incident

Uptimely’s External Status Page monitor watches Supabase’s status page and alerts your team by email, SMS, phone call, Slack, Discord or browser push when it reports a problem, next to the monitors for your own services.

Watch Supabase free →

Status of similar services

Every service status we track

Is Supabase down right now?

The status at the top of this page is Supabase's own, read from its public status page every couple of minutes. It shows what Supabase's team has confirmed. For an independent check of whether supabase.com answers right now, use the live check on the is-it-down page.

Where is Supabase's official status page?

Supabase publishes its status at https://status.supabase.com. This page shows the same data with the recent incident history in one place, and links each incident to Supabase's own write-up.

Why does Supabase not work for me when its status says operational?

A status page lists the incidents a vendor has confirmed, and confirmation takes time: problems often reach users minutes before they reach the status page, and some partial or regional problems never appear on it. Your own network, account or region can also be the cause.

How can I get alerted when Supabase has an incident?

Add an External Status Page monitor in Uptimely pointed at https://status.supabase.com. It reads the page on a schedule and alerts your team by email, SMS, phone call, Slack, Discord or browser push when Supabase reports a problem, beside the monitors for your own services.

Verified by the Uptimely team.