# Degraded logging state and delayed API logs

- Provider: [Knock](https://down.guide/providers/knock)
- Confidence: Confirmed
- Impact: Degraded
- lasted 1h 12m
- started 2026-03-31 13:06 UTC
- id: DWN-3dd075b1a0
- Official page: https://status.knock.app/incidents/01KN2010K8K2D33JKKRESDYCWV

## Updates from Knock
### 2026-03-31 13:06 UTC: investigating
We're currently investigating an issue with delayed ingestion of our API logs, putting pressure on our ingestion pipeline and resulting in some degraded state for browsing API logs as well.

### 2026-03-31 13:29 UTC: monitoring
We’ve shipped a fix and we’re seeing initial signs of recovery. We are continuing to monitor closely.

### 2026-03-31 13:50 UTC: monitoring
We are seeing full recovery of API log delays. We are continuing to monitor before closing out this incident

### 2026-03-31 14:18 UTC: resolved
This incident has now been resolved and the service is now fully operational.

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

---
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-3dd075b1a0), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
