Resolved -
This incident has been resolved.
Oct 29, 19:21 CDT
Update -
Microsoft is reporting node repairs are complete and performance should have returned to normal. Internally, we have been seeing consistent performance in production environments
Oct 29, 19:12 CDT
Update -
Microsoft is continuing their node recovery process. Some requests may continue to experience intermittent failures until more nodes are restored. Microsoft estimates recovery will finish at 23:20 UTC on 29 October 2025.
Oct 29, 17:04 CDT
Update -
We are starting to see users able to login and navigate the site. We'll continue to monitor until Microsoft says the issue has been fully resolved.
Oct 29, 15:29 CDT
Update -
Microsoft is continuing to recover nodes and route traffic through healthy nodes. Our backend systems are beginning to come back online. You may start to see notifications and services returning as they are restored. We’re continuing to monitor progress and will provide an update once the platform is fully stable.
Oct 29, 14:49 CDT
Monitoring -
An update from Microsoft: "We have pushed our ‘last known good’ configuration, and customers may begin to see initial signs of recovery. We are currently recovering nodes and routing traffic through healthy nodes, and as we make progress in this workstream, customers will continue to see improvement."
We will continue to monitor our services and notify you when they become available again.
Oct 29, 14:08 CDT
Update -
Microsoft has initiated a deployment to fix the configuration issues, "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."
Oct 29, 13:39 CDT
Update -
Microsoft continues to work on the issue but does not have an ETA yet.
Oct 29, 13:02 CDT
Update -
Microsoft has identified the problem and is working on rolling the change back to its "last known good state". No ETA yet but we hope to have an update within 30 minutes.
Oct 29, 12:30 CDT
Update -
An update from Microsoft: "We are actively assessing failover options of internal services from our AFD infrastructure. Our investigation into the contributing factors and additional recovery workstreams continues. More information will be provided within 60 minutes or sooner."
Oct 29, 12:00 CDT
Update -
Microsoft has provided an update: "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."
Oct 29, 11:36 CDT
Update -
Microsoft has acknowledged the issue and is currently investigating.
Oct 29, 11:22 CDT
Identified -
Microsoft Azure is experiencing an outage which is affecting all of our services. We are monitoring the situation and will provide updates as we receive them from Microsoft.
Oct 29, 11:02 CDT
Investigating -
We are seeing issues with uwpipeline.com. We are currently investigating and will provide updates soon.
Oct 29, 10:54 CDT
