Istoricul incidentelor Knock App

1. 1 octombrie 2026 la 14:09 UTCidentified

   Sincronizarea mesajelor în depozitele de date ale clienților este amânată. Lucrăm la rezolvarea întârzierii. Alte sincronizări de date nu sunt afectate.

2. 1 octombrie 2026 la 16:06 UTCidentified

   Resincronizăm în mod activ datele mesajului curent în depozitul de date şi ne aşteptăm ca asta să se termine în următoarele 3 ore. În acel moment, vom emite o nouă sincronizare pentru toate destinațiile din aval cu date actualizate.

3. 2 octombrie 2026 la 02:56 UTCidentified

   Lucrăm activ la obţinerea celor mai actualizate date pentru export. Slujba îşi ia mai mult timp pentru a fugi. O să reluăm sincronizarea imediat ce terminăm treaba.

4. 2 octombrie 2026 la 04:16 UTCmonitoring

   Am reconstruit cu succes mesele pentru export și rulează sincronizări acum. Continuăm să monitorizăm și vom lucra la unele remediere și stabilizare în următoarele zile.

5. 2 octombrie 2026 la 21:05 UTCresolved

   Ne-am întors la programul normal de sincronizare pentru conectorul nostru depozit de date.

Traducere automată din actualizarea oficială a incidentului.

1. 21 septembrie 2026 la 18:22 UTCinvestigating

   Investigăm o problemă cu logarea tabloului de bord prin intermediul legăturii magice. Sign-in prin Google și Passkey nu sunt afectate. Mesajele trimise prin API nu sunt afectate.

2. 21 septembrie 2026 la 18:41 UTCmonitoring

   Un fix a fost implementat, și suntem în prezent monitorizarea serviciului.

3. 21 septembrie 2026 la 19:24 UTCresolved

   Acest incident este rezolvat, și link-ul magic login este complet funcțional. Activitatea malicioasă a determinat furnizorul nostru de e-mail să semnalizeze e-mailurile tranzacţionale ale tabloului Knock, perturbând furnizarea de linkuri magice. Am blocat activitatea şi am restabilit livrarea prin e-mail. Doar e-mailurile lui Knock de la [email protected] au fost afectate. Canalele de email ale clienţilor nu au fost afectate.

Traducere automată din actualizarea oficială a incidentului.

1. 31 august 2026 la 16:42 UTCidentified

   Unii clienți pot vedea erori în procesarea fluxului de lucru. Am identificat problema și sunt de rulare o fix.

2. 31 august 2026 la 16:59 UTCmonitoring

   Un fix a fost implementat, și suntem în prezent monitorizarea serviciului. Mai devreme, fluxurile de lucru sunt rejudecate.

3. 31 august 2026 la 17:35 UTCmonitoring

   Un fix a fost implementat, și suntem în prezent monitorizarea serviciului.

4. 31 august 2026 la 18:26 UTCresolved

   Acest incident a fost rezolvat şi serviciul este acum complet operaţional.

Traducere automată din actualizarea oficială a incidentului.

1. 30 iulie 2026 la 18:10 UTCinvestigating

   Investigăm o întârziere cu exporturile noastre de la depozitul de date. Vom posta o actualizare în curând.

2. 31 iulie 2026 la 16:49 UTCresolved

   Acest incident a fost rezolvat şi serviciul este acum complet operaţional.

Traducere automată din actualizarea oficială a incidentului.

1. 17 iulie 2026 la 19:37 UTCinvestigating

   Investigăm întârzierile disponibilității jurnalelor de rulare a fluxului de lucru în Dashboard și V1 API. În prezent vedem întârzieri de până la 18 minute pentru unele jurnale de rulare.

2. 17 iulie 2026 la 19:57 UTCresolved

   Acest incident a fost rezolvat şi serviciul este acum complet operaţional.

Traducere automată din actualizarea oficială a incidentului.

1. 16 iulie 2026 la 15:32 UTCinvestigating

   Investigăm în prezent erori de procesare fluxuri de lucru notificare și trimiterea de mesaje pentru unii clienți.

2. 16 iulie 2026 la 15:35 UTCidentified

   Am trimis un fix și încep să vadă recuperare. Continuăm să monitorizăm îndeaproape.

3. 16 iulie 2026 la 15:40 UTCmonitoring

   Procesarea fluxului de lucru și transmiterea mesajelor sunt operaționale din nou. Continuăm să monitorizăm îndeaproape.

4. 16 iulie 2026 la 15:45 UTCresolved

   Acest incident a fost rezolvat şi serviciul este acum complet operaţional.

Traducere automată din actualizarea oficială a incidentului.

1. 10 iulie 2026 la 15:17 UTCinvestigating

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

2. 10 iulie 2026 la 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 iulie 2026 la 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 iulie 2026 la 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 iulie 2026 la 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 iulie 2026 la 00:12 UTCresolved

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

1. 24 iunie 2026 la 14:00 UTCinvestigating

   We are investigating delays processing workflow run event logs.

2. 24 iunie 2026 la 17:26 UTCinvestigating

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

3. 24 iunie 2026 la 17:50 UTCresolved

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

4. 25 iunie 2026 la 15:30 UTCinvestigating

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

5. 26 iunie 2026 la 06:35 UTCresolved

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

1. 16 iunie 2026 la 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 iunie 2026 la 18:26 UTCmonitoring

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

3. 16 iunie 2026 la 18:44 UTCresolved

   This incident has been resolved.

1. 16 iunie 2026 la 13:34 UTCinvestigating

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

2. 16 iunie 2026 la 13:36 UTCmonitoring

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

3. 16 iunie 2026 la 13:38 UTCresolved

   This incident has been resolved.

1. 15 iunie 2026 la 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 iunie 2026 la 16:31 UTCresolved

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

1. 4 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 12:11 UTCresolved

   This incident has been resolved.

1. 1 mai 2026 la 17:25 UTCinvestigating

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

2. 1 mai 2026 la 17:30 UTCmonitoring

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

3. 1 mai 2026 la 18:26 UTCresolved

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

1. 1 mai 2026 la 10:19 UTCinvestigating

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

2. 1 mai 2026 la 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 mai 2026 la 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 mai 2026 la 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 mai 2026 la 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 mai 2026 la 12:58 UTCidentified

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

7. 1 mai 2026 la 13:18 UTCresolved

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

1. 14 aprilie 2026 la 15:09 UTCinvestigating

   We are investigating errors resolving and redirecting tracked links.

2. 14 aprilie 2026 la 15:14 UTCmonitoring

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

3. 14 aprilie 2026 la 15:19 UTCresolved

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

1. 31 martie 2026 la 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 martie 2026 la 13:29 UTCmonitoring

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

3. 31 martie 2026 la 13:50 UTCmonitoring

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

4. 31 martie 2026 la 14:18 UTCresolved

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

1. 25 martie 2026 la 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 martie 2026 la 16:21 UTCidentified

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

3. 25 martie 2026 la 16:22 UTCidentified

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

4. 25 martie 2026 la 16:36 UTCresolved

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

1. 20 martie 2026 la 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 martie 2026 la 00:47 UTCidentified

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

3. 20 martie 2026 la 00:54 UTCresolved

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

1. 3 martie 2026 la 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 martie 2026 la 17:23 UTCidentified

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

3. 3 martie 2026 la 17:24 UTCmonitoring

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

4. 3 martie 2026 la 17:32 UTCresolved

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