Incidentsby GlyphLog Ingestion Degradation
Sep 28, 13:47 UTCSep 28, 14:36 UTC
Duration
49m
Impact
Minor
Root cause
Not disclosed
Supabase, 90 days
58 incidents
Affected
Not listed by the vendor.
Final update
Log ingestion is normal.
Timeline
- Resolved · Sep 28, 14:36 UTC
Log ingestion is normal.
- Monitoring · Sep 28, 14:00 UTC
Log ingestion has recovered. We are monitoring for continued stability.
- Identified · Sep 28, 13:52 UTC
The log ingestion issue was the result of a scaling gap. The relevant resources have been scaled and ingestion is recovering.
- Investigating · Sep 28, 13:47 UTC
Log ingestion is experiencing some delays. Ingestion will be retried by clients.
More from Supabase
Full historyElevated Error rates for All Supabase project APIslasted 1h 18mDatabase Connection Errorslasted 3h 4mStorage request degradation in eu-west-1lasted 8mProject Lifecycle Issues in ap-northeast-1lasted 4h 48mInterruption in connections to Supavisor in eu-west-2lasted 1h 42mIncreased Errors with Project Lifecycle Operations in US-West-2lasted 2h 28m