Is Supabase down? › Outage history

Supabase outage history

Supabase published 32 incidents on its official status page since Aug 28, 2026, 3 of them rated at the highest impact level. 9 were major or long incidents with their own pages; the biggest are listed first. Below them is every smaller incident, then our own 90 day check history.

Biggest Supabase outages

Ranked by the official impact level, then by how long they lasted. Each has its own page with the cause, the fix time and every official update.

  1. Sep 4, 2026: Project Lifecycle Actions Showing increased error rates across all regions 7 hours 11 min · rated "Critical"
  2. Sep 1, 2026: User unable to log in to Supabase Dashboard 1 hour 28 min · rated "Critical"
  3. Sep 24, 2026: Permission errors in the Supabase Dashboard 36 minutes · rated "Critical"
  4. Sep 10, 2026: Unresponsive Projects 27 hours 40 min · rated "Major"
  5. Oct 22, 2026: Project lifecycle operation errors in the EU region ongoing · rated "Major"
  6. Aug 31, 2026: Project Creation Failures 2 hours 38 min · rated "Major"
  7. Sep 16, 2026: Auth Service Outage 1 hour 23 min · rated "Major"
  8. Oct 21, 2026: Project lifecycle operations such as project creation, pausing, and restoration, in all regions 1 hour 16 min · rated "Major"
  9. Oct 22, 2026: Elevated Mgmt API Error Rates in Multiple Regions ongoing · rated "Major"

Every smaller Supabase incident

Minor and short incidents from the Supabase status page, newest first, each with a line from the official updates. Times are UTC.

October 2026

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

    duration not stated · marked as no impact

    "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."

  • Oct 20, 2026, 21:59 UTC · Projects stuck in restarting state

    7 hours 41 min · marked as no impact

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

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

    60 minutes · rated "Minor"

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

  • Oct 17, 2026, 06:27 UTC · Project creation errors ap-ne1

    1 hour 22 min · rated "Minor"

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

  • Oct 12, 2026, 22:59 UTC · Realtime latency

    45 hours 26 min · rated "Minor"

    "Realtime has fully recovered."

  • Oct 12, 2026, 19:49 UTC · Edge Function Degradation

    22 hours 36 min · rated "Minor"

    "Edge function deployments have remained stable. We are closing the incident."

  • Oct 12, 2026, 19:39 UTC · Log ingestion impaired

    5 hours 51 min · rated "Minor"

    "We have resolved the log ingestion issue. During the time of this incident, logs may have been delayed or unavailable. Log ingestion has now returned to normal operation."

  • Oct 6, 2026, 15:23 UTC · Upgrade Issues

    2 hours 56 min · marked as no impact

    "We've rolled out a fix for this issue and re-enabled upgrades in the dashboard. We apologize for the inconvenience."

  • Oct 6, 2026, 07:53 UTC · Increased errors on management api leading to project operation failures

    1 hour 10 min · rated "Minor"

    "This issue has been resolved and our error rates have returned back to normal. During this incident users would have observed unauthorized/5xx failures across multiple operations on the project operations and dashboard functions."

September 2026

  • Sep 29, 2026, 16:26 UTC · Intermittent latency in Eastern US

    6 days 20 hours · rated "Minor"

    "A fix for this issue has been implemented and our data shows previous impacted users have recovered."

  • Sep 28, 2026, 13:47 UTC · Log Ingestion Degradation

    49 minutes · marked as no impact

    "Log ingestion is normal."

  • Sep 24, 2026, 15:36 UTC · Project Lifecycle Issues in eu-west-1

    2 hours 2 min · rated "Minor"

    "The remaining projects have now been brought back up, and we have no projects remaining on the unhealthy underlying hardware in the upstream infrastructure. We are monitoring to ensure ongoing stability."

  • Sep 23, 2026, 21:58 UTC · Supabase CLI CI workflow failures

    1 hour 42 min · marked as no impact

    "We've identified the cause and are working on a fix."

  • Sep 23, 2026, 10:09 UTC · Increased error rate in project creation and project restore

    40 minutes · rated "Minor"

    "We've identified the issue affecting project creation and are implementing a fix. Users may experience delays when creating new projects while we work to resolve this."

  • Sep 23, 2026, 09:31 UTC · Storage search failing for restored projects

    24 hours 30 min · rated "Minor"

    "Storage is now operating normally. We apologise for the disruption. Hardening measures are being put in place to prevent recurrence and will be communicated upon completion."

  • Sep 22, 2026, 11:09 UTC · Supavisor connection disruptions in EU West 1 (Ireland)

    1 hour 11 min · rated "Minor"

    "This incident has been resolved. Following the restart of the affected Supavisor node, error rates returned to normal and no further disruptions have been observed during the monitoring period. All services are operating normally."

  • Sep 22, 2026, 08:33 UTC · Project creations are degraded in multiple regions

    31 minutes · marked as no impact

    "The latency has recovered and the incident is now resolved."

  • Sep 19, 2026, 20:12 UTC · Project Lifecycle Activity Degradation

    2 hours · rated "Minor"

    "Project lifecycle operations are behaving normally."

  • Sep 16, 2026, 17:54 UTC · Query slowness for projects running Postgres version 14 in us-east-1 and ap-northeast-2

    2 hours 42 min · marked as no impact

    "The fix has been implemented for ap-northeast-2 and we're working on implementing the fix for us-east-1. We will continue to provide updates as progress is made."

  • Sep 16, 2026, 09:24 UTC · Edge Function Latency

    3 hours 3 min · marked as no impact

    "We are investigating reports of increased Edge Function latency and elevated rates of HTTP 503 responses, beginning at approximately 06:00 UTC."

  • Sep 14, 2026, 18:08 UTC · Latency issues resulting in 504 errors

    duration not stated · marked as no impact

    "We observed latency issues over the weekend resulting in 504 errors primarily impacting customers on the Free tier. The incident has been resolved."

  • Sep 9, 2026, 09:07 UTC · Brief connection disruptions in us-east-1 (N. Virginia)

    duration not stated · marked as no impact

    "Between 05:50-06:05 UTC some customer using Supavisor in us-east-1 may have experienced brief dropped connections or connection disruptions. This issue was caused by an unexpected restart of Supavisor instances in the affected cluster."

August 2026

  • Aug 28, 2026, 17:11 UTC · Projects failing to load Supautils in multiple regions

    duration not stated · marked as no impact

    "PostgreSQL 15 projects were failing to load /usr/lib/postgresql/15/lib/supautils.so because GLIBC_2.33 is unavailable on affected hosts. This disrupted database access in multiple regions."

Supabase uptime, last 90 days

Tracked since Oct 7, 2026. Updated Oct 22, 2026, 12:35 UTC.

Uptime100%
Avg response102 ms
Problems, 30 days6
Last problemOngoing
90 days agoUp Degraded Down No dataToday

Every Supabase problem in the last 90 days

  • Degraded

    Partial System Outage

    Oct 22, 2026, 04:06 UTC · ongoing for 8 hours 29 min · from Supabase's official status page

  • Degraded

    Partial System Outage

    Oct 21, 2026, 15:50 UTC · lasted 1 hour 4 min · from Supabase's official status page

  • Degraded

    Partial System Degradation

    Oct 19, 2026, 17:26 UTC · lasted 16 minutes · from Supabase's official status page

  • Degraded

    Partial System Degradation

    Oct 17, 2026, 06:30 UTC · lasted 48 minutes · from Supabase's official status page

  • Degraded

    Partial System Degradation

    Oct 13, 2026, 13:52 UTC · lasted 13 hours 8 min · from Supabase's official status page

  • Degraded

    Partial System Degradation

    Oct 12, 2026, 19:45 UTC · lasted 6 hours 40 min · from Supabase's official status page

Day by day

Day (UTC)UptimeAvg responseWorst
Oct 22, 2026100%116 msDegraded
Oct 21, 2026100%118 msDegraded
Oct 20, 2026100%125 msUp
Oct 19, 2026100%107 msDegraded
Oct 18, 2026100%124 msUp
Oct 17, 2026100%105 msDegraded
Oct 16, 2026100%114 msUp
Oct 15, 2026100%107 msUp
Oct 14, 2026100%112 msDegraded
Oct 13, 2026100%105 msDegraded
Oct 12, 2026100%109 msDegraded
Oct 11, 2026100%94 msUp
Oct 10, 2026100%72 msUp
Oct 9, 2026100%78 msUp
Oct 8, 2026100%79 msUp
Oct 7, 2026100%69 msUp

Supabase outage questions

Was Supabase down today?

Yes. Supabase had a problem today (Oct 22, 2026, UTC): Partial System Outage (degraded, still ongoing).

Was Supabase down yesterday?

Yes. Supabase had a problem yesterday (Oct 21, 2026, UTC): Partial System Outage (degraded, 1 hour 4 min).

When was Supabase last down?

Right now: a problem started on Oct 22, 2026, 04:06 UTC: Partial System Outage.

What was the biggest Supabase outage?

Of the incidents on record since Aug 28, 2026, the biggest was on Sep 4, 2026: Project Lifecycle Actions Showing increased error rates across all regions. The Supabase status page rated it "Critical" and it lasted 7 hours 11 min.

How often does Supabase go down?

Supabase's status page posted 32 incidents since Aug 28, 2026, 19 of them in the last 30 days. Most incidents affect part of the service, not all of it. Uptime from our own checks over the last 90 days: 100%.

Times are UTC. Official incidents are the company's own posts, quoted from the Supabase status page. Problem periods start when the official status page or our checks first show a problem and end when the service is next found working, so durations are accurate to within a few minutes. Recent outages across all services.