All Systems Operational
US
Operational
Platform
Operational
Secret Server Cloud
Operational
Privileged Access Service / Cloud Suite
Operational
Privilege Manager Cloud
Operational
Privileged Behavior Analytics
Operational
Account Lifecycle Manager
Operational
DevOps Secrets Vault
Operational
Fastpath Assure
Operational
EU
Operational
Platform
Operational
Secret Server Cloud
Operational
Privileged Access Service / Cloud Suite
Operational
Privilege Manager Cloud
Operational
Privileged Behavior Analytics
Operational
Account Lifecycle Manager
Operational
DevOps Secrets Vault
Operational
Fastpath Assure
Operational
UK
Operational
Platform
Operational
Secret Server Cloud
Operational
Privileged Access Service / Cloud Suite
Operational
Fastpath Assure
Operational
SEA
Operational
Platform
Operational
Secret Server Cloud
Operational
Privilege Manager Cloud
Operational
Privileged Access Service / Cloud Suite
Operational
AU
Operational
Platform
Operational
Secret Server Cloud
Operational
Privileged Access Service / Cloud Suite
Operational
Privilege Manager Cloud
Operational
Account Lifecycle Manager
Operational
DevOps Secrets Vault
Operational
Privileged Behavior Analytics
Operational
CA
Operational
Platform
Operational
Secret Server Cloud
Operational
Privileged Access Service / Cloud Suite
Operational
Privilege Manager Cloud
Operational
Privileged Behavior Analytics
Operational
Account Lifecycle Manager
Operational
DevOps Secrets Vault
Operational
BR
Operational
Privileged Access Service / Cloud Suite
Operational
UAE
Operational
Platform
Operational
Secret Server Cloud
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Scheduled Maintenance
Action Required: PowerShell 7.6 Prerequisite for Privilege Control for Servers (PCS) Command Relay Sep 9, 2026 12:00-13:00 EDT
Update -
We will be undergoing scheduled maintenance during this time.
Sep 04, 2026 - 15:25 EDT
Sep 04, 2026 - 15:25 EDT
Scheduled -
Who this affects
This applies only to Privilege Control for Servers (PCS) customers who run the Command Relay workload on a Delinea Platform Engine. No action is needed if you do not run Command Relay.
What is happening
On Wednesday, September 9, 2026, we are publishing an updated Command Relay workload for Privilege Control for Servers (PCS) that runs on the .NET 10 and PowerShell 7 runtimes. PCS customers running Command Relay need to complete one change before that date.
Action required before September 9
PowerShell 7.6 or later must be installed on every Windows host running the Delinea Platform Engine with the PCS Command Relay workload. This is a prerequisite you install yourself. Command Relay does not install it for you.
PowerShell 7.6 is the only prerequisite you need to install. The .NET 10 runtime ships inside the PowerShell package, so no separate .NET installation is required.
How to check each host
Run pwsh -Version on each Platform Engine host running Command Relay. A version below 7.6, or a command that is not recognized, means that host needs PowerShell 7.6 installed.
How to install
PowerShell 7.6 is a Microsoft Long Term Support release, generally available since March 2026. There are two installation options:
1. Using winget, run the following:
winget install --id Microsoft.PowerShell --source winget
OR
2. Refer to the following Microsoft link:
https://learn.microsoft.com/en-us/powershell/scripting/install/install-powershell-on-windows?view=powershell-7.6
If a host is not ready
Command Relay checks for PowerShell 7.6 as the first step of setup and stops before installing anything else. The workload message and engine logs name the PowerShell requirement as the reason. Nothing else on the host is changed, and the update can be run again once PowerShell 7.6 is in place.
Questions
More information can be found in the Delinea Knowledge Base at https://support.delinea.com/s/article/1787266049638 and contact Delinea Support if you need additional help.
Aug 21, 2026 - 17:19 EDT
This applies only to Privilege Control for Servers (PCS) customers who run the Command Relay workload on a Delinea Platform Engine. No action is needed if you do not run Command Relay.
What is happening
On Wednesday, September 9, 2026, we are publishing an updated Command Relay workload for Privilege Control for Servers (PCS) that runs on the .NET 10 and PowerShell 7 runtimes. PCS customers running Command Relay need to complete one change before that date.
Action required before September 9
PowerShell 7.6 or later must be installed on every Windows host running the Delinea Platform Engine with the PCS Command Relay workload. This is a prerequisite you install yourself. Command Relay does not install it for you.
PowerShell 7.6 is the only prerequisite you need to install. The .NET 10 runtime ships inside the PowerShell package, so no separate .NET installation is required.
How to check each host
Run pwsh -Version on each Platform Engine host running Command Relay. A version below 7.6, or a command that is not recognized, means that host needs PowerShell 7.6 installed.
How to install
PowerShell 7.6 is a Microsoft Long Term Support release, generally available since March 2026. There are two installation options:
1. Using winget, run the following:
winget install --id Microsoft.PowerShell --source winget
OR
2. Refer to the following Microsoft link:
https://learn.microsoft.com/en-us/powershell/scripting/install/install-powershell-on-windows?view=powershell-7.6
If a host is not ready
Command Relay checks for PowerShell 7.6 as the first step of setup and stops before installing anything else. The workload message and engine logs name the PowerShell requirement as the reason. Nothing else on the host is changed, and the update can be run again once PowerShell 7.6 is in place.
Questions
More information can be found in the Delinea Knowledge Base at https://support.delinea.com/s/article/1787266049638 and contact Delinea Support if you need additional help.
Aug 21, 2026 - 17:19 EDT
Action required: Install the SSL.com certificates on your Cloud Suite systems Oct 17, 2026 04:00-14:00 EDT
What is happening
On October 17, 2026 we are rotating the *.my.centrify.net certificate. The new certificate is issued by SSL.com, as part of a phased change in the Certificate Authority that issues certificates for Cloud Suite / Privileged Access Service (PAS) domains. Systems whose trusted certificate store does not contain the SSL.com root and intermediate certificates will not validate the new certificate.
This change is not limited to one domain. Going forward, all Cloud Suite / PAS certificates are planned to be issued by SSL.com as existing certificates come up for rotation. The SSL.com root and intermediate certificates will be required for those rotations as well, so installing them now prepares your systems for every future change rather than just this one.
This is separate from the centrify.com rotation completed on August 22, which used Sectigo. Installing the Sectigo certificates does not prepare you for October 17.
Who this affects
This applies to any system that connects to a Delinea PAS or Cloud Suite tenant on my.centrify.net, including systems running the Cloud Suite client or the Server Suite agent joined to a cloud tenant, on Linux, Windows, or Solaris, and the Cloud Connector on Windows. Systems joined only to Active Directory with no cloud tenant are not affected, and customers of other Delinea products do not need to take any action.
Action required before October 17, 2026
1. Install the SSL.com certificates
Root: SSL.com TLS RSA Root CA 2022
Intermediate: SSL.com TLS Transit RSA CA R2
Intermediate: SSL.com TLS Issuing RSA CA R1
All SSL.com certificates can be downloaded from https://www.ssl.com/repository
Both intermediates are required. Add these alongside your existing Sectigo certificates rather than replacing them. The Sectigo certificates are still in use and must stay in place.
Per-operating-system instructions are available in our Support KB: https://support.delinea.com/s/article/1772984332766
2. Make sure your systems are fully patched
Systems missing operating system security patches are at higher risk of disruption during any service update, and current patch levels help your systems retrieve updated public root certificates automatically. Patching alone is not sufficient for this change, so complete step 1 as well.
How to check whether you are ready
On Linux, list the SSL.com certificates in your trust bundle. All three should appear.
awk -v cmd='openssl x509 -noout -subject' '/BEGIN/{c=cmd}{print | c}/END/{close(c)}' /etc/ssl/certs/ca-certificates.crt | grep -i "ssl.com"
On Windows, open certlm.msc and confirm the SSL.com root appears under Trusted Root Certification Authorities and both SSL.com intermediates appear under Intermediate Certification Authorities.
Connecting to your tenant is not a valid readiness test. The current certificate is not SSL.com-issued, so a successful connection today does not confirm you are ready.
If the certificates are not installed by October 17
Affected systems will fail certificate validation and lose connectivity to the service. Nothing is permanently damaged. Installing the certificates and refreshing the trust store restores service, and on Linux it takes effect after restarting the agent.
Reach out to support@delinea.com if you encounter any challenges.
Posted on Aug 25, 2026 - 16:06 EDT
On October 17, 2026 we are rotating the *.my.centrify.net certificate. The new certificate is issued by SSL.com, as part of a phased change in the Certificate Authority that issues certificates for Cloud Suite / Privileged Access Service (PAS) domains. Systems whose trusted certificate store does not contain the SSL.com root and intermediate certificates will not validate the new certificate.
This change is not limited to one domain. Going forward, all Cloud Suite / PAS certificates are planned to be issued by SSL.com as existing certificates come up for rotation. The SSL.com root and intermediate certificates will be required for those rotations as well, so installing them now prepares your systems for every future change rather than just this one.
This is separate from the centrify.com rotation completed on August 22, which used Sectigo. Installing the Sectigo certificates does not prepare you for October 17.
Who this affects
This applies to any system that connects to a Delinea PAS or Cloud Suite tenant on my.centrify.net, including systems running the Cloud Suite client or the Server Suite agent joined to a cloud tenant, on Linux, Windows, or Solaris, and the Cloud Connector on Windows. Systems joined only to Active Directory with no cloud tenant are not affected, and customers of other Delinea products do not need to take any action.
Action required before October 17, 2026
1. Install the SSL.com certificates
Root: SSL.com TLS RSA Root CA 2022
Intermediate: SSL.com TLS Transit RSA CA R2
Intermediate: SSL.com TLS Issuing RSA CA R1
All SSL.com certificates can be downloaded from https://www.ssl.com/repository
Both intermediates are required. Add these alongside your existing Sectigo certificates rather than replacing them. The Sectigo certificates are still in use and must stay in place.
Per-operating-system instructions are available in our Support KB: https://support.delinea.com/s/article/1772984332766
2. Make sure your systems are fully patched
Systems missing operating system security patches are at higher risk of disruption during any service update, and current patch levels help your systems retrieve updated public root certificates automatically. Patching alone is not sufficient for this change, so complete step 1 as well.
How to check whether you are ready
On Linux, list the SSL.com certificates in your trust bundle. All three should appear.
awk -v cmd='openssl x509 -noout -subject' '/BEGIN/{c=cmd}{print | c}/END/{close(c)}' /etc/ssl/certs/ca-certificates.crt | grep -i "ssl.com"
On Windows, open certlm.msc and confirm the SSL.com root appears under Trusted Root Certification Authorities and both SSL.com intermediates appear under Intermediate Certification Authorities.
Connecting to your tenant is not a valid readiness test. The current certificate is not SSL.com-issued, so a successful connection today does not confirm you are ready.
If the certificates are not installed by October 17
Affected systems will fail certificate validation and lose connectivity to the service. Nothing is permanently damaged. Installing the certificates and refreshing the trust store restores service, and on Linux it takes effect after restarting the agent.
Reach out to support@delinea.com if you encounter any challenges.
Posted on Aug 25, 2026 - 16:06 EDT