One Identity Starling had 8 outages in the last 2 years totaling 397h 0m of downtime — averaging 0.3 incidents per month.
There were 8 One Identity Starling outages since August 11, 2025 totaling 397h 0m of downtime. Each is summarised below — incident details, duration, and resolution information.
The "Recent Connector Logs" page is not properly displaying log data. The issue has been identified and we are working towards a resolution. We will update this page as we progress towards resolution.
A fix has been implemented and issue has been resolved.
Since 12:09 UTC October 21, Starling One Identity Connect services may have degraded performance, due to a 3rd party component that we depend on is experiencing an outage in the West US region. We are actively monitoring the issue. All further updates will be posted here on our status page.
Microsoft has confirmed that the issue is now resolved. We are currently monitoring the system to ensure stability and verify that no residual impact remains.
This incident has been resolved.
Message: OneLogin Engineers have identified an issue; some customers may be experiencing degraded performance that might delay service response time. We are working to quickly restore service. Current Status: Degraded Performance Started: September 4, 2025 11:32PM PDT
[Investigating] OneLogin Engineers have identified an issue; some customers may be experiencing degraded performance that might delay service response time. We are working to quickly restore service.
[Investigating] OneLogin Engineers have mitigated the issue while they investigate the root cause. Customers should now find that Smart Hook errors have been resolved.
[Monitoring] Engineers have resolved the issue are are currently monitoring.
[Resolved] OneLogin Engineers have resolved the issue.
We are investigating issue with Starling Cloud Assistant not sending messages. We will provide regular updates as the investigation/resolution progresses.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This issue has been resolved, all functionality should be back to normal at this time.
**What happened?** 08/21/25 6:43 AM UTC Functionality of Starling Cloud Assistant US/EU was interrupted. **What went wrong and why?** The client secrets used by the Cloud Assistant application expired. This caused the Cloud Assistant apps in Prod US and EU to fail authentication thus interrupting functionality. Automated emails are used to notify our product teams of upcoming secret expiries and to take action. This email notification was mis-processed by our internal team, so the corresponding work items were not created or performed. **How did we respond?** The secrets were updated and the Cloud Assistant applications were restarted, resolving issue. **How are we making incidents like this less likely or less impactful?** Our team is automating the email workflow to create a work item so that secret expiration notices are not missed in future.
Status update from OneLogin regarding MFA, Portal, Single Sign-On Service in EU Operating Region Message: OneLogin Engineers have identified an issue with Single Sign-On Services; some customers may be experiencing degraded performance. We are working to quickly restore service.
Status update from OneLogin regarding MFA, Portal, Single Sign-On Service in EU Operating Region We are continuing to investigate an issue impacting some customers relating to SSO.
Status update from OneLogin regarding MFA, Portal, Single Sign-On Service, PAM Essentials in EU Operating Region Message: We have identified a problem impacting SSO services and have implemented measures to resolve it. We will continue to monitor all services to ensure they are fully operational.
Message: Issue has been resolved, all services are fully operational.
This incident has been resolved.