Is Knock App down?
Last checked just nowNo incidents right now.
Knock App is operational right now. Last checked just now; the most recent incident resolved 9d ago.
Real-time Knock App status, recent outages, and incident history — pulled directly from Knock App's official status page at https://status.knock.app every 5 minutes. Pingoru tracks 9 Knock App services and has captured 12 incidents in the last 90 days (98.89% uptime). Get email, Slack, Discord, or webhook alerts the moment Knock App reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Logs
Timeline · 3 updates
- investigating · Jun 04, 2026, 11:40 AM UTC
Status: Investigating 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. Affected components Logs (Degraded performance)
- monitoring · Jun 04, 2026, 12:07 PM UTC
Status: Monitoring We have shipped a fix and we are seeing recovery of log data load times. We are continuing to monitor closely before resolving. Affected components Logs (Operational)
- resolved · Jun 04, 2026, 12:11 PM UTC
Status: Resolved This incident has been resolved. Affected components Logs (Operational)
Latest: Status: Resolved This incident has been resolved. Affected components Logs (Operational)
-
- Agent
Timeline · 3 updates
- investigating · May 01, 2026, 05:25 PM UTC
Status: Investigating We're currently investigating an issue with our service. We'll have an update soon. Affected components Agent (Partial outage)
- monitoring · May 01, 2026, 05:30 PM UTC
Status: Monitoring A fix has been implemented, and we're currently monitoring the service. Affected components Agent (Operational)
- resolved · May 01, 2026, 06:26 PM UTC
Status: Resolved This incident has now been resolved and the service is now fully operational. Affected components Agent (Operational)
Latest: Status: Resolved This incident has now been resolved and the service is now fully operational. Affected components Agent (Operational)
-
- Notification deliveryLogs
Timeline · 7 updates
- investigating · May 01, 2026, 10:19 AM UTC
Status: Investigating We're currently investigating an issue related to slow notification processing and message delivery. Some workflows will be delayed Affected components Notification delivery (Degraded performance)
- investigating · May 01, 2026, 10:33 AM UTC
Status: Investigating 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. Affected components Notification delivery (Degraded performance)
- investigating · May 01, 2026, 10:56 AM UTC
Status: Investigating 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. Affected components Logs (Degraded performance) Notification delivery (Degraded performance)
- identified · May 01, 2026, 11:22 AM UTC
Status: Identified 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. Affected components Logs (Degraded performance) Notification delivery (Degraded performance)
- identified · May 01, 2026, 12:05 PM UTC
Status: Identified 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. Affected components Logs (Operational) Notification delivery (Degraded performance)
- identified · May 01, 2026, 12:58 PM UTC
Status: Identified We are seeing a recovery in all workflow and broadcast processing delays. We are monitoring closely. Affected components Logs (Operational) Notification delivery (Operational)
- resolved · May 01, 2026, 01:18 PM UTC
Status: Resolved All behavior remains normal, we are considering this incident resolved. Affected components Logs (Operational) Notification delivery (Operational)
Latest: Status: Resolved All behavior remains normal, we are considering this incident resolved. Affected components Logs (Operational) Notification delivery (Operational)
-
- Link and open tracking
Timeline · 3 updates
- investigating · Apr 14, 2026, 03:09 PM UTC
Status: Investigating We are investigating errors resolving and redirecting tracked links. Affected components Link and open tracking (Full outage)
- monitoring · Apr 14, 2026, 03:14 PM UTC
Status: Monitoring We've shipped a fix and are seeing resolution in tracked link resolution. We are monitoring closely. Affected components Link and open tracking (Degraded performance)
- resolved · Apr 14, 2026, 03:19 PM UTC
Status: Resolved This incident has now been resolved and the service is now fully operational. Affected components Link and open tracking (Operational)
Latest: Status: Resolved This incident has now been resolved and the service is now fully operational. Affected components Link and open tracking (Operational)
-
See the full Knock App outage history
6 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Knock App outage history →Or sign up free to get alerts when Knock App breaks · 10 free monitors · No credit card
- Started Jun 04, 2026, 12:11 PM UTC · Resolved Jun 04, 2026, 12:11 PM UTC · —
- Started May 01, 2026, 06:26 PM UTC · Resolved May 01, 2026, 06:26 PM UTC · —
- Started May 01, 2026, 01:18 PM UTC · Resolved May 01, 2026, 01:18 PM UTC · —
- Errors with tracked link resolution ResolvedStarted Apr 14, 2026, 03:19 PM UTC · Resolved Apr 14, 2026, 03:19 PM UTC · —
- Errors with tracked link resolution ResolvedStarted Apr 14, 2026, 03:09 PM UTC · Resolved Apr 14, 2026, 03:19 PM UTC · 10m
- Started Mar 31, 2026, 02:18 PM UTC · Resolved Mar 31, 2026, 02:18 PM UTC · —
- Started Mar 31, 2026, 01:06 PM UTC · Resolved Mar 31, 2026, 02:18 PM UTC · 1h 12m
- Message event delays ResolvedStarted Mar 25, 2026, 04:36 PM UTC · Resolved Mar 25, 2026, 04:36 PM UTC · —