Log Ingestion Degradation
Sep 28, 13:47 UTCSep 28, 14:36 UTC
Duration
49m
Impact
Informational
Root cause
Not disclosed
Supabase, 90 days
76 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 history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Oct 615:23 UTC2 days ago | Upgrade IssuesOct 6, 15:23 UTC | none | 2h 56m |
| Oct 615:23 UTC2 days ago | Upgrade IssuesOct 6, 15:23 UTC | minor | 2h 56m |
| Oct 607:53 UTC2 days ago | Increased errors on management api leading to project operation failuresOct 6, 07:53 UTC | minor | 1h 10m |
| Oct 607:53 UTC2 days ago | Increased errors on management api leading to project operation failuresOct 6, 07:53 UTC | minor | 1h 10m |
| Sep 2916:26 UTC9 days ago | Intermittent latency in Eastern USSep 29, 16:26 UTC | minor | 6d 19h |
| Sep 2916:26 UTC9 days ago | Intermittent latency in Eastern USSep 29, 16:26 UTC | minor | 6d 19h |