Historial de interrupciones de Knock App

1. 1 de octubre de 2026 a las 14:09 UTCidentified

   La sincronización de mensajes en los almacenes de datos del cliente se retrasa. Estamos trabajando en resolver el retraso. No se afecta la sincronización de otros datos.

2. 1 de octubre de 2026 a las 16:06 UTCidentified

   Estamos re-syncing current message data into the data warehouse and expect this to complete in the next 3 hours. En ese momento, emitiremos una nueva sincronización a todos los destinos aguas abajo con datos actualizados.

3. 2 de octubre de 2026 a las 2:56 UTCidentified

   Estamos trabajando activamente en obtener los datos de mensaje más actualizados para la exportación. El trabajo está tardando mucho en correr. Vamos a volver a funcionar sincronizaciones tan pronto como este trabajo haya finalizado.

4. 2 de octubre de 2026 a las 4:16 UTCmonitoring

   Hemos reconstruido con éxito las tablas para la exportación y estamos ejecutando sincronizaciones ahora. Seguimos monitoreando y trabajaremos en alguna rehabilitación y estabilización en los próximos días.

5. 2 de octubre de 2026 a las 21:05 UTCresolved

   Volvemos a los horarios normales de sincronización para nuestro conector de almacén de datos.

Traducido automáticamente desde la actualización oficial del incidente.

1. 21 de septiembre de 2026 a las 18:22 UTCinvestigating

   Actualmente estamos investigando un problema con la entrada de dashboard vía enlace mágico. El registro a través de google y passkey no se impacta. El envío de mensajes a través de API no está afectado.

2. 21 de septiembre de 2026 a las 18:41 UTCmonitoring

   Se ha implementado una solución, y actualmente estamos monitoreando el servicio.

3. 21 de septiembre de 2026 a las 19:24 UTCresolved

   Este incidente se resuelve, y el login de enlace mágico es totalmente funcional. La actividad maliciosa causó a nuestro proveedor de correo electrónico que marcara los correos electrónicos transaccionales de Knock, interrumpiendo la entrega de enlaces mágicos. Hemos bloqueado la actividad y la entrega de correo electrónico restaurada. Sólo los correos electrónicos de Knock de [email protected] fueron impactados. Los canales de correo electrónico del cliente no fueron afectados.

Traducido automáticamente desde la actualización oficial del incidente.

1. 31 de agosto de 2026 a las 16:42 UTCidentified

   Algunos clientes pueden ver errores en el procesamiento de flujo de trabajo. Hemos identificado el problema y estamos sacando una solución.

2. 31 de agosto de 2026 a las 16:59 UTCmonitoring

   Se ha implementado una solución, y actualmente estamos monitoreando el servicio. Los flujos de trabajo más tempranos se están recuperando.

3. 31 de agosto de 2026 a las 17:35 UTCmonitoring

   Se ha implementado una solución, y actualmente estamos monitoreando el servicio.

4. 31 de agosto de 2026 a las 18:26 UTCresolved

   Este incidente se ha resuelto y el servicio está en pleno funcionamiento.

Traducido automáticamente desde la actualización oficial del incidente.

1. 30 de julio de 2026 a las 18:10 UTCinvestigating

   Actualmente estamos investigando un retraso con nuestras exportaciones de almacenes de datos. Publicaremos una actualización pronto.

2. 31 de julio de 2026 a las 16:49 UTCresolved

   Este incidente se ha resuelto y el servicio está en pleno funcionamiento.

Traducido automáticamente desde la actualización oficial del incidente.

1. 17 de julio de 2026 a las 19:37 UTCinvestigating

   Estamos investigando retrasos de disponibilidad de registros de funcionamiento de flujo de trabajo en el Dashboard y V1 API. Actualmente estamos viendo retrasos de hasta 18 minutos para algunos registros de ejecución.

2. 17 de julio de 2026 a las 19:57 UTCresolved

   Este incidente se ha resuelto y el servicio está en pleno funcionamiento.

Traducido automáticamente desde la actualización oficial del incidente.

1. 16 de julio de 2026 a las 15:32 UTCinvestigating

   Actualmente estamos investigando errores procesando flujos de trabajo de notificación y enviando mensajes para algunos clientes.

2. 16 de julio de 2026 a las 15:35 UTCidentified

   Hemos enviado una solución y estamos empezando a ver recuperación. Continuamos monitoreando de cerca.

3. 16 de julio de 2026 a las 15:40 UTCmonitoring

   El procesamiento del flujo de trabajo y la entrega de mensajes están operativos de nuevo. Continuamos monitoreando de cerca.

4. 16 de julio de 2026 a las 15:45 UTCresolved

   Este incidente se ha resuelto y el servicio está en pleno funcionamiento.

Traducido automáticamente desde la actualización oficial del incidente.

1. 10 de julio de 2026 a las 15:17 UTCinvestigating

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

2. 10 de julio de 2026 a las 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 de julio de 2026 a las 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 de julio de 2026 a las 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 de julio de 2026 a las 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 de julio de 2026 a las 0:12 UTCresolved

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

1. 24 de junio de 2026 a las 14:00 UTCinvestigating

   We are investigating delays processing workflow run event logs.

2. 24 de junio de 2026 a las 17:26 UTCinvestigating

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

3. 24 de junio de 2026 a las 17:50 UTCresolved

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

4. 25 de junio de 2026 a las 15:30 UTCinvestigating

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

5. 26 de junio de 2026 a las 6:35 UTCresolved

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

1. 16 de junio de 2026 a las 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 de junio de 2026 a las 18:26 UTCmonitoring

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

3. 16 de junio de 2026 a las 18:44 UTCresolved

   This incident has been resolved.

1. 16 de junio de 2026 a las 13:34 UTCinvestigating

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

2. 16 de junio de 2026 a las 13:36 UTCmonitoring

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

3. 16 de junio de 2026 a las 13:38 UTCresolved

   This incident has been resolved.

1. 15 de junio de 2026 a las 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 de junio de 2026 a las 16:31 UTCresolved

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

1. 4 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 12:11 UTCresolved

   This incident has been resolved.

1. 1 de mayo de 2026 a las 17:25 UTCinvestigating

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

2. 1 de mayo de 2026 a las 17:30 UTCmonitoring

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

3. 1 de mayo de 2026 a las 18:26 UTCresolved

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

1. 1 de mayo de 2026 a las 10:19 UTCinvestigating

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

2. 1 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 12:58 UTCidentified

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

7. 1 de mayo de 2026 a las 13:18 UTCresolved

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

1. 14 de abril de 2026 a las 15:09 UTCinvestigating

   We are investigating errors resolving and redirecting tracked links.

2. 14 de abril de 2026 a las 15:14 UTCmonitoring

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

3. 14 de abril de 2026 a las 15:19 UTCresolved

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

1. 31 de marzo de 2026 a las 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 de marzo de 2026 a las 13:29 UTCmonitoring

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

3. 31 de marzo de 2026 a las 13:50 UTCmonitoring

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

4. 31 de marzo de 2026 a las 14:18 UTCresolved

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

1. 25 de marzo de 2026 a las 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 de marzo de 2026 a las 16:21 UTCidentified

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

3. 25 de marzo de 2026 a las 16:22 UTCidentified

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

4. 25 de marzo de 2026 a las 16:36 UTCresolved

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

1. 20 de marzo de 2026 a las 0: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 de marzo de 2026 a las 0:47 UTCidentified

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

3. 20 de marzo de 2026 a las 0:54 UTCresolved

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

1. 3 de marzo de 2026 a las 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 de marzo de 2026 a las 17:23 UTCidentified

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

3. 3 de marzo de 2026 a las 17:24 UTCmonitoring

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

4. 3 de marzo de 2026 a las 17:32 UTCresolved

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