Delinea Status Page

Oct 13, 2026 · resolved Oct 13

This incident has been resolved.

Oct 13, 2026 · resolved Oct 13

At approximately 9:13 PM UTC on October 13, 2026, some customers experienced premature disconnections when launching PRA Remote Application sessions. The sessions terminated after approximately 2–3 minutes. <b>Root Cause:</b> A recent update to the FreeRDP library introduced a regression bug that omitted the RAIL (Remote Applications Integrated Locally) client handshake during Remote Application sessions. Without this handshake, the target host treated the session as inactive and terminated it after the configured idle timeout. <b>Resolution:</b> The PRA engine was patched to restore the RAIL client handshake for Remote Application connections. The fix was deployed and connectivity was restored for affected customers by approximately 12:34 PM UTC on October 14, 2026. <b>Affected Components:</b> Platform: Privileged Remote Access - US, SEA, UK and AU regions <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>.

Sep 28, 2026 · resolved Oct 6

We’re pleased to inform you that the incident affecting the service(s) listed below has been resolved. Our team has implemented a fix, and all systems are now operating normally. We apologize for any inconvenience this incident may have caused, and we appreciate your understanding and support. For any questions or concerns, please reach out to our support team at https://support.delinea.com.

Oct 1, 2026 · resolved Oct 2

## Incident Overview On October 1, 2026, customers in the EU region had problems using Secret Server Cloud \(SSC\). Users could not launch sessions from secrets, and pages for viewing secret details and audit history loaded slowly or failed. Scheduled background tasks such as heartbeats, password changes, discovery and notifications were delayed, and some Distributed Engines could not connect. * Start Time: October 1, 2026, 08:38 PM UTC * End Time: October 2, 2026, 12:30 AM UTC ## Root Cause and Remediation SSC uses a messaging service to pass work between its components. Examples include recording secret view activity for auditing, running scheduled tasks and preparing session launches. On September 30, 2026, the SSC service that processes these messages in the EU region began handling work at a much lower rate than normal. New activity kept arriving at the normal rate, so unprocessed messages built up in the queue. When the queue reached its capacity, the extra messages were moved to a holding area for undeliverable messages. Over the following hours this holding area kept growing until the messaging service hit its storage limit. Our engineering team increased the capacity of the messaging service, scaled up and restarted the SSC EU services, and cleared the backlog of undeliverable messages. Once the backlog drained, session launches, page loads and scheduled tasks returned to normal by October 2, 2026, 12:30 AM UTC. Delayed background tasks, including heartbeats, password changes and notifications, were processed automatically after service was restored. Customers did not need to take any action. Because the services were restored immediately to end customer impact, we did not capture the diagnostic data needed to determine why their throughput dropped, so the underlying trigger remains unknown. The queue growth should have been caught earlier. During a recent migration of our alerting tooling, a configuration change sent certain cloud metric alerts, including the messaging queue size alert, to the wrong destination. That alert triggered on the morning of October 1 but never notified our on-call team. Our automated remediation for other alert types was unaffected, which masked the gap. ## Preventative Actions 1. We corrected the alert routing on October 2, 2026, so these alerts now reach our on-call team, and we are adding canary and heartbeat alerts that notify us if alert delivery from our monitoring tools stops or drops unexpectedly. 2. We are strengthening how we change alerting, by testing each alert type end to end before and after any production deployment. 3. We are monitoring for a recurrence of the slowdown and will capture the diagnostic data needed to determine its cause if it happens again. 4. We are updating our deployment cycle with a safeguard that ensures the background services are refreshed even when a release is delayed, and we are adding this step to our release checklist.  We apologize for the disruption this caused and appreciate your patience while we resolved it.

Sep 29, 2026 · resolved Sep 29

## Incident Overview  Delinea Platform users in the EU, UK, Southeast Asia, and Australia regions experienced very slow logins and intermittent login failures. Affected functionality included Entra ID single sign-on, local account authentication, and Privileged Remote Access \(PRA\) session establishment.  * Start: September 28, 2026, approximately 11:20 PM UTC  * End: September 29, 2026, approximately 01:10 AM UTC   ## Root Cause and Remediation  A scheduled deployment introduced the use of regional cache replicas to improve authentication performance. Pre-release validation confirmed the replicas were active, but a firewall configuration error prevented data synchronization between the primary cache and the regional replicas. The cloud provider's standard health reporting continued to show the replicas as healthy and available, so the issue was not surfaced before or during the release.   When the authentication service attempted to read from these replicas, requests stalled and timed out, resulting in login failures. Internal monitoring detected the elevated error rates, and the engineering team identified the root cause and rolled back the change. The rollback returned all affected regions to the primary cache and restored normal authentication. Regional cache replicas will remain disabled for the EU, UK, Southeast Asia, and Australia regions while we evaluate alternative architectures. We assessed private network connectivity between caches and determined it does not meet our reliability requirements.  ## Preventive Actions  * We are making significant improvements to how the authentication service recovers from cache connectivity problems. The goal is that a degraded cache connection no longer causes stalled or failed logins.  * We have added alternate monitoring for connection failures, giving earlier detection of cache related issues that are not reflected in the cloud provider's health reporting.  We apologize for the disruption and are committed to preventing recurrence through these measures.

Is Delinea down right now?

No — Delinea is up. All systems operational as of Oct 18, 2:16 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.