Knock App Outage History

Knock App had 32 outages in the last 2 years totaling 18h 26m of downtime — averaging 1.3 incidents per month.

There were 32 Knock App outages since July 17, 2025 totaling 18h 26m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.knock.app

Minor June 16, 2026

Elevated errors connecting to the Knock V1 Websocket API

Detected by Pingoru: Jun 16, 2026, 06:44 PM UTC
Resolved: Jun 16, 2026, 06:44 PM UTC
Duration: —

Affected: In-app feeds and guides

Timeline · 3 updates

investigating Jun 16, 2026, 05:55 PM UTC

Status: Investigating We're currently investigating elevated error rates connecting to the V1 Websocket API. Realtime behavior for in-app feed and guides is degraded as a result. Affected components In-app feeds and guides (Degraded performance)
monitoring Jun 16, 2026, 06:26 PM UTC

Status: Monitoring We have shipped a fix and are seeing resolution in websocket connections. We are continuing to monitor closely. Affected components In-app feeds and guides (Operational)
resolved Jun 16, 2026, 06:44 PM UTC

Status: Resolved This incident has been resolved. Affected components In-app feeds and guides (Operational)

Read the full incident report →

Minor June 16, 2026

Workflow run log delays

Detected by Pingoru: Jun 16, 2026, 01:38 PM UTC
Resolved: Jun 16, 2026, 01:38 PM UTC
Duration: —

Affected: Webhook deliveryLogs

Timeline · 3 updates

investigating Jun 16, 2026, 01:34 PM UTC

Status: Investigating We are investigating delays in ingesting workflow run logs and triggering outbound webhooks from workflow run events. Affected components Webhook delivery (Degraded performance) Logs (Degraded performance)
monitoring Jun 16, 2026, 01:36 PM UTC

Status: Monitoring We are seeing recovery in workflow run log and webhook delivery delays and are continuing to monitor. Affected components Webhook delivery (Operational) Logs (Operational)
resolved Jun 16, 2026, 01:38 PM UTC

Status: Resolved This incident has been resolved. Affected components Webhook delivery (Operational) Logs (Operational)

Read the full incident report →

Minor June 15, 2026

Delayed processing of workflow logs

Detected by Pingoru: Jun 15, 2026, 04:31 PM UTC
Resolved: Jun 15, 2026, 04:31 PM UTC
Duration: —

Affected: Logs

Timeline · 2 updates

monitoring Jun 15, 2026, 02:35 PM UTC

Status: Monitoring We intermittently experienced delayed workflow logs between ~09:00 AM UTC and ~01:45 PM UTC today (2026/06/15). This was caused by some internal changes in how we fan out workflow logs, which caused consumers to get temporarily backlogged. The peak delay we experienced before processing workflow logs was around 15 minutes, but we intermittently saw delays of up to 5-6 minutes. This affected 1. Logs showing up in the dashboard. 2. Workflow batch mappings. We saw complete resolution at 01:43 PM UTC. Logs are being processed within our usual window (within up to ~5s) again. Affected components Logs (Degraded performance)
resolved Jun 15, 2026, 04:31 PM UTC

Status: Resolved We did not experience any further issues after we put the fix in place. Affected components Logs (Operational)

Read the full incident report →

Minor June 4, 2026

Elevated response times loading some log data

Detected by Pingoru: Jun 04, 2026, 12:11 PM UTC
Resolved: Jun 04, 2026, 12:11 PM UTC
Duration: —

Affected: Logs

Timeline · 3 updates

investigating Jun 04, 2026, 11:40 AM UTC

Status: Investigating We're seeing elevated response times loading some log data. This is leading to slower page loads in the Dashboard and slower responses from some V1 API endpoints. Affected components Logs (Degraded performance)
monitoring Jun 04, 2026, 12:07 PM UTC

Status: Monitoring We have shipped a fix and we are seeing recovery of log data load times. We are continuing to monitor closely before resolving. Affected components Logs (Operational)
resolved Jun 04, 2026, 12:11 PM UTC

Status: Resolved This incident has been resolved. Affected components Logs (Operational)

Read the full incident report →

Minor May 1, 2026

We're investigating an issue with our Agent in the dashboard

Detected by Pingoru: May 01, 2026, 06:26 PM UTC
Resolved: May 01, 2026, 06:26 PM UTC
Duration: —

Affected: Agent

Timeline · 3 updates

investigating May 01, 2026, 05:25 PM UTC

Status: Investigating We're currently investigating an issue with our service. We'll have an update soon. Affected components Agent (Partial outage)
monitoring May 01, 2026, 05:30 PM UTC

Status: Monitoring A fix has been implemented, and we're currently monitoring the service. Affected components Agent (Operational)
resolved May 01, 2026, 06:26 PM UTC

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

Read the full incident report →

Minor May 1, 2026

Slow workflow processing and message delivery

Detected by Pingoru: May 01, 2026, 01:18 PM UTC
Resolved: May 01, 2026, 01:18 PM UTC
Duration: —

Affected: Notification deliveryLogs

Timeline · 7 updates

investigating May 01, 2026, 10:19 AM UTC

Status: Investigating We're currently investigating an issue related to slow notification processing and message delivery. Some workflows will be delayed Affected components Notification delivery (Degraded performance)
investigating May 01, 2026, 10:33 AM UTC

Status: Investigating We're seeing an extremely high amount of load on our services which is causing workflow and broadcast delays. We're working to relieve the pressure immediately. Affected components Notification delivery (Degraded performance)
investigating May 01, 2026, 10:56 AM UTC

Status: Investigating We're seeing some recovery on our services but are dealing with delays in some workflow and broadcast processing still. Our logging service is also currently delayed, so may not reflect the latest as we catch up and work through a huge influx of work. Affected components Logs (Degraded performance) Notification delivery (Degraded performance)
identified May 01, 2026, 11:22 AM UTC

Status: Identified One of our workflow queues is currently still backlogged, but we're seeing good resolution across other areas of our service and we have effectively cordoned off the source of the issue. We're burning through remaining work and are exploring ways to shed the load further to get back to stability. Affected components Logs (Degraded performance) Notification delivery (Degraded performance)
identified May 01, 2026, 12:05 PM UTC

Status: Identified We've taken steps to shuffle around work in our system which has meant that we're processing new work for all customers again. We still have some queued workflow executions that we're working through and expect to be fully caught up in the next 40 minutes. Affected components Logs (Operational) Notification delivery (Degraded performance)
identified May 01, 2026, 12:58 PM UTC

Status: Identified We are seeing a recovery in all workflow and broadcast processing delays. We are monitoring closely. Affected components Logs (Operational) Notification delivery (Operational)
resolved May 01, 2026, 01:18 PM UTC

Status: Resolved All behavior remains normal, we are considering this incident resolved. Affected components Logs (Operational) Notification delivery (Operational)

Read the full incident report →

Minor April 14, 2026

Errors with tracked link resolution

Detected by Pingoru: Apr 14, 2026, 03:19 PM UTC
Resolved: Apr 14, 2026, 03:19 PM UTC
Duration: —

Affected: Link and open tracking

Timeline · 3 updates

investigating Apr 14, 2026, 03:09 PM UTC

Status: Investigating We are investigating errors resolving and redirecting tracked links. Affected components Link and open tracking (Full outage)
monitoring Apr 14, 2026, 03:14 PM UTC

Status: Monitoring We've shipped a fix and are seeing resolution in tracked link resolution. We are monitoring closely. Affected components Link and open tracking (Degraded performance)
resolved Apr 14, 2026, 03:19 PM UTC

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

Read the full incident report →

Minor March 31, 2026

Degraded logging state and delayed API logs

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

Affected: Logs

Timeline · 4 updates

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)
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)
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)
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)

Read the full incident report →

Minor March 25, 2026

Message event delays

Detected by Pingoru: Mar 25, 2026, 04:36 PM UTC
Resolved: Mar 25, 2026, 04:36 PM UTC
Duration: —

Affected: Webhook deliveryLogs

Timeline · 4 updates

investigating Mar 25, 2026, 03:29 PM UTC

Status: Investigating We are investigating delays in creating and processing message events. Some customers may experience delays seeing message events in the Knock Dashboard. Some customers may also experience delays in outbound webhook events triggered by message events. Affected components Webhook delivery (Degraded performance) Logs (Degraded performance)
identified Mar 25, 2026, 04:21 PM UTC

Status: Identified We've implemented a fix and are seeing message event lag begin to recover. Affected components Webhook delivery (Degraded performance) Logs (Degraded performance)
identified Mar 25, 2026, 04:22 PM UTC

Status: Identified Webhook delivery lag has resolved. We are still waiting for message event Dashboard availability lag to recover. Affected components Webhook delivery (Operational) Logs (Degraded performance)
resolved Mar 25, 2026, 04:36 PM UTC

Status: Resolved All message event lag has recovered. We are considering this incident resolved. Affected components Webhook delivery (Operational) Logs (Operational)

Read the full incident report →

Minor March 20, 2026

Issues promoting workflows

Detected by Pingoru: Mar 20, 2026, 12:54 AM UTC
Resolved: Mar 20, 2026, 12:54 AM UTC
Duration: —

Affected: Dashboard

Timeline · 3 updates

investigating Mar 20, 2026, 12:33 AM UTC

Status: Investigating We're currently investigating an issue with promoting workflows. We're working on a fix now. This does not impact notification delivery. Affected components Dashboard (Degraded performance)
identified Mar 20, 2026, 12:47 AM UTC

Status: Identified We've identified the issue with workflow promotion and are deploying a fix for it now. Affected components Dashboard (Degraded performance)
resolved Mar 20, 2026, 12:54 AM UTC

Status: Resolved The fix has been deployed and workflows are able to be promoted again. Affected components Dashboard (Operational)

Read the full incident report →

Minor March 20, 2026

Issues promoting workflows

Detected by Pingoru: Mar 20, 2026, 12:33 AM UTC
Resolved: Mar 20, 2026, 12:54 AM UTC
Duration: 21m

Read the full incident report →

Minor March 3, 2026

We're seeing some delays in log processing

Detected by Pingoru: Mar 03, 2026, 05:32 PM UTC
Resolved: Mar 03, 2026, 05:32 PM UTC
Duration: —

Affected: Logs

Timeline · 4 updates

investigating Mar 03, 2026, 05:02 PM UTC

Status: Investigating We're currently investigating an issue with log processing. There are no issues currently processing workflows and messages, but logs are affected. Affected components Logs (Degraded performance)
identified Mar 03, 2026, 05:23 PM UTC

Status: Identified We've identified the issue with the service and are actively working on a fix. Affected components Logs (Degraded performance)
monitoring Mar 03, 2026, 05:24 PM UTC

Status: Monitoring A fix has been implemented, and we're currently monitoring the service. Affected components Logs (Degraded performance)
resolved Mar 03, 2026, 05:32 PM UTC

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

Read the full incident report →

Minor February 18, 2026

Increased latency in the dashboard

Detected by Pingoru: Feb 18, 2026, 04:54 PM UTC
Resolved: Feb 18, 2026, 04:54 PM UTC
Duration: —

Affected: Dashboard

Timeline · 3 updates

investigating Feb 18, 2026, 03:35 PM UTC

Status: Investigating We're currently investigating an issue with our service. We'll have an update soon. Affected components Dashboard (Degraded performance)
monitoring Feb 18, 2026, 04:08 PM UTC

Status: Monitoring A fix has been implemented, and we're currently monitoring the service. Affected components Dashboard (Operational)
resolved Feb 18, 2026, 04:54 PM UTC

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

Read the full incident report →

Minor February 18, 2026

Subscription workflows are delayed for some customers

Detected by Pingoru: Feb 18, 2026, 11:02 AM UTC
Resolved: Feb 18, 2026, 11:02 AM UTC
Duration: —

Affected: Notification delivery

Timeline · 3 updates

investigating Feb 18, 2026, 10:16 AM UTC

Status: Investigating We're currently investigating an issue with subscriptions in our service. Affected components Notification delivery (Degraded performance)
monitoring Feb 18, 2026, 10:32 AM UTC

Status: Monitoring Our service has caught up on the backlog of subscription workflow executions. Affected components Notification delivery (Operational)
resolved Feb 18, 2026, 11:02 AM UTC

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

Read the full incident report →

Minor February 10, 2026

Delayed workflow run logs

Detected by Pingoru: Feb 10, 2026, 01:20 AM UTC
Resolved: Feb 10, 2026, 01:20 AM UTC
Duration: —

Affected: Logs

Timeline · 4 updates

investigating Feb 10, 2026, 12:50 AM UTC

Status: Investigating We're currently investigating an issue with delayed workflow run logs. Workflow execution and message delivery are unaffected, but our log queues are currently behind. Affected components Logs (Degraded performance)
identified Feb 10, 2026, 01:07 AM UTC

Status: Identified We’ve shipped a fix to improve throughput for our consumer that processes workflow run logs and are beginning to see the consumer catch up on its backlog. We’re continuing to monitor closely. Affected components Logs (Degraded performance)
monitoring Feb 10, 2026, 01:12 AM UTC

Status: Monitoring Workflow run logs are no longer delayed. We are monitoring closely before closing this out. Affected components Logs (Operational)
resolved Feb 10, 2026, 01:20 AM UTC

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

Read the full incident report →

Minor February 5, 2026

Issues loading Knock Dashboard

Detected by Pingoru: Feb 05, 2026, 05:53 PM UTC
Resolved: Feb 05, 2026, 05:53 PM UTC
Duration: —

Affected: Dashboard

Timeline · 3 updates

investigating Feb 05, 2026, 05:36 PM UTC

Status: Investigating We're investigating reports of issues loading the Knock Dashboard. Notification delivery is not impacted at this time. Affected components Dashboard (Full outage)
monitoring Feb 05, 2026, 05:40 PM UTC

Status: Monitoring We have shipped a fix and are seeing resolution. We are monitoring for any regression. Affected components Dashboard (Operational)
resolved Feb 05, 2026, 05:53 PM UTC

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