Solventum Outage History

Beginning on Monday, 2026-10-05 infrequent, intermittent failures during federated authentication have been observed: end-users see a white screen while waiting for a https://cloudservices.solventumhsp.com URL to load. This URL is used by all Solventum applications, including managed deployments of 360 Encompass (360Eitc) and CRS (CITC). Generally, this can be resolved by trying again. Beginning at approximately 14:00 Eastern on Friday, 2026-10-09, however, the frequency of these timeouts has begun to increase and end-users are more likely to encounter them.

Beginning around 14:30 Eastern, automated application monitoring began to report login failures at a high right. On-call teams are investigating.

To help prevent unexpected outages for CitC sites hosted at https://pe5.citc.solventum.com, Managed Services Operations will perform maintenance this evening starting at 9:00 PM Eastern. During this time, AWS will be applying automated infrastructure updates. To minimize the risk of service interruption, CitC services at https://pe5.citc.solventum.com will be proactively managed. The maintenance is expected to last approximately 1 hour. Thank you for your understanding.

Automated application monitoring for managed deployments indicates end-users may be unable to authenticate into managed deployments of 360Eitc and CITC.

At approximately 10:12 Eastern, automated application alerts began to fire, indicating that end-user access to Solventum-managed deployments was affected. On-call response teams are investigating an issue affecting all services that use federated authentication, including service and API endpoints.

CoreSTS (including IdP) services appear to be experiencing an outage. This may prevent end-users from authenticating into managed deployments of 360 Encompass and CRS.

The scope of this issue has been confirmed to include the ServiceNow Support website as well. Other services may be affected, resulting in unexpected or incomplete functionality (e.g. error messages) affecting applications width cloud dependencies such as 360 Encompass and CRS. End-users are not able to authenticate into managed deployments. On-call resources have been alerted and are investigating.

Microsoft has published an incident on their Azure status page: https://azure.status.microsoft/en-us/status >Starting at approximately 16:00 UTC, customers and Microsoft services leveraging Azure Front Door (AFD) may have experienced latencies, timeouts, and errors. We have confirmed that an inadvertent configuration change was the trigger event for this issue. This can affect any end-user attempting to federate into a third-party (e.g. Solventum) application. End-users may observe: - They see the Solventum login screen - Enter an email/username - Are redirected to a white screen (instead of Microsoft login)

MSO is currently investigating an apparently wide-spread issue where the North America/US Solventum sign-in page ("We never stop solving for you") loads extremely slowly or does not finish loading, preventing end-users from authenticating into applications.

The 25.5.20.n release of 360 Encompass includes changes to CRS/Codefinder that may cause certain types of integrated session launches to fail. Support and development teams are investigating root cause and developing workarounds. This incident will be updated when RCA is finalized and a general remediation is developed.

The Solventum foundation services team is investigating an issue where end-users who use Solventum-managed identities (sometimes called "password users") are unable to sign into managed systems (CRSitc, 360Etic).

Following the application of the 25.2.10.0 release on Wednesday, 2025-03-07, some sites reported that CDI Evidence Sheets failed to return results. Instead, they show an error message: "Associated Evidence cannot be displayed errors affecting some sites". This issue does NOT affect all sites and, in some cases, has been resolved by restarting the 360 Encompass system (i.e. SWARI reboot). The root cause and scope of the issue are not well understood at this time, however, so no formal KPI exists. This incident will be updated as more information becomes available.