Identifi Status Page

Apr 14, 2026

We are continuing to work on a fix for this issue.

Mar 24, 2026 · resolved Mar 30

**Root Cause** Our investigation determined that the virtual machine \(VM\) powering the network appliance responsible for terminating customer VPN connections experienced CPU resource throttling on the underlying Azure infrastructure. This throttling degraded the appliance's ability to process network traffic, resulting in connection drops and packet loss for affected customers. To resolve the issue, Identifi migrated the appliance to an Azure VM type that is not subject to resource throttling. **What We're Doing to Prevent Recurrence** Identifi has implemented dedicated resource monitoring and alerting for this VM, enabling our team to detect and respond to similar infrastructure conditions before they impact customers.

Mar 18, 2026 · resolved Mar 19

This incident has been resolved.

Feb 24, 2026 · resolved Feb 24

All services remain operational. Root Cause Analysis will be published when available.

Nov 10, 2025 · resolved Nov 11

All installations are online. We continue to investigate the root cause.