movingimage incident
LiveStream Pro – lspro.movingimage.com not reachable
movingimage experienced a critical incident on October 29, 2025 affecting LSPro, lasting 7h 4m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 29, 2025, 04:03 PM UTC
Dear movingimage Users, We are investigating an issue that is affecting the movingimage platform. The affected services are listed below this email, and on our status page. When we have further information or a resolution on this issue, we will post an update on the status page. Thank you for your understanding. If you have any questions, feel free to get in contact with us. Your movingimage Team
- identified Oct 29, 2025, 05:02 PM UTC
The underlying root cause for the outage is an ongoing incident on Azure side which is also affecting our services: https://azure.status.microsoft/en-us/status As soon there is an update we will let you know.
- identified Oct 29, 2025, 05:18 PM UTC
Issue is identified as Azure global outage of the various services. As Azure is still not reporting DNS outage on their status page, we're affected as many other people around the globe. We are continuing to monitor situation and will act accordingly.
- identified Oct 29, 2025, 06:40 PM UTC
We got informed from Azure that issue is with Azure CDN (Azure Front Door). Full notification message from the Azure can be found below: --------------------- 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. Current status: We have initiated the deployment of our last known good configuration, which is expected to complete within 30 minutes. As this deployment progresses, customers should begin to see initial signs of recovery. Once completed, we will begin recovering nodes and routing traffic through these healthy nodes. Customer configuration changes will remain temporarily blocked while we continue mitigation efforts. We will notify customers once this block has been lifted. Some customers may also have experienced issues accessing the Azure management portal. We have failed the portal away from AFD to mitigate these access issues. Customers should now be able to access the Azure portal directly, and while most portal extensions are functioning as expected, a small number of endpoints (e.g., Marketplace) may still experience intermittent loading problems. We do not yet have an ETA for full mitigation, but we will provide another update within 30 minutes, once the deployment has completed. Customers may also consider implementing failover strategies using Azure Traffic Manager to redirect traffic from Azure Front Door to their origin servers as an interim measure. This message was last updated at 18:24 UTC on 29 October 2025
- monitoring Oct 29, 2025, 09:01 PM UTC
Dear movingimage Users, We are pleased to inform you that the identified issue is now mitigated. The affected services listed below are being monitored. Thank you for your understanding. If you have any questions, feel free to get in contact with us. Your movingimage Team
- resolved Oct 29, 2025, 11:08 PM UTC
Dear movingimage Users, We are pleased to inform you that the identified issue is now resolved. The restored services are listed below. Here you will find the current status and a summary of the root cause on Azure side: https://azure.status.microsoft/en-us/status Thank you for your understanding. If you have any questions, feel free to get in contact with us. Your movingimage Team