Problems loading Displayr

We have observed that all Azure Front Door (AFD) instances used by Displayr have now recovered.

Microsoft continues to roll out fixes to all customers. However based on their advice since our specific Azure Front Door instances have now recovered they should continue to operate reliably. The incident is now resolved for Displayr.

"The AFD service is now operating above 98% availability. While the majority of customers and services are mitigated or seeing strong improvement across affected regions, we are continuing to work on tail-end recovery for remaining impacted customers and services. We have revised our mitigation time and are currently tracking toward full mitigation by 00:40 UTC on 30 October 2025, though we will communicate if mitigation is achieved sooner."

https://azure.status.microsoft/en-us/status

Systems are recovering more widely. You should be able to log in and edit or view documents, and also visualizations now work.

There are still intermittent issues. Occasionally you may still see "Parts of this web page have failed to load" however it should occur less often.

The status from Azure has not changed, and we expect a full recovery by 23:20 UTC on 29 October 2025.

We are seeing systems recover. You should be able to log in and edit or view documents.

However, there are still issues with specific systems. In particular, you may not be able to view visualizations as these also have a reliance on Azure Front Door and are still experiencing issues.

The status from Azure has not changed, and we expect a full recovery by 23:20 UTC on 29 October 2025.

Microsoft has issued another update with an expected resolution time:

"At this stage, we anticipate full mitigation within the next four hours as we continue to recover nodes. This means we expect recovery to happen by 23:20 UTC on 29 October 2025. We will provide another update on our progress within two hours, or sooner if warranted."

https://azure.status.microsoft/en-us/status

Microsoft has found the issue is related to a bad change to Azure Front Door (the CDN that Displayr uses) and is rolling back to a last good configuration.

"Starting at approximately 16:00 UTC, we began experiencing Azure Front Door (AFD) issues resulting in a loss of availability of some services. We suspect that an inadvertent configuration change as the trigger event for this issue. We are taking two concurrent actions where we are blocking all changes to the AFD services and at the same time rolling back to our last known good state.

We have failed the portal away from AFD to mitigate the portal access issues. Customers should be able to access the Azure management portal directly.

We do not have an ETA for when the rollback will be completed, but we will update this communication within 30 minutes or when we have an update."

Displayr continues to be affected.

The latest status update from Microsoft Azure indicates a broad issue with DNS that they are investigating and are starting to take mitigation actions.

"Starting at approximately 16:00 UTC, we began experiencing DNS issues resulting in availability degradation of some services. Customers may experience issues accessing the Azure Portal. We have taken action that is expected to address the portal access issues here shortly. We are actively investigating the underlying issue and additional mitigation actions. More information will be provided within 60 minutes or sooner."

https://azure.status.microsoft/en-us/status

There appears to be an issue with Azure Front Door, a CDN used by Displayr. This affects all geographic regions and will result in the following message appearing in Displayr: "Parts of this web page have failed to load due to a problem with your Internet connection."

Microsoft has acknowledged an issue and is starting investigation: https://azure.status.microsoft/en-us/status

We are currently investigating this issue.