Delinea Status Page

Aug 3, 2026 · resolved Aug 3

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.

Jul 29, 2026 · resolved Jul 29

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. <b>Backfill Notice: </b> This incident was added to our status page retrospectively to provide an accurate record of service impact. More information on backfill incidents is available <a href="https://support.delinea.com/s/article/1781234369651">here</a>.

Jul 28, 2026 · resolved Jul 28

This issue has been resolved, and services are operating normally. We will continue to monitor to ensure stability.

Jul 27, 2026 · resolved Jul 27

## Incident Overview On July 27, 2026, Secret Server Cloud \(US region\) customers experienced widespread failures with RDP sessions, remote password rotation, and folder creation. The root cause was a critical internal caching layer that filled up to capacity because session entries were being stored in it without expiration. As the cache filled, it began rejecting write operations, causing a backend processing service to fail. Messages continually accumulated in an internal message queue which degraded performance for all affected tenants. * Start: July 27, 2026, approximately 2:00 PM EDT * End: July 27, 2026, approximately 4:10 PM EDT * Region impacted: US ## Root Cause and Remediation The internal caching layer had been accumulating session data with no expiration for over 20 days. At the time of investigation, approximately 86% of cache entries had no expiration set. The root cause is a code-level bug that was not setting expirations properly on session entries. Once the cache reached capacity, new writes were rejected, breaking the log pipeline and cascading into broader service failures across tenants. To remediate, the caching layer was manually flushed at approximately 4:04 PM EDT, restoring write capacity and allowing the message queue to drain. A code fix to add TTL \(time-to-live\) to the affected keys has been identified and is in progress. ## Preventative Actions * Apply a code fix to add TTL to session entries and other unbounded growth keys in the caching layer, preventing recurrence regardless of deployment cadence. * Add memory utilization alerting for the caching layer at defined thresholds, so memory pressure is detected proactively before capacity is reached. * We are looking into adding a post-release action for flushing the cache as a standard step in the deployment process We sincerely apologize for the disruption this caused and the inconvenience to your operations. We are committed to preventing recurrence through the above actions.

Jul 25, 2026 · resolved Jul 25

## 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.

Is Delinea down right now?

No — Delinea is up. All systems operational as of Aug 19, 9:40 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.