Is Centrify down?

Multiple Delinea Platform tenants were unexpectedly frozen due to an erroneous bulk configuration change, preventing customers from accessing their tenants. Engineering identified the cause, ran a revert job beginning at approximately 2:20 PM PDT, and all affected tenants were confirmed unfrozen by 2:49 PM PDT.

We are investigating an issue affecting login and access to the Delinea Platform in the US region. Some users may be unable to log in or may experience slow performance when accessing their tenants. In most cases, retrying the login attempt allows users to successfully access their tenant. Our engineering team is actively engaged. We will provide an update as soon as more information is available.

We are continuing to investigate login and access issues affecting the Delinea Platform in the US region. Affected users may see an "upstream request timeout" error message when attempting to sign in, or may experience slow performance when accessing their tenant. Our engineering team is fully engaged and treating this as a top priority. We will provide an update as soon as more information is available.

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

A fix has been implemented and we are monitoring the results.

This incident has been resolved. Login and access to the Delinea Platform in the US region have returned to normal, and users should no longer encounter errors or degraded performance when signing in. We are continuing our investigation into the underlying cause and will share a root cause analysis once that investigation is complete. We apologize for the disruption this caused.

## Incident Overview On August 28, 2026, Delinea Platform customers in the US region experienced intermittent login failures and slow performance when signing in or accessing their tenants, including error or timeout pages on the sign-in screen for some users. In some cases, retrying the login attempt allowed users to successfully access their tenant.   * Start: August 28, 2026 approximately 17:29 UTC  * End: August 28, 2026 approximately 19:19 UTC  ## Root Cause and Remediation  A caching related code change that was made on Aug 27, combined with an unusually large volume of background synchronization activity on Aug 28, exceeded the normal operating capacity of our caching infrastructure supporting login and authentication services. Connections to it began failing and other dependent services attempted to recover those connections repeatedly rather than cleanly, preventing the caching infrastructure from stabilizing on its own. This led to slow or failed login attempts and delays in identity-related operations across the US region.  Our engineering team rolled back the caching change and restarted the affected services, which cleared the failed connections and began restoring functionality, though performance remained degraded. The caching resource was scaled up to restore normal performance. We continued to closely monitor the service until full recovery was confirmed.  ## Preventative Actions * Increase the capacity and resiliency of our caching infrastructure by distributing workloads across additional resources.  * Correct monitoring thresholds to ensure capacity pressure is detected proactively before it impacts platform performance.   * Limit connection-recovery retries to prevent recovering connections from compounding system load during a stress event.  * Apply rate limiting to large synchronization jobs to prevent any single job from negatively impacting platform-wide performance.  We sincerely apologize for the disruption this caused and the inconvenience to your operations. We are committed to preventing recurrence through the above actions.

Resolved This incident has been resolved. We apologize for the disruption this caused. Investigating We are investigating an issue where users in non-US regions are unable to establish new remote sessions. Affected users receive an "Engine unavailable" message when launching a session. Impact is limited to customers in non-US regions. Tenants hosted in the US region are not affected. We will provide an update as soon as we have more information. Backfill Notice: This incident was added to our status page retrospectively to provide an accurate record of service impact. More information on backfill incidents is available here.

## Incident Overview A subset of customers in non-US regions were unable to launch new PRA sessions and received an "Engine unavailable" error. Existing running sessions were unaffected. * Start: August 14, 2026, 09:46 UTC * End: August 14, 2026, 10:45 UTC ## Root Cause and Remediation A new version of the PRA service was deployed to production on August 14, 2026 at 09:46 UTC. The new version did not correctly apply a required configuration value in the production environment, which prevented the service from locating the session engine for non-US regions. Affected customers were consequently unable to launch new sessions and received an "Engine unavailable" error. Following an increase in backend error rates during post-deployment monitoring, correlated with incoming customer reports, the deployment was rolled back to the previous stable version. Rollback completed at 10:45 UTC. Resolution was verified through backend logs and by confirming that impacted customers could successfully launch new sessions. ## Preventative Actions * Review the deployment process to determine why the configuration issue was not detected prior to production release. * Implement a staged rollout model so that new service versions are released to a single region and validated before wider deployment. * Introduce automated post-deployment health checks, including a synthetic session launch per region, that gate promotion and trigger rollback on failure. We sincerely apologize for the disruption this caused and appreciate your patience while we worked to resolve it.

We are investigating reports of degraded performance affecting Secret Server. Some users may be unable to access the Vault UI. Users may encounter the error: [Federation Runtime]: remoteEntryExports is undefined, which can prevent access to secrets. Our team is actively investigating the cause and working to restore normal service. We will provide updates as more information becomes available.

After further investigation, we have determined that this issue is isolated to Secret Server on-premises deployments and does not affect Secret Server Cloud (SSC). No impact to SSC has been identified in the US, EU, or SEA regions. This incident is now resolved.

We identified an issue affecting Secret Server Cloud for a subset of customers in the Singapore region due to increased load on backend infrastructure. Affected users experienced slow response times or difficulty accessing their instance. This was a performance issue only. This issue has been resolved and normal performance has been restored. We apologize for any inconvenience this may have caused.

### Incident Overview  On July 29, 2026, a subset of Secret Server Cloud customers in the Singapore region experienced a performance issue due to increased load on backend infrastructure. Affected users experienced slow response times or difficulty accessing their instance.  Start of Impact: July 29, 1:41AM UTC  End of Impact: July 29, 2:32AM UTC  ### Root Cause  During the affected period, a shared backend resource supporting the Singapore region experienced a spike in utilization that pushed it to its maximum capacity. An automated process responsible for scaling resources to handle the increased load failed to execute as expected, resulting in increased response times for a subset of customers in that region.  ### Preventative Actions  To prevent recurrence, the following measures are being implemented:  * Enhancing our automated scaling process to reduce the risk of similar issues occurring in the future.  We sincerely apologize for the disruption this caused and the inconvenience to your operations. We are committed to preventing recurrence through the above actions.