Log Ingestion Problems
Jul 22, 16:29 UTCJul 22, 20:10 UTC
Duration
3h 40m
Impact
Minor
Root cause
Not disclosed
Supabase, 90 days
56 incidents
Affected
Dashboard
Final update
This issue is now resolved. Log ingestion has returned to normal and customers can now view project logs.
Timeline
- Resolved · Jul 22, 20:10 UTC
This issue is now resolved. Log ingestion has returned to normal and customers can now view project logs.
- Monitoring · Jul 22, 18:40 UTC
We are continuing to monitor log ingestion to ensure it remains stable.
- Monitoring · Jul 22, 17:49 UTC
We have implemented a fix, and log ingestion has returned to normal. We will continue to monitor this issue to ensure it stays stable.
- Identified · Jul 22, 16:56 UTC
We have identified the issue and are working to re-enable the ingestion of logs.
- Investigating · Jul 22, 16:29 UTC
We are experiencing a problem with log ingestion. Customers may experience a lack of new logs being visible from their projects. We are investigating.
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