rewindex

ChangesSupabaseAPI Gateway Request Issues

Supabase: Incident updated: API Gateway Request Issues

Incident updateNormal progress (rule, 100%)Changed status.supabase.com (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Supabase removed; blue is what they added. Muted text is unchanged context.

ChangedStatus#1
Before: investigating
After: identified
AddedUpdateidentified#2
Before: not present
After: We have identified the issue as related to the demand on our backplane. We are implementing mitigations to scale and manage that demand.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

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.

History of this incident

Monday, October 26

1 incident change

Friday, October 23

1 incident change

Thursday, October 22

3 incident changes

Cite this

Incident updated: API Gateway Request Issues on Supabase’s status page, changed 2026-10-22 17:33 UTC (change 1 of 5).

Title
Incident updated: API Gateway Request Issues
Vendor
Supabase
Date
URL
https://rewindex.com/change/r07beafdb1a5c0e

All Supabase changesSupabase profileMarkdownJSON