Log ingestion issues
May 18, 23:26 UTCMay 19, 00:10 UTC
Duration
44m
Impact
Minor
Root cause
Not disclosed
Supabase, 90 days
56 incidents
Affected
Not listed by the vendor.
Final update
This incident has been resolved, and log delivery has returned to normal. During the incident, some logs may have been delayed or unavailable. While some upstream sources may retry delivery automatically, we cannot guarantee recovery of all missing logs from the affected period. Thank you for your patience while we worked to resolve this.
Timeline
- Resolved · May 19, 00:10 UTC
This incident has been resolved, and log delivery has returned to normal. During the incident, some logs may have been delayed or unavailable. While some upstream sources may retry delivery automatically, we cannot guarantee recovery of all missing logs from the affected period. Thank you for your patience while we worked to resolve this.
More from Supabase
Full historyInterruption in connections to Supavisor in eu-west-2lasted 1h 42mIncreased Errors with Project Lifecycle Operations in US-West-2lasted 2h 28mIntermittent 502/503 errors for pg_net calls to Edge Functionslasted 42mStorage issues in us-east-1 and eu-central-1lasted 16h 18mIntermittent errors on Supavisor Shared Pooler in us-east-2lasted 29mManagement API Postgres config updates overwriting previous updateslasted 2h 8m