Delinea Status Page

Aug 14, 2026 · resolved Aug 14

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

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

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

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.

Is Delinea down right now?

No — Delinea is up. All systems operational as of Aug 28, 1:45 AM 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.