Knock App driftsforstyrrelser

1. 1. oktober 2026 kl. 14.09 UTCidentified

   Besked synkronisering i kundens data lagre er forsinket. Vi arbejder på at løse forsinkelsen. Andre data synkronisering er ikke påvirket.

2. 1. oktober 2026 kl. 16.06 UTCidentified

   Vi er aktivt re- synkronisering aktuelle meddelelse data ind i datalageret og forventer dette til at fuldføre i de næste 3 timer. På det tidspunkt vil vi udstede en ny synkronisering til alle downstream destinationer med opdaterede data.

3. 2. oktober 2026 kl. 02.56 UTCidentified

   Vi arbejder aktivt på at få de mest up-to-date besked data til eksport. Jobbet tager længere tid. Vi genkører synkerne, så snart jobbet er fuldført.

4. 2. oktober 2026 kl. 04.16 UTCmonitoring

   Vi har med succes genopbygget tabellerne til eksport og kører nu synk. Vi fortsætter med at overvåge og vil arbejde på en vis oprydning og yderligere stabilisering i de kommende dage.

5. 2. oktober 2026 kl. 21.05 UTCresolved

   Vi er tilbage til normale sync tidsplaner for vores data lager stik.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 21. september 2026 kl. 18.22 UTCinvestigating

   Vi undersøger i øjeblikket et problem med dashboard login via magisk link. Signal- i via google og passkey er ikke påvirket. Brev der sendes via API er ikke påvirket.

2. 21. september 2026 kl. 18.41 UTCmonitoring

   Et fix er blevet implementeret, og vi overvåger i øjeblikket tjenesten.

3. 21. september 2026 kl. 19.24 UTCresolved

   Denne hændelse er løst, og magiske link login er fuldt funktionel. Ondskabelig aktivitet forårsaget vores e-mail-udbyder til at flag Knock dashboard 's transaktionsmæssige e-mails, forstyrre magiske link leveringsevne. Vi har blokeret aktiviteten og genoprettet e-mail levering. Kun Knocks e-mails fra hello @ notifi.knock.app blev påvirket. Kundee-mail-kanaler var upåvirket.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 31. august 2026 kl. 16.42 UTCidentified

   Nogle kunder kan se fejl i workflow køre behandling. Vi har identificeret problemet.

2. 31. august 2026 kl. 16.59 UTCmonitoring

   Et fix er blevet implementeret, og vi overvåger i øjeblikket tjenesten. Tidligere svigtende arbejdsgange bliver prøvet igen.

3. 31. august 2026 kl. 17.35 UTCmonitoring

   Et fix er blevet implementeret, og vi overvåger i øjeblikket tjenesten.

4. 31. august 2026 kl. 18.26 UTCresolved

   Denne hændelse er nu løst, og tjenesten er nu fuldt operationel.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 30. juli 2026 kl. 18.10 UTCinvestigating

   Vi efterforsker i øjeblikket en forsinkelse med vores datalagereksport. Vi sender snart en opdatering.

2. 31. juli 2026 kl. 16.49 UTCresolved

   Denne hændelse er nu løst, og tjenesten er nu fuldt operationel.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 17. juli 2026 kl. 19.37 UTCinvestigating

   Vi undersøger forsinkelser af tilgængeligheden af workflow køre logs i Dashboard og V1 API. I øjeblikket ser vi forsinkelser på op til 18 minutter for nogle køre logs.

2. 17. juli 2026 kl. 19.57 UTCresolved

   Denne hændelse er nu løst, og tjenesten er nu fuldt operationel.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 16. juli 2026 kl. 15.32 UTCinvestigating

   Vi er i øjeblikket ved at undersøge fejl behandling af anmeldelse arbejdsgange og sende beskeder til nogle kunder.

2. 16. juli 2026 kl. 15.35 UTCidentified

   Vi har sendt et fix og er begyndt at se bedring. Vi overvåger fortsat nøje.

3. 16. juli 2026 kl. 15.40 UTCmonitoring

   Workflow behandling og meddelelse levering er operationel igen. Vi overvåger fortsat nøje.

4. 16. juli 2026 kl. 15.45 UTCresolved

   Denne hændelse er nu løst, og tjenesten er nu fuldt operationel.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 10. juli 2026 kl. 15.17 UTCinvestigating

   We're currently investigating an issue with our service. We'll have an update soon.

2. 10. juli 2026 kl. 15.28 UTCidentified

   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.

3. 10. juli 2026 kl. 15.33 UTCmonitoring

   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.

4. 10. juli 2026 kl. 15.40 UTCresolved

   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.

1. 1. juli 2026 kl. 21.53 UTCmonitoring

   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.

2. 3. juli 2026 kl. 00.12 UTCresolved

   This incident has now been resolved and the service is now fully operational.

1. 24. juni 2026 kl. 14.00 UTCinvestigating

   We are investigating delays processing workflow run event logs.

2. 24. juni 2026 kl. 17.26 UTCinvestigating

   We're still investigating delays affecting workflow run event logs.

3. 24. juni 2026 kl. 17.50 UTCresolved

   We've completely recovered any lag on workflow logs and we are back to normal.

4. 25. juni 2026 kl. 15.30 UTCinvestigating

   We're currently investigating an issue with some workflow logs being delayed.

5. 26. juni 2026 kl. 06.35 UTCresolved

   This incident has now been resolved and the service is now fully operational.

1. 16. juni 2026 kl. 17.55 UTCinvestigating

   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.

2. 16. juni 2026 kl. 18.26 UTCmonitoring

   We have shipped a fix and are seeing resolution in websocket connections. We are continuing to monitor closely.

3. 16. juni 2026 kl. 18.44 UTCresolved

   This incident has been resolved.

1. 16. juni 2026 kl. 13.34 UTCinvestigating

   We are investigating delays in ingesting workflow run logs and triggering outbound webhooks from workflow run events.

2. 16. juni 2026 kl. 13.36 UTCmonitoring

   We are seeing recovery in workflow run log and webhook delivery delays and are continuing to monitor.

3. 16. juni 2026 kl. 13.38 UTCresolved

   This incident has been resolved.

1. 15. juni 2026 kl. 14.35 UTCmonitoring

   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.

2. 15. juni 2026 kl. 16.31 UTCresolved

   We did not experience any further issues after we put the fix in place.

1. 4. juni 2026 kl. 11.40 UTCinvestigating

   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.

2. 4. juni 2026 kl. 12.07 UTCmonitoring

   We have shipped a fix and we are seeing recovery of log data load times. We are continuing to monitor closely before resolving.

3. 4. juni 2026 kl. 12.11 UTCresolved

   This incident has been resolved.

1. 1. maj 2026 kl. 17.25 UTCinvestigating

   We're currently investigating an issue with our service. We'll have an update soon.

2. 1. maj 2026 kl. 17.30 UTCmonitoring

   A fix has been implemented, and we're currently monitoring the service.

3. 1. maj 2026 kl. 18.26 UTCresolved

   This incident has now been resolved and the service is now fully operational.

1. 1. maj 2026 kl. 10.19 UTCinvestigating

   We're currently investigating an issue related to slow notification processing and message delivery. Some workflows will be delayed

2. 1. maj 2026 kl. 10.33 UTCinvestigating

   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.

3. 1. maj 2026 kl. 10.56 UTCinvestigating

   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.

4. 1. maj 2026 kl. 11.22 UTCidentified

   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.

5. 1. maj 2026 kl. 12.05 UTCidentified

   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.

6. 1. maj 2026 kl. 12.58 UTCidentified

   We are seeing a recovery in all workflow and broadcast processing delays. We are monitoring closely.

7. 1. maj 2026 kl. 13.18 UTCresolved

   All behavior remains normal, we are considering this incident resolved.

1. 14. april 2026 kl. 15.09 UTCinvestigating

   We are investigating errors resolving and redirecting tracked links.

2. 14. april 2026 kl. 15.14 UTCmonitoring

   We've shipped a fix and are seeing resolution in tracked link resolution. We are monitoring closely.

3. 14. april 2026 kl. 15.19 UTCresolved

   This incident has now been resolved and the service is now fully operational.

1. 31. marts 2026 kl. 13.06 UTCinvestigating

   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.

2. 31. marts 2026 kl. 13.29 UTCmonitoring

   We’ve shipped a fix and we’re seeing initial signs of recovery. We are continuing to monitor closely.

3. 31. marts 2026 kl. 13.50 UTCmonitoring

   We are seeing full recovery of API log delays. We are continuing to monitor before closing out this incident

4. 31. marts 2026 kl. 14.18 UTCresolved

   This incident has now been resolved and the service is now fully operational.

1. 25. marts 2026 kl. 15.29 UTCinvestigating

   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.

2. 25. marts 2026 kl. 16.21 UTCidentified

   We've implemented a fix and are seeing message event lag begin to recover.

3. 25. marts 2026 kl. 16.22 UTCidentified

   Webhook delivery lag has resolved. We are still waiting for message event Dashboard availability lag to recover.

4. 25. marts 2026 kl. 16.36 UTCresolved

   All message event lag has recovered. We are considering this incident resolved.

1. 20. marts 2026 kl. 00.33 UTCinvestigating

   We're currently investigating an issue with promoting workflows. We're working on a fix now. This does not impact notification delivery.

2. 20. marts 2026 kl. 00.47 UTCidentified

   We've identified the issue with workflow promotion and are deploying a fix for it now.

3. 20. marts 2026 kl. 00.54 UTCresolved

   The fix has been deployed and workflows are able to be promoted again.

1. 3. marts 2026 kl. 17.02 UTCinvestigating

   We're currently investigating an issue with log processing. There are no issues currently processing workflows and messages, but logs are affected.

2. 3. marts 2026 kl. 17.23 UTCidentified

   We've identified the issue with the service and are actively working on a fix.

3. 3. marts 2026 kl. 17.24 UTCmonitoring

   A fix has been implemented, and we're currently monitoring the service.

4. 3. marts 2026 kl. 17.32 UTCresolved

   This incident has now been resolved and the service is now fully operational.