Delinea Incident History

1. resolvedSep 4 · 22:00 UTC

   This incident has been resolved. We apologize for the disruption this caused. Investigating We are investigating reports of Delinea Platform tenants displaying a frozen tenant message, preventing users from signing in and accessing their environment. The condition began at approximately 4:49 PM EDT due to an incorrect configuration change, preventing certain customers from accessing their tenants. Engineering identified the cause, ran a revert job beginning at approximately 5:08 PM EDT, and all affected tenants were confirmed unfrozen by 5:55 PM EDT. 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.

Reported by Delinea on their status page.

1. resolvedAug 28 · 20:16 UTC

   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.

Reported by Delinea on their status page.

1. postmortemAug 20 · 11:49 UTC

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

Reported by Delinea on their status page.

1. postmortemAug 20 · 11:48 UTC

   ### Incident Overview  On July 20, 2026, a subset of Delinea Platform customers in the US region experienced delays in audit event processing, resulting in a lag between when actions occurred and when the corresponding audit events appeared in logs.  * Start: July 20, 2026, 10:54 AM UTC  * End: July 23, 2026, 3:58 PM UTC  ### Root Cause and Remediation  The incident was caused by an increase in audit event volume following a recent Secret Server release, which exceeded the processing capacity of the audit event pipeline in the US region. As volume grew, events were queued for processing rather than delivered in real time, causing a backlog and a corresponding delay in audit log availability. No audit events were lost during this incident.  Our engineering team scaled the underlying data processing capacity to work through the backlog while monitoring queue depth and processing rates. By July 23, 2026, all delayed events had been fully processed, audit logs were current, and normal operations had resumed.  ### Preventative Actions  * Improve automated scaling to the audit event pipeline so it can absorb increases in volume without creating a backlog or delaying log availability.  * Improve monitoring and alerting audit processing volume and queue depth to detect potential delays earlier and respond 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.

Reported by Delinea on their status page.

1. postmortemAug 19 · 22:11 UTC

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

Reported by Delinea on their status page.