Centrify incident
Delinea Platform Connector Connectivity Issues
Centrify experienced a notice incident on July 25, 2026, lasting —. The incident has been resolved; the full update timeline is below.
Update timeline
- resolved Jul 26, 2026, 06:13 PM UTC
We are aware of reports from several customers experiencing Connector connectivity issues in the US region. We have identified the cause as the network infrastructure supporting Connector traffic and have mitigated the impact. Connectivity should now be restored. Further investigation and infrastructure changes are planned for next week to prevent recurrence.
- postmortem Aug 04, 2026, 05:01 PM UTC
## Incident Overview On July 24, 2026, customers in the US region experienced Connector connectivity issues affecting authentication through the Delinea Platform. Some Connectors intermittently went offline while others in the same environment continued operating normally, with no consistent pattern distinguishing affected from unaffected Connectors. Restarting or re-registering an affected Connector did not restore connectivity. * Start: July 24, 2026, approximately 4:50 PM ET \(8:50 PM UTC\) * End: July 24, 2026, approximately 8:00 PM ET \(July 25, 12:00 AM UTC\) ## Root Cause and Remediation The root cause was overload on backend relay services that route Connector traffic to the Delinea Platform. Because impacted and unimpacted Connectors were sometimes present in the same customer environment, initial investigation focused on individual Connector configuration and network paths. Further investigation identified the issue on TCP relays in the US-West region; one affected relay was temporarily removed from the relay pool for isolation and diagnosis. This confirmed the underlying issue was load on the affected relays rather than a defect in the relay software or hardware itself. To remediate, our team investigated and stabilized the affected relay services as they were identified, restoring Connector connectivity. Connectivity was confirmed restored the evening of July 24, and the incident was resolved by approximately 8:00 PM ET. No action was required from customers, and no customer data was lost. ## Preventative Actions * Added new relays in US-West and US-East to increase capacity and reduce the likelihood of relay overload recurring. * Improve tooling for the backend relay services to make them more resilient and self-recovering under load. * We are implementing additional monitoring of the relay services to detect this specific condition and connectivity degradation before customers are impacted. We sincerely apologize for the disruption this caused and the inconvenience to your operations. We are committed to preventing recurrence through the above actions.