Supabase: Projects in sa-east-1 experiencing delayed event ingestion
Timeline of updates
- investigating
EC2 scheduled events are timing out for projects in sa-east-1, leading to a subset of projects being reported as unhealthy in the Dashboard.
As a workaround, impacted users can re-start their project while we are working on providing a fix.
- monitoring
The issue has been recovered for projects impacted in sa-east-1. Actual project health or uptime has not been impacted at any time.
Users still experiencing an unhealthy event notification on their dashboard can re-start their project to recover.
A full fix will be deployed end of today UTC.
- resolved
This issue is now resolved.
Changes Rewindex caught on this incident
- Incident updated: Projects in sa-east-1 experiencing delayed event ingestion
- Incident updated: Projects in sa-east-1 experiencing delayed event ingestion
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.
How the archive is checked, and what it cannot prove.
Rewindex captured this after the last checkpoint; the next run () commits it.
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: none) posted by Supabase, started 2026-11-17 03:59 UTC, resolved after 8.7 h, 3 update(s); edited after publishing.
- Title
- Projects in sa-east-1 experiencing delayed event ingestion
- Vendor
- Supabase
- Date
- URL
- https://rewindex.com/company/supabase/incidents/01M7KTJ9JF2ZX7934BENS430HX
Supabase profileRecent Supabase incidentsAll outages on November 17, 2026Supabase in November 2026MarkdownJSON