ServiceNow root certificate error leaves users high and dry
Briefly

ServiceNow has identified an expired SSL Root certificate that is affecting MID Server and instance-to-instance connectivity, impacting integrations and orchestrations.
It would be nice if they actually notified all impacted customers (basically everyone) before I page out several other teams while waiting on SN to pick up my ticket.
After confirming there was no network or host issues, I called SN and they told me about the issue, and another 90 minutes before they linked my CASE to the outage.
The certificate expiration error was flagged with ServiceNow two weeks ago, but the certificate replacement job was botched, leading to widespread disruption.
Read at Theregister
[
]
[
|
]