Resolved after 2 hours 27 minutes, affecting Postgres (ap-east-1) and Postgres (ap-northeast-1) and 1 more, on November 12, 2026.
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.
Affected components
Update timeline
- investigating Nov 12, 2026, 08:35 PM UTC
We have observed increased connection errors, some databases may be unavailable with all services unhealthy.
- investigating Nov 12, 2026, 09:13 PM UTC
We continue to investigate the root cause of this issue and will provide updates as more information becomes available.
- investigating Nov 12, 2026, 09:42 PM UTC
The impact is not limited to the regions initially identified. Only a subset of projects are affected. Affected projects may continue to experience increased connection errors or database unavailability. We are continuing to investigate and will provide further updates as more information becomes available.
- identified Nov 12, 2026, 10:38 PM UTC
We have identified the issue and are implementing a fix. We are seeing improvements across affected regions. We will continue to provide further updates as they become available.
- monitoring Nov 12, 2026, 11:03 PM UTC
We are seeing continued improvements across affected regions, and services are recovering. We are moving this incident to monitoring while we continue to verify stability.
- resolved Nov 12, 2026, 11:40 PM UTC
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.
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.