Supabase reported this minor-impact incident on its official status page on Jul 31, 2026, 18:36 UTC. It was resolved after 4d 1h.
Right now Supabase is degraded. Live Supabase status →
After monitoring, we have confirmed that issues affecting Management API performance have been resolved.
We are continuing to monitor the the Management API to ensure no further intermittent occurrences appear. We will provide another update within 24 hours.
We have identified the root cause and deployed a fix. We will continue to monitor the behavior through the weekend to ensure no further occurrences appear.
We are continuing mitigation efforts for the intermittent issues with the Management API.
Cause isolation is continuing. We are doing work to ensure the accuracy of the understood cause in order to have confidence in the mitigation method under consideration.
We've isolated the cause of the network issues with the Management API and we are working on a fix.
We have been alerted that our Management API is experiencing performance degradation due to intermittent network issues. Users who experience the problem are encouraged to log out and log back in to the dashboard as that has cleared the issue in many cases. Additionally, users can retry failed actions as needed. We are actively investigating a persistent fix.
Our 5-minute checks didn't record a change in Supabase's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
Supabase reported 43 incidents in the last 90 days, 16 of them major or critical. A typical incident lasted 2h 2m. See Supabase's uptime and incident history