Avigilon - Notice history

The problem was caused by an unusual spike in external API calls that overloaded a backend database. This led initially to an API slow down that grew into an API outage. We've optimized database performance and will further rate limit external APIs.

The problem was caused by database performance related to a specific integration. A multi-stage improvement plan has been deployed. This incident has been resolved.

We implemented a fix and are currently monitoring the result. Slower API and UI response times should be recovering to normal.

During a standard deployment, a human error led to mistakenly deploying the older unstable June 30th version of the sync service, which caused the same issue from the June 30th event to recur. There were no new defects introduced. Once the error was identified, Engineering removed the unstable sync service from production.

A change was deployed that had no system impact, except for a UI banner stating the deployed version. The banner normally appears only in internal environments, but in this case it ended up showing in production environments. This was solely a UI bug and did not include any system changes, only internally facing changes. We are putting guardrails in place to prevent this from occurring again.

A newly released field-mapping feature introduced a step that reorganized the user records returned by the Okta API. In directories where an Okta user record contains two fields that share the same short name at different levels of the record, that step could not distinguish them and selected the wrong one. As a result, each user's unique identifier was replaced with a value that is identical for every user.

Because every user then carried the same identifier, the sync could not match users to their existing accounts. Directory Sync marks any user it cannot account for as inactive; therefore, it deactivated the affected users.

The defect only manifests against a specific Okta record structure that not all Okta configurations return. That structure was absent from our test environment. This combination made the root cause unusually difficult to trace and took the most time to diagnose during the incident. The affected record structure is valid and correct on the customer side; the defect was entirely in how our feature handled it.

We implemented a fix and are currently monitoring the result.
Users will neither to either manually sync the idp or wait for the 15/60 minute auto synch in order to see the issue resolved.

We implemented a fix and are currently monitoring the result.

Please click the + Get app button to reinstall and restore Muster Reports.

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

On June 22, 2026, a temporary automatic software update caused a brief sync delay, preventing new user or group changes from being copied into our system. No data was lost or exposed, and the issue has been resolved with automatic updates now catching up on any missed changes.

During routine operation, our platform encountered an internal infrastructure limit within our cloud environment. While we addressed this immediately, it exposed a series of behaviors that caused some users to be unable to see their list of entries in the mobile app. All identified issues have now been fixed. We have reviewed all impacted accounts and confirmed that service is fully restored.

We are currently investigating this incident.

Mitigation efforts are being monitored for resolution.