Thycotic outage history

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 .

We are investigating an issue affecting login and access to the Delinea Platform in the US region. Some users may be unable to log in or may experience slow performance when accessing their tenants. In most cases, retrying the login attempt allows users to successfully access their tenant. Our engineering team is actively engaged. We will provide an update as soon as more information is available.

We are continuing to investigate login and access issues affecting the Delinea Platform in the US region. Affected users may see an "upstream request timeout" error message when attempting to sign in, or may experience slow performance when accessing their tenant. Our engineering team is fully engaged and treating this as a top priority. We will provide an update as soon as more information is available.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

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.

This incident has been resolved. We apologize for the disruption this caused. Investigating We are investigating an issue where users in non-US regions are unable to establish new remote sessions. Affected users receive an "Engine unavailable" message when launching a session. Impact is limited to customers in non-US regions. Tenants hosted in the US region are not affected. We will provide an update as soon as we have more information. 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 .

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

We are investigating reports of degraded performance affecting Secret Server. Some users may be unable to access the Vault UI. Users may encounter the error: [Federation Runtime]: remoteEntryExports is undefined, which can prevent access to secrets. Our team is actively investigating the cause and working to restore normal service. We will provide updates as more information becomes available.

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.

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

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

We are investigating reports that some Secret Server Cloud users are unable to sign in and are being redirected to an error page. We are actively working to resolve the issue and will provide another update soon.

We have identified the root cause of the issue. A configuration change prevented affected tenants from connecting to the database, causing the application to fail to load and display error pages. Our engineering team has applied a corrective change and is validating the fix. We will provide another update soon.

A fix has been implemented and we are monitoring the results.

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

We have identified an issue preventing some customers from connecting via RDP or changing passwords remotely. We are actively working to resolve the issue and will provide another update soon.

We have identified the issue preventing some customers from connecting via proxy or changing passwords remotely. During this incident, some customers also experienced errors when creating folders. Our engineering team has isolated the root cause and is actively implementing a fix to restore normal service. We will provide another update as progress continues.

We have applied mitigation measures to restore service availability and are actively monitoring the environment to ensure continued stability. We apologize for any inconvenience this may have caused and appreciate your patience.

The issues affecting our Secret Server Cloud customers has been resolved. We apologize for any inconvenience this may have caused.

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

We are aware of reports from several customers experiencing Connector connectivity issues in the US region. We have identified the cause as the network infrastructure supporting Connector traffic and have mitigated the impact. Connectivity should now be restored. Further investigation and infrastructure changes are planned for next week to prevent recurrence. 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 .

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

We wanted to provide you with an update on the incident affecting the service(s) listed below. Our team has been working diligently to address the issue, and we have made significant progress. We appreciate your continued patience and support as we work to fully restore normal service. For any questions or concerns, please reach out to our support team at https://support.delinea.com.

We have identified the cause of the intermittent 504 / Gateway Timeout errors that some customers have experienced when accessing their Delinea Platform instances or when connector-based operations are in use. The issue stems from elevated response times in a backend service that handles connector connectivity, which is causing some requests to time out. Our engineering team has isolated the source and is actively applying corrective action to restore normal performance. Some customers may continue to see intermittent timeouts until the fix is fully in place. We will provide a further update as the situation changes.

The issue has been identified, and remediation efforts are currently underway. We will continue to provide updates as we make progress.

This incident has been resolved.

## Incident Overview  On July 24, 2026,  a subset of Delinea Platform customers in the US and AU regions experienced intermittent 504 Gateway Timeout errors, resulting in temporary service disruption while accessing Platform. On July 24, 2026, some Delinea Platform customers in US and AU regions experienced intermittent 504 Gateway Timeout errors, resulting in temporary service disruption while accessing the platform.  Start: July 24, 2026, 11:20 AM ET  End: July 24, 2026, 3:30 PM ET  ## Root Cause and Remediation  The incident was caused by an unexpected increase in request volume generated by a Secret Server Cloud synchronization process, which exceeded the processing capacity of The Platform service. As the service became overloaded, request latency increased and some requests exceeded the gateway timeout threshold, resulting in intermittent 504 Gateway Timeout errors for a subset of Platform customers.  Our engineering team applied immediate mitigations to reduce load while working to resolve the underlying capacity constraint, and is implementing a long-term solution to improve capacity handling and prevent similar incidents. Additional monitoring will also be added to detect and respond to this type of condition more quickly.  ## Preventative Actions  * Improve capacity handling: Enhance the backend capacity to better accommodate periods of elevated request volume without impacting customer traffic.  * Optimize Secret Server Cloud synchronization: Engineering has implemented mitigations to address the immediate issue and prevent recurrence in the short term. A long-term solution is being developed to further improve the handling of synchronization workloads.   * Expand monitoring and alerting: implement additional monitoring and alerting to detect elevated request volumes and performance degradation earlier, enabling faster response and mitigation.      We sincerely apologize for the disruption this caused and the inconvenience to your operations. We are committed to preventing recurrence through the above actions.

We are experiencing delays in audit event processing for customers in our US East region. Audit logs and audit activity may appear delayed or incomplete in the Delinea Platform and Secret Server Cloud interfaces. No audit events are being lost. All events are captured and will be processed. Core product functionality including secret access, authentication, and password management is not affected. Our engineering team has identified the root cause and has scaled database and processing resources to address the backlog. The backlog is actively draining.

The audit event processing backlog affecting customers in our US East region has been fully cleared. Audit logs are now current and up to date. No audit events were lost during this period. Thank you for your patience.

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

We are currently investigating an issue affecting Delinea Platform where SCIM synchronization is experiencing timeouts on new user/group creation. This issue is primarily impacting customers with large group sizes (thousands of users per group). It has caused slow performance and, in some cases, login failures. As a mitigation step, SCIM Public Preview has been disabled to minimize further impact. Our team is actively investigating the root cause and will provide updates as more information becomes available.

A fix for the SCIM timeout issue has been implemented. Performance has returned to normal, and SCIM synchronization is functioning as expected. This incident is now resolved. If you continue to experience any related issues, please contact our support team at https://support.delinea.com Thank you for your patience.

## Incident Overview On July 10, 2026, customers using SCIM public preview with Active Directory integration experienced degraded connector performance. Impact was limited to tenants with an AD group containing a very large membership \(thousands of users\) that underwent a membership change during the incident window. Affected connectors saw CPU and memory utilization rise to critical levels, impairing their ability to process other requests, including logins.  * Start: July 9, 2026, approximately 11:00 PM Central \(July 10, 4:00 AM UTC\)  * End: July 13, 2026, approximately 8:00 PM Central \(July 14, 1:00 AM UTC\)  ## Root Cause and Remediation SCIM functionality, previously available through private preview, was promoted to public preview on June 24, 2026. To satisfy the SCIM protocol, the SCIM service maintains a partial copy of Active Directory's user and group data, built from change notifications streamed from AD. When SCIM received a membership-change notification for a group it had not yet fully populated, it queried AD for the group's entire membership rather than the specific change. For customers with very large AD groups, this generated a high volume of queries through the customer's connector, overwhelming it. Tenants with public preview enabled received the SCIM feature automatically, so environments not actively using SCIM were also exposed.  To remediate, SCIM was disabled for affected customers after confirming they were not actively using it, and SCIM public preview was disabled on July 13 as a precaution while a permanent fix was validated. The service was updated so that a single membership-change notification triggers a query for only that change, not the group's full membership. The fix was deployed by end of day July 13, and SCIM public preview was re-enabled on July 14, 2026 at 8:00 AM Central. No action was required from customers.  ## Preventative Actions * Expand testing to include large-scale AD group scenarios before future preview promotions.  * Add monitoring for abnormal connector-directed API call volume, so similar issues are detected before customer impact.  We sincerely apologize for the disruption this caused and the inconvenience to your operations. We are committed to preventing recurrence through the above actions.

We are aware of an issue affecting the Delinea Platform and Secret Server Cloud where users may be unable to launch secrets, encountering the error "An error has occurred in Secret Server Cloud." Our team is actively investigating the root cause and will provide an update as more information becomes available.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

## **Incident Overview**  On July 11, 2026, following a [Secret Server Cloud release](https://status.delinea.com/incidents/b8yxjwdy4kv2), customers using Session Connector launchers experienced secret launch failures, including launches brokered through the Delinea Platform. Affected launches returned an HTTP 500 error and no connection file was generated. Other launcher types and all other Secret Server functionality were unaffected.  * Start: July 11, 2026, approximately 5:00 PM UTC * End: July 12, 2026, 8:34 AM UTC \(rollback completed across all regions\) ## **Root Cause and Remediation** The release changed how launcher configuration is resolved at launch time in a way that was incompatible with certain existing Session Connector launcher configurations. Launch requests for those configurations failed with a server error instead of completing normally.  To remediate, our team rolled back the release across all regions. The rollback began at 8:21 AM UTC and was completed by 8:34 AM UTC on July 12, resolving the incident. Following the rollback, our team confirmed with affected customers that secret launching had returned to normal function. No action was required from customers.  A corrected fix has been completed and verified with expanded automated regression coverage for Session Connector to launch configurations and will be included in an upcoming Secret Server Cloud release. No customer action will be required.  ## **Preventative Actions** * Automated launch test coverage is being expanded to all supported launcher types and configurations.  * Automated detection of new error signatures introduced by deployments, reducing time to detection and rollback for similar issues.  We sincerely apologize for the disruption this caused and the inconvenience to your operations. We are committed to preventing recurrence through the above actions.

Our team is aware of an issue affecting RPC and is actively investigating. We will provide additional updates as more information becomes available.

We have identified the root cause and are actively working to mitigate the issue. Further updates will be provided as they become available.

We have implemented a fix and are currently monitoring. Further updates will be provided soon.

We are pleased to inform you that the incident affecting US Secret Server Cloud 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.

## Incident Overview On July 9, 2026, customers in the SSC US region experienced degraded secret access for approximately two hours. Affected customers were unable to reliably view secrets, launch remote sessions, or perform RPC operations during the impact window. * Start: July 9, 2026, 1:52 PM Central \(6:52 PM UTC\) * End: July 9, 2026, 3:55 PM Central \(8:55 PM UTC\) ## Root Cause and Remediation During routine investigation of an unrelated alert, credentials used by our internal messaging infrastructure were regenerated. This infrastructure supports background processing, web requests, and session handling across the SSC US region. The regeneration invalidated several connections, with no transition period. This caused background processing to stop and web requests that depend on the messaging layer to hang and eventually fail. To remediate, Our team updated the affected systems with the new credentials and restarted the impacted services. Connectivity was automatically re-established once services restarted. No action was required from customers. Recovery was confirmed at 3:55 PM Central. ## Preventative Actions * Improved change-control gates on root key operations against production namespaces to prevent unreviewed key rotations. We sincerely apologize for the disruption this caused and the inconvenience to your operations. We are committed to preventing recurrence through the above action.

We are aware of an issue affecting the Delinea Platform in the US region. Some users may be experiencing difficulty logging in or accessing the platform, including unresponsive login attempts and unavailable resources after signing in. Our team is actively investigating. We will provide an update as soon as we have more information.

We have identified the cause of this incident. A connectivity issue with an upstream network provider affecting our New York point of presence is impacting access to the Delinea Platform for some US region users. Mitigation has been applied, with traffic being rerouted through an alternate point of presence to restore service. We are monitoring the situation closely and will provide a further update as events warrant

Traffic has been fully rerouted through alternate points of presence and service has been restored for affected US region users. We are monitoring the platform to confirm full stability.

This incident has been resolved.

We are currently investigating reports of Distributed Engines being unable to connect to Secret Server Cloud. Customers may experience issues accessing secrets that rely on Distributed Engines, including remote session launches through Connection Manager and proxied secret operations. Our engineering team is actively investigating the root cause and working to restore full functionality. We will provide an update as soon as we have more information. We apologize for any inconvenience this may be causing.

We are continuing to investigate this issue.

We have identified the cause of the Distributed Engine connectivity issue. A compatibility mismatch between the Distributed Engine and a backend service is preventing connections from being established. Our engineering team is deploying a fix to the impacted regions (US, UK and CA) to resolve the issue. We will continue to provide updates as the deployment progresses. We apologize for any inconvenience this may be causing.

The fix has been deployed to the UK and Canada regions. Distributed Engines in those regions will automatically re-establish connectivity. Deployment to the US region is still in progress. We will provide another update once the US deployment is complete. We apologize for any inconvenience this may be causing.

The fix has been successfully deployed to all regions. We have confirmed that Distributed Engine connectivity has been re-established across UK, Canada, and US regions. We are continuing to monitor the environment to ensure stability. We apologize for any inconvenience this has caused.

This incident has been resolved.

## Incident Overview On May 20, 2026, a subset of customers in the US, UK, and Canada regions experienced Distributed Engines going offline, which prevented access to secrets that depend on Distributed Engines. Affected customers were unable to launch remote sessions through Connection Manager and could not perform other proxied secret operations during the impact window. * **Start:** May 20, 2026, 11:30 AM Central \(4:30 PM UTC\) * **End:** May 20, 2026, 2:35 PM Central \(7:35 PM UTC\) ## Root Cause and Remediation During the recent patch of Secret Server, the Distributed Engines in US, CA, and UK were not functioning for a brief period due to an incompatibility issue between the new Distributed Engine and the prior Secret Server version. The new Distributed Engine expected a configuration value that the older Secret Server version was not yet providing, which prevented the Distributed Engine from starting up cleanly. The affected Distributed Engines entered a retry loop and could not self-recover until the compatibility issue was corrected. To remediate, the latest Secret Server backend was deployed to the impacted regions, restoring compatibility with the new Distributed Engine. The deployment was completed first in the UK and Canada regions, followed by the US region. Distributed Engines in all affected regions automatically re-established connectivity once the deployment was completed, requiring no customer action. Connectivity was confirmed restored across all three regions at 2:35 PM Central. ## Preventative Actions * Implement forward-compatibility testing for Distributed Engine releases, including a response-mocking harness that simulates a Secret Server omitting newly introduced configuration keys, and a per-PR checklist to ensure new configuration reads are covered by the harness. * Update the Distributed Engine release pipeline to support region-specific deployments, enabling controlled rollout sequencing and tighter regional containment during multi-component releases. * Strengthen automated testing to verify Secret Server compatibility with both the prior and current Distributed Engine versions. We sincerely apologize for the disruption this caused and the inconvenience to your operations. We are committed to preventing recurrence through the above actions.

Between approximately 7:47 PM and 10:48 PM EDT on Sunday, May 10, 2026, some US customers in East US region may have experienced intermittent timeout errors (including 504s) or delays when logging in to Platform. This was caused by a disruption at a US datacenter operated by our upstream network provider, which affected traffic routing in the region. The upstream issue has since been resolved and affected infrastructure has been restored. Platform login is now operating normally, and we are continuing to monitor. We apologize for any inconvenience this may have caused.

**Incident Overview**  On May 10, 2026, between 23:47 UTC and 02:48 UTC \(the next day\), some US customers in the East US region experienced intermittent login errors, including 504 timeouts and slow response times. The issue originated at the Ashburn, VA location of our web application firewall \(WAF\) infrastructure, which handles traffic routing for East US region. Service was restored during the incident by rerouting traffic through alternate locations. The Ashburn site was returned to service at 12:00 UTC on May 11, 2026.  **Root Cause**  The outage was triggered by a hardware failure within the Ashburn WAF infrastructure. A faulty optical transceiver caused the primary network link between aggregation switches to become unstable, leading to repeated connection drops. A secondary link that should have served as a failover was already inactive at the time, a condition that had gone undetected due to a gap in infrastructure monitoring. With no functioning backup, the degradation of the primary link disrupted traffic flowing through the site, resulting in the login errors customers experienced.  Two factors extended the duration of impact. First, the monitoring gap meant that the inactive backup link was not visible ahead of the incident. Second, there was a delay in executing the standard failover process \(deactivating the affected site and rerouting traffic\) once customer impact was identified. Both gaps have since been identified and remediated.  **Preventive Actions**  * The faulty optical transceivers on both the primary and secondary network links at the Ashburn location are being replaced, with a spare unit kept on-site to support faster response if needed in the future.  * The monitoring gap that failed to surface the inactive secondary link is being addressed, ensuring both active and backup links are visible to the network operations team going forward.  * Response procedures are being reviewed and reinforced to ensure the site deactivation and traffic rerouting process is initiated promptly whenever significant customer impact is detected.

As of 13:37 UTC, the degraded performance affecting Secret Server Cloud in the EU region has been resolved. Customers who experienced failures launching secrets or intermittent API errors should no longer be impacted. Our team is conducting a root cause analysis. We will post a follow-up update once findings are available. We apologize for any disruption this caused. ----------------------------------------------------------------------------------------------------------------------- Investigating — May 11, 2026, 07:57 UTC We are investigating reports of degraded performance affecting Secret Server Cloud in the EU region. Some users may be unable to launch secrets. We will provide an update as soon as more information is available.

As of 13:37 UTC on May 11, 2026, the Intermittent failures launching Secrets in the EU region has been resolved. Our preliminary investigation determined that the root cause was an outage impacting a cloud infrastructure service used by Secret Server Cloud. Normal service has been confirmed restored. We are continuing to work with our cloud provider to obtain full root cause details and identify preventative actions. We apologize for the impact to your experience and appreciate your patience while we investigated.

**Incident Overview** On May 11, 2026, starting at 07:53 UTC, Secret Server Cloud customers in the EU region experienced intermittent failures when launching secrets, initiating proxied RDP/SSH sessions, and making API calls requiring distributed engine communication. The incident was traced to a degradation in the underlying cloud messaging infrastructure in the West Central Europe region. At 13:37 UTC, the degraded performance affecting our services was fully resolved and normal operations were restored. The impact was limited to SSC customers with Distributed Engines. Secret viewing, management, and Web UI availability remained unaffected. **Root Cause** A degradation in the cloud messaging infrastructure in the West Central Europe region caused message subscription management operations to return HTTP 504 Gateway Timeout errors, preventing Distributed Engines from completing initialization and taking them offline. This resulted in timeouts across all distributed engine-routed operations, most visibly secret launches and proxied session initiations. The failure was isolated to the control plane layer of the messaging infrastructure. TCP-level connectivity remained healthy throughout the incident, and the issue was not attributed to any network or configuration change on our side. The issue was mitigated by our Cloud provider rolling back a recent release on the messaging infrastructure that had contributed to the control plane failures. **Preventive Actions** * Expand monitoring coverage for cloud messaging exception rates and Distributed Engine subscription failure patterns to enable proactive detection ahead of customer impact. * Review integration of Cloud provider health notifications into our on-call alerting pipeline to improve visibility into infrastructure events affecting Secret Server Cloud regions. * Assess improvements to Distributed Engine startup and reconnection logic to introduce retry handling with exponential back-off on transient messaging failures, reducing the risk of short-lived disruptions escalating into sustained engine outages. **Lessons Learned** The duration of customer impact during this incident was extended by gaps in our operational response. Specifically: * Limited visibility into cloud provider health events delayed our awareness of the underlying infrastructure degradation, and we did not follow our standard operating procedure to escalate with our vendor in a timely manner. * Acknowledgment of the incident on our status page was delayed, deviating from our standard incident communication process. * This incident reinforced the importance of continual improvements in both our monitoring and situational awareness of our infrastructure, as well as in our engineer training and development. We apologize for the extended impact our handling of this incident had on our customers and on their operations. We continue to take our responsibilities to our customers seriously, and have taken lessons from the handling of this incident to strengthen our processes going forward.

We are investigating reports of degraded performance affecting Privileged Access Service / Cloud Suite Pod34. Some users may experience slower than normal response times. Users may encounter slow page loads, increased latency, or timeouts. Our team is actively investigating.

We wanted to provide you with an update on the incident affecting the service(s) listed below. We have implemented a mitigation and are monitoring the situation. For any questions or concerns, please reach out to our support team at https://support.delinea.com.

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.

We are investigating reports of degraded performance affecting Privileged Access Service / Cloud Suite Pod34. Some users may experience slower than normal response times. Users may encounter slow page loads, increased latency, or timeouts. Our team is actively investigating.

We’re pleased to inform you that the incident affecting the service(s) listed below has been resolved. The load causing the issue has resolved. 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.

We have identified an issue in the recently rolled out Cloud Suite 26.1 release where custom authorization profiles containing wildcard or regex characters (e.g., "*") may return HTTP 401 errors. Built-in authorization profiles are not affected. A workaround is available. Please refer to the following knowledge base article for details: https://support.delinea.com/s/article/1777148833588 A fix is actively in progress, and is expected to be available shortly. We will post an update as events warrant. We apologize for any inconvenience this may cause.

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.