Incidents reported on status page for Omnidocs https://status.omnidocs.cloud/ https://d1lppblt9t2x15.cloudfront.net/logos/d85f1762dc43a7283dc28182e406131a.png https://status.omnidocs.cloud/ en https://status.omnidocs.cloud/incident/784493 Thu, 11 Dec 2025 11:16:00 -0000 https://status.omnidocs.cloud/incident/784493#de70f1c31e017dc67bd5b986b036468d3c91eaac5ba4b75c2d013b1aa379fe53 All systems were reported operational once again at 11.16 UTC. We have now flagged the key oversights in the process that got us here, and are going to be implementing the necessary changes to minimize the risk going forward. Once again, we’re truly sorry for the disruption this has caused to your operations, and thank you kindly for your patience. https://status.omnidocs.cloud/incident/784493 Thu, 11 Dec 2025 10:39:00 -0000 https://status.omnidocs.cloud/incident/784493#e389bd16ff6352b4530229d3588beb476b0219f89206136348291a253d214136 On December 11, 2025 at 10.39 UTC, a series of our SSL Certificates expired, resulting in the prompt interruption of most of our core services through the inability to securely connect to them over HTTPS. This caused customers to experience browser security warnings or failed SSL / HTTPS connections on their systems. The team was alerted of and able to correct the failing certificates quickly, but propagation through our infrastructure took longer than expected, which dreadfully extended the downtime period and, more importantly, the impact for our customers. Apologies for the disruption this has caused to your operations, and thank you kindly for your patience.