31 Knock App incidents · 2025年12月 — official updates, affected components, duration and resolution details.
消息同步到客户数据仓库被延迟. 我们正在努力解决拖延问题。 其他数据同步不受影响.
我们正积极将当前消息数据重新同步到数据仓中,并期望在接下来的3小时内完成. 届时,我们将向所有下游目的地发布新的同步数据.
我们正在积极获取最新消息数据供出口. 这项工作需要较长的时间才能完成。 一旦完成这项工作,我们将重新运行同步.
我们成功重建了导出表格, 并正在同步运行 。 我们正在继续监测,并将在今后几天中进行一些补救和进一步稳定.
我们的数据仓库连接器恢复到正常同步时间表.
自动翻译自官方事件更新。
我们正在调查一个问题 仪表板登录 通过魔法链接。 通过谷歌和密码签入并不受影响。 通过 API 发送信件不受影响 .
目前我们正对服务进行监控.
这一事件已经解决,而"魔法链接"登录功能完全正常. 恶意活动导致我们的电子邮件供应商标出"敲打仪表板"的交易邮件,扰乱了魔法链接的可交付性. 我们封锁了活动 恢复了邮件发送 只有从[email protected]的敲门邮件受到影响。 客户电子邮件渠道未受影响.
自动翻译自官方事件更新。
一些客户可能看到工作流程运行处理出错. 我们已经查明了问题 正在解决.
目前我们正对服务进行监控 先前失败的工作流程正在被重新审查.
目前我们正对服务进行监控.
这一事件现已得到解决,服务现已全面运作.
自动翻译自官方事件更新。
我们正在调查数据仓出口的延误 我们很快就会发布最新消息.
这一事件现已得到解决,服务现已全面运作.
自动翻译自官方事件更新。
我们正在调查Dashboard和V1 API中工作流程运行日志的延迟提供情况。 目前我们看到一些运行日志的延迟时间可达18分钟.
这一事件现已得到解决,服务现已全面运作.
自动翻译自官方事件更新。
我们正在调查处理通知工作流程的错误,并为一些客户发送信息.
我们已经运出一个固定 并开始看到恢复。 我们正在继续密切监测.
工作流程处理和消息发送再次投入使用. 我们正在继续密切监测.
这一事件现已得到解决,服务现已全面运作.
自动翻译自官方事件更新。
We're currently investigating an issue with our service. We'll have an update soon.
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.
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.
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.
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.
This incident has now been resolved and the service is now fully operational.
We are investigating delays processing workflow run event logs.
We're still investigating delays affecting workflow run event logs.
We've completely recovered any lag on workflow logs and we are back to normal.
We're currently investigating an issue with some workflow logs being delayed.
This incident has now been resolved and the service is now fully operational.
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.
We have shipped a fix and are seeing resolution in websocket connections. We are continuing to monitor closely.
This incident has been resolved.
We are investigating delays in ingesting workflow run logs and triggering outbound webhooks from workflow run events.
We are seeing recovery in workflow run log and webhook delivery delays and are continuing to monitor.
This incident has been resolved.
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.
We did not experience any further issues after we put the fix in place.
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.
We have shipped a fix and we are seeing recovery of log data load times. We are continuing to monitor closely before resolving.
This incident has been resolved.
We're currently investigating an issue with our service. We'll have an update soon.
A fix has been implemented, and we're currently monitoring the service.
This incident has now been resolved and the service is now fully operational.
We're currently investigating an issue related to slow notification processing and message delivery. Some workflows will be delayed
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.
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.
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.
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.
We are seeing a recovery in all workflow and broadcast processing delays. We are monitoring closely.
All behavior remains normal, we are considering this incident resolved.
We are investigating errors resolving and redirecting tracked links.
We've shipped a fix and are seeing resolution in tracked link resolution. We are monitoring closely.
This incident has now been resolved and the service is now fully operational.
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.
We’ve shipped a fix and we’re seeing initial signs of recovery. We are continuing to monitor closely.
We are seeing full recovery of API log delays. We are continuing to monitor before closing out this incident
This incident has now been resolved and the service is now fully operational.
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.
We've implemented a fix and are seeing message event lag begin to recover.
Webhook delivery lag has resolved. We are still waiting for message event Dashboard availability lag to recover.
All message event lag has recovered. We are considering this incident resolved.
We're currently investigating an issue with promoting workflows. We're working on a fix now. This does not impact notification delivery.
We've identified the issue with workflow promotion and are deploying a fix for it now.
The fix has been deployed and workflows are able to be promoted again.
We're currently investigating an issue with log processing. There are no issues currently processing workflows and messages, but logs are affected.
We've identified the issue with the service and are actively working on a fix.
A fix has been implemented, and we're currently monitoring the service.
This incident has now been resolved and the service is now fully operational.
