- Detected by Pingoru
- Oct 01, 2026, 04:06 PM UTC
- Resolved
- Oct 02, 2026, 09:05 PM UTC
- Duration
- 1d 4h
Affected: Data warehouse synchronization
Timeline · 5 updates
-
identified Oct 01, 2026, 02:09 PM UTC
Status: Identified Message synchronization into customer data warehouses is delayed. We are working on resolving the delay. Other data synchronization is not affected. Affected components Data warehouse synchronization (Partial outage)
-
identified Oct 01, 2026, 04:06 PM UTC
Status: Identified We're actively re-syncing current message data into the data warehouse and expect this to complete in the next 3 hours. At that time, we will issue a new sync to all downstream destinations with up to date data. Affected components Data warehouse synchronization (Partial outage)
-
identified Oct 02, 2026, 02:56 AM UTC
Status: Identified We're actively working on getting the most up-to-date message data for export. The job is taking an extended time to run. We are going to re-run syncs as soon as this job has completed. Affected components Data warehouse synchronization (Partial outage)
-
monitoring Oct 02, 2026, 04:16 AM UTC
Status: Monitoring We have successfully rebuilt the tables for export and are running syncs now. We are continuing to monitor and will be working on some remediation and further stabilization in the coming days. Affected components Data warehouse synchronization (Degraded performance)
-
resolved Oct 02, 2026, 09:05 PM UTC
Status: Resolved We're back to normal sync schedules for our data warehouse connector. Affected components Data warehouse synchronization (Operational)
Read the full incident report →
- Detected by Pingoru
- Sep 21, 2026, 07:24 PM UTC
- Resolved
- Sep 21, 2026, 07:24 PM UTC
- Duration
- —
Affected: Dashboard
Timeline · 3 updates
-
investigating Sep 21, 2026, 06:22 PM UTC
Status: Investigating We're currently investigating an issue with dashboard login via magic link. Sign-in via google and passkey are not impacted. Message sending via API is not affected. Affected components Dashboard (Partial outage)
-
monitoring Sep 21, 2026, 06:41 PM UTC
Status: Monitoring A fix has been implemented, and we're currently monitoring the service. Affected components Dashboard (Operational)
-
resolved Sep 21, 2026, 07:24 PM UTC
Status: Resolved This incident is resolved, and magic link login is fully functional. Malicious activity caused our email provider to flag the Knock dashboard's transactional emails, disrupting magic link deliverability. We've blocked the activity and restored email delivery. Only Knock's emails from [email protected] were impacted. Customer email channels were unaffected. Affected components Dashboard (Operational)
Read the full incident report →
- Detected by Pingoru
- Aug 31, 2026, 06:26 PM UTC
- Resolved
- Aug 31, 2026, 06:26 PM UTC
- Duration
- —
Affected: Notification deliveryLink and open tracking
Timeline · 4 updates
-
identified Aug 31, 2026, 04:42 PM UTC
Status: Identified Some customers may seen errors in workflow run processing. We've identified the issue and are rolling out a fix. Affected components Link and open tracking (Partial outage) Notification delivery (Partial outage)
-
monitoring Aug 31, 2026, 04:59 PM UTC
Status: Monitoring A fix has been implemented, and we're currently monitoring the service. Earlier failing workflows are being retried. Affected components Link and open tracking (Operational) Notification delivery (Degraded performance)
-
monitoring Aug 31, 2026, 05:35 PM UTC
Status: Monitoring A fix has been implemented, and we're currently monitoring the service. Affected components Link and open tracking (Operational) Notification delivery (Operational)
-
resolved Aug 31, 2026, 06:26 PM UTC
Status: Resolved This incident has now been resolved and the service is now fully operational. Affected components Link and open tracking (Operational) Notification delivery (Operational)
Read the full incident report →
- Detected by Pingoru
- Jul 31, 2026, 04:49 PM UTC
- Resolved
- Jul 31, 2026, 04:49 PM UTC
- Duration
- —
Affected: Data warehouse synchronization
Timeline · 2 updates
-
investigating Jul 30, 2026, 06:10 PM UTC
Status: Investigating We're currently investigating a delay with our data warehouse exports. We will post an update soon. Affected components Data warehouse synchronization (Degraded performance)
-
resolved Jul 31, 2026, 04:49 PM UTC
Status: Resolved This incident has now been resolved and the service is now fully operational. Affected components Data warehouse synchronization (Operational)
Read the full incident report →
- Detected by Pingoru
- Jul 17, 2026, 07:57 PM UTC
- Resolved
- Jul 17, 2026, 07:57 PM UTC
- Duration
- —
Affected: Logs
Timeline · 2 updates
-
investigating Jul 17, 2026, 07:37 PM UTC
Status: Investigating We are investigating delays of availability of workflow run logs in the Dashboard and V1 API. Currently we're seeing delays of up to 18 minutes for some run logs. Affected components Logs (Degraded performance)
-
resolved Jul 17, 2026, 07:57 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 →
- Detected by Pingoru
- Jul 10, 2026, 03:40 PM UTC
- Resolved
- Jul 10, 2026, 03:40 PM UTC
- Duration
- —
Affected: APINotification deliveryWebhook delivery
Timeline · 4 updates
-
investigating Jul 10, 2026, 03:17 PM UTC
Status: Investigating We're currently investigating an issue with our service. We'll have an update soon. Affected components Webhook delivery (Full outage) API (Degraded performance) Notification delivery (Full outage)
-
identified Jul 10, 2026, 03:28 PM UTC
Status: Identified We've identified the issue with the service and are actively working on a fix. We're seeing workflows and message deliveries process again at the usual rate. Affected components Webhook delivery (Full outage) API (Degraded performance) Notification delivery (Full outage)
-
monitoring Jul 10, 2026, 03:33 PM UTC
Status: Monitoring A fix has been implemented, and we're currently monitoring the service. All our services seem to be recovering. We're in the process of replaying any failed work that happened during the window. We expect there was no loss of workflows during this incident, but some work may have been delayed. Affected components Webhook delivery (Degraded performance) API (Operational) Notification delivery (Degraded performance)
-
resolved Jul 10, 2026, 03:40 PM UTC
Status: Resolved This incident has now been resolved and the service is now fully operational. We're replaying any jobs that may have failed during the window. All our processing queues are fully caught up. We will share a full post mortem as soon as possible. Affected components Webhook delivery (Operational) API (Operational) Notification delivery (Operational)
Read the full incident report →
- Detected by Pingoru
- Jul 03, 2026, 12:12 AM UTC
- Resolved
- Jul 03, 2026, 12:12 AM UTC
- Duration
- —
Affected: Data warehouse synchronization
Timeline · 2 updates
-
monitoring Jul 01, 2026, 09:53 PM UTC
Status: Monitoring Message data synchronization into downstream customer data warehouse destinations is delayed for messages created after 8 PM ET on June 30, 2026. We have implemented a fix. We expect the issue to be fully resolved following the nightly synchronization job scheduled on July 2nd, 2026. Affected components Data warehouse synchronization (Partial outage)
-
resolved Jul 03, 2026, 12:12 AM UTC
Status: Resolved This incident has now been resolved and the service is now fully operational. Affected components Data warehouse synchronization (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 26, 2026, 06:35 AM UTC
- Resolved
- Jun 26, 2026, 06:35 AM UTC
- Duration
- —
Affected: Logs
Timeline · 7 updates
-
investigating Jun 24, 2026, 02:00 PM UTC
Status: Investigating We are investigating delays processing workflow run event logs. Affected components Logs (Degraded performance)
-
investigating Jun 24, 2026, 03:17 PM UTC
Status: Investigating We're still investigating delays affecting workflow run event logs. Affected components Logs (Degraded performance)
-
investigating Jun 24, 2026, 04:24 PM UTC
Status: Investigating We're still investigating delays affecting workflow run event logs. Affected components Logs (Degraded performance)
-
investigating Jun 24, 2026, 05:26 PM UTC
Status: Investigating We're still investigating delays affecting workflow run event logs. Affected components Logs (Degraded performance)
-
resolved Jun 24, 2026, 05:50 PM UTC
Status: Resolved We've completely recovered any lag on workflow logs and we are back to normal. Affected components Logs (Operational)
-
investigating Jun 25, 2026, 03:30 PM UTC
Status: Investigating We're currently investigating an issue with some workflow logs being delayed. Affected components Logs (Degraded performance)
-
resolved Jun 26, 2026, 06:35 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 →
- 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 →
- 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 →
- 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 →
- 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 →
- 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 →
- 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 →
- 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 →
- 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 →
- 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 →
- 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 →
- 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 →
- 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 →
- 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 →
- 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 →
- 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)
Read the full incident report →
- Detected by Pingoru
- Jan 08, 2026, 03:53 PM UTC
- Resolved
- Jan 08, 2026, 06:08 PM UTC
- Duration
- 2h 14m
Read the full incident report →
- Detected by Pingoru
- Dec 18, 2025, 08:41 AM UTC
- Resolved
- Dec 18, 2025, 01:57 PM UTC
- Duration
- 5h 15m
Read the full incident report →
