Supabase incident
Query slowness for projects running Postgres version 14 in us-east-1 and ap-northeast-2
Resolved after 2 hours 42 minutes, on September 16, 2026.
This incident has been resolved.
Update timeline
- 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.
- 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.
- identified Sep 16, 2026, 06:32 PM UTC
We are continuing to work on a fix and will provide updates as things progress.
- identified Sep 16, 2026, 06:32 PM UTC
We are continuing to work on a fix and will provide updates as things progress.
- 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.
- 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.
- 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.
- 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.
- resolved Sep 16, 2026, 08:36 PM UTC
This incident has been resolved.
- resolved Sep 16, 2026, 08:36 PM UTC
This incident has been resolved.
- resolved Sep 16, 2026, 08:36 PM UTC
This incident has been resolved.
Your product runs on more than Supabase
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services