Supabase: Elevated Mgmt API Error Rates in Multiple Regions
Affected components: ap-east-1eu-west-3sa-east-1ap-south-1ap-northeast-1ap-southeast-1ap-southeast-2ca-central-1eu-central-2us-west-1us-east-1eu-west-2us-east-2eu-north-1ap-northeast-2eu-west-1us-west-2eu-central-1
Timeline of updates
- investigating
We have noticed issues with requests coming to our API gateway. We are investigating.
- identified
We have identified the issue as related to the demand on our backplane. We are implementing mitigations to scale and manage that demand.
- monitoring
The mitigations have managed the demand spike. We are monitoring for continued stability.
- monitoring
We have additional mitigations we will be deploying to reinforce our backplane. We will leave this statuspage up and in Monitoring status until all mitigations are deployed. Updates will be forthcoming if anything changes that could impact customers.
- monitoring
We have additional mitigations we will be deploying to reinforce the Management API. Updates will be forthcoming if anything changes that could impact customers.
- resolved
This issue has been resolved and our response times are back to operational.
Changes Rewindex caught on this incident
- Incident updated: API Gateway Request Issues
- Incident updated: API Gateway Request Issues
- Incident updated: API Gateway Request Issues
- Incident updated: Elevated Mgmt API Error Rates in Multiple Regions
- Incident updated: Elevated Mgmt API Error Rates in Multiple Regions
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
4d755ee8b2d7d9ed…Version 2 captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
54dd437c3d517855…Version 3 captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
ca8b20623564fb9e…Version 4 captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
cd842b000225902d…Version 5 captured
In the 2026-10-23 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
63c32f14833b5a5a…Version 6 captured
In the 2026-10-26 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
73789ae3f7683805…
Impact, status and times are the vendor’s own, as last archived. View on status.supabase.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Supabase, started 2026-10-22 17:01 UTC, resolved after 4 d, 6 update(s); edited after publishing.
- Title
- Elevated Mgmt API Error Rates in Multiple Regions
- Vendor
- Supabase
- Date
- URL
- https://rewindex.com/company/supabase/incidents/01M5J8ZQ04EZXAYF10Q75MGC1T
Supabase profileRecent Supabase incidentsAll outages on October 22, 2026Supabase in October 2026MarkdownJSON