Delinea Status Page

Jul 13, 2026 · resolved Jul 13

A fix for the SCIM timeout issue has been implemented. Performance has returned to normal, and SCIM synchronization is functioning as expected. This incident is now resolved. If you continue to experience any related issues, please contact our support team at https://support.delinea.com Thank you for your patience.

Jul 12, 2026 · resolved Jul 12

This incident has been resolved.

Jul 9, 2026 · resolved Jul 9

## Incident Overview On July 9, 2026, customers in the SSC US region experienced degraded secret access for approximately two hours. Affected customers were unable to reliably view secrets, launch remote sessions, or perform RPC operations during the impact window. * Start: July 9, 2026, 1:52 PM Central \(6:52 PM UTC\) * End: July 9, 2026, 3:55 PM Central \(8:55 PM UTC\) ## Root Cause and Remediation During routine investigation of an unrelated alert, credentials used by our internal messaging infrastructure were regenerated. This infrastructure supports background processing, web requests, and session handling across the SSC US region. The regeneration invalidated several connections, with no transition period. This caused background processing to stop and web requests that depend on the messaging layer to hang and eventually fail. To remediate, Our team updated the affected systems with the new credentials and restarted the impacted services. Connectivity was automatically re-established once services restarted. No action was required from customers. Recovery was confirmed at 3:55 PM Central. ## Preventative Actions * Improved change-control gates on root key operations against production namespaces to prevent unreviewed key rotations. We sincerely apologize for the disruption this caused and the inconvenience to your operations. We are committed to preventing recurrence through the above action.

May 28, 2026 · resolved May 28

This incident has been resolved.

May 20, 2026 · resolved May 20

## Incident Overview On May 20, 2026, a subset of customers in the US, UK, and Canada regions experienced Distributed Engines going offline, which prevented access to secrets that depend on Distributed Engines. Affected customers were unable to launch remote sessions through Connection Manager and could not perform other proxied secret operations during the impact window. * **Start:** May 20, 2026, 11:30 AM Central \(4:30 PM UTC\) * **End:** May 20, 2026, 2:35 PM Central \(7:35 PM UTC\) ## Root Cause and Remediation During the recent patch of Secret Server, the Distributed Engines in US, CA, and UK were not functioning for a brief period due to an incompatibility issue between the new Distributed Engine and the prior Secret Server version. The new Distributed Engine expected a configuration value that the older Secret Server version was not yet providing, which prevented the Distributed Engine from starting up cleanly. The affected Distributed Engines entered a retry loop and could not self-recover until the compatibility issue was corrected. To remediate, the latest Secret Server backend was deployed to the impacted regions, restoring compatibility with the new Distributed Engine. The deployment was completed first in the UK and Canada regions, followed by the US region. Distributed Engines in all affected regions automatically re-established connectivity once the deployment was completed, requiring no customer action. Connectivity was confirmed restored across all three regions at 2:35 PM Central. ## Preventative Actions * Implement forward-compatibility testing for Distributed Engine releases, including a response-mocking harness that simulates a Secret Server omitting newly introduced configuration keys, and a per-PR checklist to ensure new configuration reads are covered by the harness. * Update the Distributed Engine release pipeline to support region-specific deployments, enabling controlled rollout sequencing and tighter regional containment during multi-component releases. * Strengthen automated testing to verify Secret Server compatibility with both the prior and current Distributed Engine versions. We sincerely apologize for the disruption this caused and the inconvenience to your operations. We are committed to preventing recurrence through the above actions.

Is Delinea down right now?

No — Delinea is up. All systems operational as of Jul 13, 11:44 PM UTC.

What is Delinea's current status?

Delinea: All Systems Operational. Alert24 checks Delinea's status page continuously and can notify you the moment it changes.

How do I get alerted when Delinea goes down?

Alert24 monitors Delinea and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.