Unable to log into Verkada Command

Update timeline

1. investigating Mar 05, 2026, 06:31 PM UTC

   Verkada is investigating an issue where users are unable to log into Verkada Command

2. investigating Mar 05, 2026, 06:33 PM UTC

   We are continuing to investigate this issue.

3. identified Mar 05, 2026, 06:52 PM UTC

   The issue has been identified and a fix is being implemented.

4. monitoring Mar 05, 2026, 07:10 PM UTC

   We have seen performance improvements and are monitoring results from the fix.

5. resolved Mar 05, 2026, 07:27 PM UTC

   This issue is resolved and we see all performance metrics remaining stable at normal levels.

6. postmortem Mar 12, 2026, 02:19 AM UTC

   On March 5, 2026 at 10:23am PT, Verkada experienced a service disruption that affected the Command platform for 40 minutes. During this window some customers may have experienced login issues, poor load times, or temporarily unavailable pages. Device functionality was not impaired although some device telemetry reporting was briefly delayed. Full service was restored on March 5, 2026 at 11:03am PT. Our monitoring alerted our engineering team to the issue within one minute. A spike of authenticated requests exhausted one of our core service’s capacities. This led to authentication issues and degraded performance in Command. The engineering team mitigated the issue by scaling up the affected service’s capacity. We take service reliability seriously and apologize for the disruption to you. We are reviewing and improving our services with increased resilience. Please reach out to us if you have any questions or are experiencing lingering issues.