Knock App incident

Degraded logging state and delayed API logs

Minor Resolved View vendor source →

Knock App experienced a minor incident on March 31, 2026 affecting Logs, lasting —. The incident has been resolved; the full update timeline is below.

Started
Mar 31, 2026, 02:18 PM UTC
Resolved
Mar 31, 2026, 02:18 PM UTC
Duration
Detected by Pingoru
Mar 31, 2026, 02:18 PM UTC

Affected components

Logs

Update timeline

  1. investigating Mar 31, 2026, 01:06 PM UTC

    Status: 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. Affected components Logs (Degraded performance)

  2. monitoring Mar 31, 2026, 01:29 PM UTC

    Status: Monitoring We’ve shipped a fix and we’re seeing initial signs of recovery. We are continuing to monitor closely. Affected components Logs (Degraded performance)

  3. monitoring Mar 31, 2026, 01:50 PM UTC

    Status: Monitoring We are seeing full recovery of API log delays. We are continuing to monitor before closing out this incident Affected components Logs (Operational)

  4. resolved Mar 31, 2026, 02:18 PM UTC

    Status: Resolved This incident has now been resolved and the service is now fully operational. Affected components Logs (Operational)