Delinea Status Page

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

This incident has been resolved.

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.

Sep 28, 2026 · resolved Sep 28

## Incident Overview Beginning at 07:10 UTC on September 28, 2026, a subset of Secret Server Cloud tenants in the Europe, UK, US, and APAC \(Singapore\) regions experienced connectivity failures. Customers on certain corporate networks encounter connection timeouts or reset errors when attempting to reach their tenants. Customers with tenant access restrictions enabled had no alternate path available and were unable to access Secret Server Cloud for the duration of the incident. * Start: September 28, 2026, 07:10 UTC * End: September 28, 2026, 10:45 UTC ## Root Cause and Remediation The Secret Server Cloud edge network experienced two separate issues that prevented traffic from some customer networks from reaching their tenants. The first was due to a defect in a software update that our edge network provider deployed. Under a specific production condition that was not identified in the provider’s pre-deployment testing, the defect caused traffic processing components to restart at several of its network locations. These components recovered automatically, and service at the affected locations was restored between 07:47 and 08:20 UTC. The second was due to an upstream internet carrier issue affecting our edge network in London caused packet loss and connection timeouts. As a result, customer networks whose traffic was routed through London continued to be affected after the first issue had cleared. Connectivity was fully restored at 10:45 UTC after traffic was rerouted away from the affected carrier. ## Preventive Actions * The provider has deployed a fix for the software defect and is strengthening its pre-deployment validation, the resilience of its infrastructure across locations, and its automated recovery mechanisms. We are tracking these commitments through to completion. * We are conducting a full review of the London carrier issue with our provider, including why traffic was not rerouted sooner, and reducing failover time so future carrier disruptions are isolated quickly. We sincerely apologize for the disruption this caused and the inconvenience to your operations. We are committed to preventing recurrence through the above actions.

Sep 26, 2026 · resolved Sep 26

We’re pleased to inform you that the issue preventing completing the deployment of pod34 and pod52 has been resolved. Both pods have been deployed and are now running on 26.2. We apologize for any inconvenience this issue 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.

Is Delinea down right now?

No — Delinea is up. All systems operational as of Oct 12, 4:52 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.