One Identity Starling Status Page

Apr 7, 2026 · resolved Apr 7

A fix has been implemented and issue has been resolved.

Nov 20, 2025 · resolved Dec 3

This incident is resolved

Oct 21, 2025 · resolved Oct 21

This incident has been resolved.

Oct 10, 2025 · resolved Oct 13

**Service Incident Summary** **Product:** One Identity Starling PAM Essentials **Region:** United States **Date:** October 9, 2025 **What happened** On October 9, 2025, at 6:05 PM UTC, customers using One Identity Starling PAM Essentials in the US region experienced an interruption to Remote Desktop session connectivity. Service was fully restored by 9:18 PM UTC. **What caused the issue** The disruption was caused by an outage within **Microsoft Azure’s West US data center**, triggered by a power-related failure during scheduled maintenance. This event impacted several Azure networking services. As a result, our service experienced an unusually high volume of network requests, which caused application components to exceed memory limits and temporarily stop responding. **How we resolved the issue** Once the root cause was identified, we scaled the affected application components to handle the increased request volume. This action restored service while Microsoft worked to resolve the underlying data center issue. **What we are doing to prevent future impact** While this type of cloud infrastructure failure is rare, we are taking steps to reduce the impact of similar events in the future by: * Continuing to monitor system health and memory utilization in real time * Reviewing scaling strategies and resilience options as our infrastructure evolves * Applying lessons learned from this incident to ongoing platform improvements

Oct 3, 2025 · resolved Oct 3

**What happened?** 10/03/25 6:43 AM UTC Safeguard On-Demand Starling Edition that utilize Stargate connectivity dropped all connected clients.   **What went wrong and why?** The SSL Certificate used in the Safeguard On-Demand Starling Edition environments that was set to expire soon was renewed and placed into production.  While this new certificate functioned without issue with all other resources it was applied to, it was not tolerated well by the One Identity Safeguard Agent used on Windows servers.  The Sectigo Root CA that was on the certificate was unfortunately not included by default in the Windows Trusted Root Authorities store of the hosts.     **How did we respond?** The Safeguard On-Demand Starling Edition environments were rolled back to use the prior certificate.  We have renewed the certificate utilizing another Certificate Authority. We have applied that new certificate and validated One Identity Safeguard Agent functionality.   **How are we making incidents like this less likely or less impactful?** Our team will be moving away from our prior 3rd party certificate provider and using a new Certificate Authority.  We will be automating the SSL Certificate workflow to expedite certificate creation. We will be making changes to improve our pre-production testing process to ensure certificate changes are tolerated by the One Identity Safeguard Agent on supported platform versions.