Major incident

Knock: Warehouse message synchronization delayed

Oct 1, 2026, 14:09 UTC
started
21:05 UTC
resolved October 2, 2026
30 h 56 min
duration

Current status of Knock: Operational — live Knock status

Timeline

  1. Oct 1, 2026, 14:09 UTC
    identified
    Message synchronization into customer data warehouses is delayed. We are working on resolving the delay. Other data synchronization is not affected.
  2. Oct 1, 2026, 16:06 UTC
    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.
  3. Oct 2, 2026, 02:56 UTC
    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.
  4. Oct 2, 2026, 04:16 UTC
    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.
  5. Oct 2, 2026, 21:05 UTC
    resolved
    We're back to normal sync schedules for our data warehouse connector.

Updates as published by Knock.

Other services with incidents at the same time

This was part of a wider event: 27 services reported incidents within the hour.

More Knock incidents