Supabase incident

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

Minor Resolved View vendor source →

Supabase experienced a minor incident on September 16, 2026, lasting 2h 42m. The incident has been resolved; the full update timeline is below.

Started
Sep 16, 2026, 05:53 PM UTC
Resolved
Sep 16, 2026, 08:36 PM UTC
Duration
2h 42m
Detected by Pingoru
Sep 16, 2026, 05:53 PM UTC

Update timeline

  1. identified Sep 16, 2026, 05:53 PM UTC

    Projects running Postgres version 14 in us-east-1 and ap-northeast-2 may experience query slowness. We've identified the cause and are working on a fix.

  2. identified Sep 16, 2026, 06:32 PM UTC

    We are continuing to work on a fix and will provide updates as things progress.

  3. identified Sep 16, 2026, 07:17 PM UTC

    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.

  4. monitoring Sep 16, 2026, 07:48 PM UTC

    The fix has been rolled out to us-east-1. We will continue to monitor both regions for stability.

  5. resolved Sep 16, 2026, 08:36 PM UTC

    This incident has been resolved.