Live / Verkada Command / Incident
Verkada Command: Some Classic Alarms customers are experiencing issues with arming/disarming their systems
Verkada Command · verkada.comMinor incidentResolved2026-11-05 15:46 UTC
Public — what happened
Summary
Verkada Command said some customers using Classic Alarms were having trouble arming and disarming their systems, and it rated the incident as minor. The company began investigating at 23:56 UTC on 2026-11-04 and did not publish a cause in its updates. At 04:03 UTC on 2026-11-05 it said a fix was in place and it was watching the results, and the incident was marked resolved at 15:46 UTC that day.
Affected
Alarms
Timeline
- Started — 2026-11-04 23:56 UTC
- Investigating — 2026-11-04 23:56 UTC
- Monitoring — 2026-11-05 04:03 UTC
- Resolved — 2026-11-05 15:46 UTC · 15h 50m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Verkada Command against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Verkada Command: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Verkada Command report →
More from Verkada Command
Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.