WhatBrokeToday
GTA 6FAQ
Supabase

Supabase: Query slowness for projects running Postgres version 14 in us-east-1 and ap-northeast-2

minor

Is it fixed? Yes.

Resolved after <1 min. First reported Sep 16, 20:36 UTC, resolved Sep 16, 20:36 UTC. The vendor posted it on its status page first.

What happened

PostgreSQL queries for projects running version 14 in the us-east-1 and ap-northeast-2 regions have been experiencing slowness. The issue has been resolved.

What caused it?

Under active investigation. No report has identified a root cause yet.

No verified workaround yet

This incident was resolved upstream without a reported workaround.

Official fix

Timeline

  1. Investigating(done)
  2. Workaround available(skipped)
  3. Resolved(done)
  4. Archived
  1. First report on status page

    Query slowness for projects running Postgres version 14 in us-east-1 and ap-northeast-2

    Source
  2. Official statement

    Status: Resolved This incident has been resolved.

    Source
  3. Status changed

    Status changed: new → archived (resolved more than 14 days ago).

Evidence

1 report · 1 StatusShow
  1. [1]
    Status First report
    Query slowness for projects running Postgres version 14 in us-east-1 and ap-northeast-2(opens official status page in a new tab)

    Status: Resolved This incident has been resolved.

    by supabase status

FAQ

What happened in the Supabase outage?

PostgreSQL queries for projects running version 14 in the us-east-1 and ap-northeast-2 regions have been experiencing slowness. The issue has been resolved.

What is affected by the Supabase outage?

Supabase (versions: Postgres version 14).

When did the Supabase outage start and end?

It started Sep 16, 20:36 UTC and was resolved Sep 16, 20:36 UTC, after <1 min.

How do I get alerts for Supabase?

Subscribe to the Supabase RSS feed for every new Supabase incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Supabase is down. Supabase feed

Where does this information come from?

WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source, including the vendor’s own status page.