# Log Ingestion Degradation

- Provider: [Supabase](https://down.guide/providers/supabase)
- Confidence: Confirmed
- Impact: Operational
- lasted 49m
- started 2026-09-28 13:47 UTC
- id: DWN-cf1e4043f1
- Official page: https://status.supabase.com/incidents/01M3M4B906PBCBR2TRSHZ1PEAQ

## Updates from Supabase
### 2026-09-28 13:47 UTC: investigating
Log ingestion is experiencing some delays. Ingestion will be retried by clients.

### 2026-09-28 13:52 UTC: identified
The log ingestion issue was the result of a scaling gap. The relevant resources have been scaled and ingestion is recovering.

### 2026-09-28 14:00 UTC: monitoring
Log ingestion has recovered. We are monitoring for continued stability.

### 2026-09-28 14:36 UTC: resolved
Log ingestion is normal.

From the builder: does your app depend on Supabase? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=supabase) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Supabase.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-cf1e4043f1), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.