InkSoft incident

CDN Not working

Critical Resolved View vendor source →

InkSoft experienced a critical incident on October 29, 2025 affecting Order Manager and Proposals and 1 more component, lasting 1d 4h. The incident has been resolved; the full update timeline is below.

Started
Oct 29, 2025, 03:56 PM UTC
Resolved
Oct 30, 2025, 07:59 PM UTC
Duration
1d 4h
Detected by Pingoru
Oct 29, 2025, 03:56 PM UTC

Affected components

Order ManagerProposalsCRMProductionPurchasingStoresOnline Designer

Update timeline

  1. investigating Oct 29, 2025, 03:56 PM UTC

    We are currently investigating issues with our CDN Network.

  2. investigating Oct 29, 2025, 04:09 PM UTC

    We are still investigating the issue, but it seems like Azure is having some issues right now. https://downdetector.com/status/windows-azure/

  3. identified Oct 29, 2025, 04:28 PM UTC

    The issue has been identified and a fix is being implemented.

  4. monitoring Oct 29, 2025, 04:34 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. monitoring Oct 29, 2025, 04:44 PM UTC

    Azure is still experiencing issues (https://azure.status.microsoft/en-us/status), but we were able to implement an ad-hoc fix to mitigate the problem.

  6. resolved Oct 30, 2025, 07:59 PM UTC

    On October 29 at approximately 16:00 UTC, we identified an issue affecting static content delivery through Azure’s CDN service. Our investigation determined that a third-party vendor outage—caused by a DNS issue with their cloud provider—was the root cause. An ad-hoc workaround was implemented by 16:40 UTC, which restored platform availability while Azure continued to work on a permanent fix. Azure has since resolved the underlying issue on October 30, 2025 00:05 AM, and we have safely removed our temporary workaround.