Histórico de interrupções do Knock App

1. 1 Here 2026 da 14:09 UTCidentified

   A sincronização de mensagens nos armazéns de dados do cliente está atrasada. Estamos a trabalhar na resolução do atraso. A sincronização de outros dados não é afetada.

2. 1 Here 2026 da 16:06 UTCidentified

   Estamos a re-sincronizar os dados da mensagem actual no armazém de dados e esperamos que isto termine nas próximas 3 horas. Nesse momento, emitiremos uma nova sincronização para todos os destinos a jusante com dados atualizados.

3. 2 Here 2026 da 02:56 UTCidentified

   Estamos a trabalhar activamente na obtenção dos dados de mensagens mais actualizados para exportação. O trabalho está a demorar muito tempo a correr. Vamos repetir as sincronizações assim que este trabalho tiver terminado.

4. 2 Here 2026 da 04:16 UTCmonitoring

   Nós reconstruímos com sucesso as tabelas para exportação e estamos executando sincronia agora. Continuamos a acompanhar e a trabalhar na reparação e estabilização nos próximos dias.

5. 2 Here 2026 da 21:05 UTCresolved

   Voltamos aos horários normais de sincronização para o conector do armazém de dados.

Traduzido automaticamente da atualização oficial do incidente.

1. 21 Gwengolo 2026 da 18:22 UTCinvestigating

   Estamos a investigar um problema com o login do painel através do link mágico. O login via google e senha não são impactados. O envio de mensagens via API não é afetado.

2. 21 Gwengolo 2026 da 18:41 UTCmonitoring

   Foi implementada uma solução e estamos a monitorizar o serviço.

3. 21 Gwengolo 2026 da 19:24 UTCresolved

   Este incidente é resolvido, e login de link mágico é totalmente funcional. A atividade maliciosa fez com que nosso provedor de email assinale os e-mails transacionais do painel Knock, interrompendo a entregabilidade de links mágicos. Bloqueamos a atividade e restabelecemos a entrega de e-mail. Apenas os e-mails de Knock de [email protected] foram impactados. Os canais de e-mail do cliente não foram afetados.

Traduzido automaticamente da atualização oficial do incidente.

1. 31 Eost 2026 da 16:42 UTCidentified

   Alguns clientes podem ver erros no processamento de execução de fluxo de trabalho. Identificámos o problema e estamos a arranjar uma solução.

2. 31 Eost 2026 da 16:59 UTCmonitoring

   Foi implementada uma solução e estamos a monitorizar o serviço. Os fluxos de trabalho falhantes anteriores estão sendo tentados novamente.

3. 31 Eost 2026 da 17:35 UTCmonitoring

   Foi implementada uma solução e estamos a monitorizar o serviço.

4. 31 Eost 2026 da 18:26 UTCresolved

   Este incidente já foi resolvido e o serviço está agora totalmente operacional.

Traduzido automaticamente da atualização oficial do incidente.

1. 30 Gouere 2026 da 18:10 UTCinvestigating

   Estamos a investigar um atraso com as exportações do nosso armazém de dados. Publicaremos uma atualização em breve.

2. 31 Gouere 2026 da 16:49 UTCresolved

   Este incidente já foi resolvido e o serviço está agora totalmente operacional.

Traduzido automaticamente da atualização oficial do incidente.

1. 17 Gouere 2026 da 19:37 UTCinvestigating

   Estamos investigando atrasos na disponibilidade de registros de execução de fluxo de trabalho no Dashboard e API V1. Atualmente estamos vendo atrasos de até 18 minutos para alguns registros de execução.

2. 17 Gouere 2026 da 19:57 UTCresolved

   Este incidente já foi resolvido e o serviço está agora totalmente operacional.

Traduzido automaticamente da atualização oficial do incidente.

1. 16 Gouere 2026 da 15:32 UTCinvestigating

   Atualmente estamos investigando erros processando fluxos de trabalho de notificação e enviando mensagens para alguns clientes.

2. 16 Gouere 2026 da 15:35 UTCidentified

   Enviamos uma solução e estamos a começar a ver recuperação. Continuamos a acompanhar de perto.

3. 16 Gouere 2026 da 15:40 UTCmonitoring

   Processamento de fluxo de trabalho e entrega de mensagens está operacional novamente. Continuamos a acompanhar de perto.

4. 16 Gouere 2026 da 15:45 UTCresolved

   Este incidente já foi resolvido e o serviço está agora totalmente operacional.

Traduzido automaticamente da atualização oficial do incidente.

1. 10 Gouere 2026 da 15:17 UTCinvestigating

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

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

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

1. 24 Mezheven 2026 da 14:00 UTCinvestigating

   We are investigating delays processing workflow run event logs.

2. 24 Mezheven 2026 da 17:26 UTCinvestigating

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

3. 24 Mezheven 2026 da 17:50 UTCresolved

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

4. 25 Mezheven 2026 da 15:30 UTCinvestigating

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

5. 26 Mezheven 2026 da 06:35 UTCresolved

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

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

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

3. 16 Mezheven 2026 da 18:44 UTCresolved

   This incident has been resolved.

1. 16 Mezheven 2026 da 13:34 UTCinvestigating

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

2. 16 Mezheven 2026 da 13:36 UTCmonitoring

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

3. 16 Mezheven 2026 da 13:38 UTCresolved

   This incident has been resolved.

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

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

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

   This incident has been resolved.

1. 1 Mae 2026 da 17:25 UTCinvestigating

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

2. 1 Mae 2026 da 17:30 UTCmonitoring

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

3. 1 Mae 2026 da 18:26 UTCresolved

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

1. 1 Mae 2026 da 10:19 UTCinvestigating

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

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

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

7. 1 Mae 2026 da 13:18 UTCresolved

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

1. 14 Ebrel 2026 da 15:09 UTCinvestigating

   We are investigating errors resolving and redirecting tracked links.

2. 14 Ebrel 2026 da 15:14 UTCmonitoring

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

3. 14 Ebrel 2026 da 15:19 UTCresolved

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

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

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

3. 31 Meurzh 2026 da 13:50 UTCmonitoring

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

4. 31 Meurzh 2026 da 14:18 UTCresolved

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

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

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

3. 25 Meurzh 2026 da 16:22 UTCidentified

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

4. 25 Meurzh 2026 da 16:36 UTCresolved

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

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

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

3. 20 Meurzh 2026 da 00:54 UTCresolved

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

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

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

3. 3 Meurzh 2026 da 17:24 UTCmonitoring

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

4. 3 Meurzh 2026 da 17:32 UTCresolved

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