Centrify Outage History
Centrify is up right nowPingoru has recorded 53 incidents for Centrify: 49 in the last 12 months and 17 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 5 | 68 of 720 (9%) |
| May 2026 | 4 | 27 of 744 (4%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 9 | 94 of 744 (13%) |
| August 2026 | 3 | 13 of 744 (2%) |
| September 2026 | 6 | 58 of 720 (8%) |
| October 2026 | 5 | 158 of 590 (27%) |
Incidents, newest first
Minor October 9, 2025 Platform: US - Intermittent Login Failures 38m Platform
Started Oct 09, 2025, 07:39 PM UTC· resolved Oct 09, 2025, 08:17 PM UTC
- investigating Oct 09, 2025, 07:39 PM UTC
We are currently investigating login failures when accessing Platform tenants in US region. Our engineering teams are fully engaged and working to restore normal service as quickly as possible. We apologize for any inconvenience this may cause and appreciate your patience during this time. For assistance or updates, please contact our support team at https://support.delinea.com.
- identified Oct 09, 2025, 07:49 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Oct 09, 2025, 07:50 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Oct 09, 2025, 08:17 PM UTC
This incident has been resolved.
- postmortem Oct 21, 2025, 09:44 PM UTC
### Incident Overview Users in the US region experienced intermittent login failures while accessing Platform tenants. Some users also experienced session logouts during this period. Affected users were generally able to log in successfully after retrying. Tenants outside the US region remained fully operational. The issue was detected promptly through our internal monitoring, and engineering teams were immediately engaged. Impact started: Oct 9, 2025, 2:21 PM \(GMT-05:00\) Impact ended: Oct 9, 2025, 2:34 PM \(GMT-05:00\) ### Root Cause Multiple Platform services rely on a shared message queueing service to publish and consume messages. One of the services did not have sufficient consumers to process queued messages. A sudden spike in message volume caused the underlying storage for the message queue to approach its capacity limits, resulting in intermittent login failures and session timeouts. The issue was identified quickly through proactive alerting, and engineers mitigated it by expanding the available storage, restoring normal operations. ### Preventive Actions 1. We are adding alerts at lower disk space utilization thresholds to detect and act before reaching critical limits. 2. Implement new monitors to identify and alert on orphaned or under-consumed queues that may accumulate unprocessed messages. 3. Continue efforts to migrate message queue hosting in-house to improve control over resource scaling, performance tuning, and monitoring.