Warehouse message synchronization delayed

What to do

• Check whether your product depends on Knock. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1d 6h it lasted.

  Anything that failed between 2026-10-01 14:09 UTC and 2026-10-02 21:05 UTC may need a replay.

• Subscribe to Knock's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=knock works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Knock 5

1. identifiedOct 1, 2026, 2:09 PM UTC

   Message synchronization into customer data warehouses is delayed. We are working on resolving the delay. Other data synchronization is not affected.

   provider

2. identifiedOct 1, 2026, 4:06 PM UTC

   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.

   provider

3. identifiedOct 2, 2026, 2:56 AM UTC

   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.

   provider

4. monitoringOct 2, 2026, 4:16 AM UTC

   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.

   provider

5. resolvedOct 2, 2026, 9:05 PM UTC

   We're back to normal sync schedules for our data warehouse connector.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.