Supabase incident
Network restrictions preventing read replica communication
Supabase experienced a minor incident on May 20, 2026 affecting Database, lasting 7h 40m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 20, 2026, 09:04 PM UTC
Network restrictions are preventing read replicas from communicating with their primaries for a limited number of customer projects. We are actively investigating this issue.
- investigating May 20, 2026, 09:46 PM UTC
We are reviewing the impact of this issue, which is limited to projects with read replicas and network restrictions. We continue to both investigate mitigation options for the issue and identify projects that may be impacted.
- identified May 20, 2026, 10:48 PM UTC
We have identified the cause of the issue impacting read replica communication for projects. Our team is actively working on a fix and continuing to assess the impact to affected projects.
- identified May 20, 2026, 11:41 PM UTC
Our team continues to work on implementing a fix for the issue. We are continuing to monitor the impact and will provide additional updates as progress is made.
- identified May 21, 2026, 01:12 AM UTC
Our team continues to work on implementing a fix for the issue. We will provide additional updates as progress is made.
- identified May 21, 2026, 03:49 AM UTC
We have developed a fix and it is currently being validated. We will provide more updates soon.
- monitoring May 21, 2026, 04:23 AM UTC
We have merged the fix and are monitoring for stability.
- resolved May 21, 2026, 04:44 AM UTC
Communication between read replicas and their primaries for impacted projects has been restored. This incident is now resolved.