Resolved after 2 hours 59 minutes, affecting Notification delivery and Logs, on May 1, 2026.
We are seeing a recovery in all workflow and broadcast processing delays. We are monitoring closely.
Affected components
Update timeline
- investigating May 01, 2026, 10:19 AM UTC
We're currently investigating an issue related to slow notification processing and message delivery. Some workflows will be delayed
- investigating May 01, 2026, 10:33 AM UTC
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.
- investigating May 01, 2026, 10:56 AM UTC
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.
- identified May 01, 2026, 11:22 AM UTC
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.
- identified May 01, 2026, 12:05 PM UTC
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.
- identified May 01, 2026, 12:58 PM UTC
We are seeing a recovery in all workflow and broadcast processing delays. We are monitoring closely.
- resolved May 01, 2026, 01:18 PM UTC
All behavior remains normal, we are considering this incident resolved.
Your product runs on more than Knock App
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.