LMS365 experienced a notice incident on April 5, 2024 affecting Learn365 United Kingdom, lasting 2h 57m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Apr 05, 2024, 12:55 PM UTC
Microsoft is currently working on an issue impacting Azure services in UK regions. As per Microsoft: Impact Statement: Starting at 08:50 UTC on 05 Apr 2024, customers using Azure services which have dependencies on Azure Front Door may experience degraded performance, latency or timeouts when attempting to access services hosted in the UK South region. Current Status: We have identified an issue with load balancing which have affected traffic between services. We are currently working on applying mitigation steps to resolve this issue. An update will be provided in 60 minutes, or as events warrant. This incident may impact LMS365 customers whose tenants are provisioned in the UK region and lead to longer response times.
- resolved Apr 05, 2024, 03:53 PM UTC
As per Microsoft: What happened? Between 08:50 UTC and 13:18 UTC on 05 Apr 2024, customers using Azure services which have dependencies on Azure Front Door may have experienced intermittent degraded performance, latency or timeouts when attempting to access services hosted in the UK South region. What do we know so far? We identified that an issue with load balancing of traffic between Azure Front Door Points of Presence (PoP)s, causing degraded performance, latency or timeouts. How did we respond? 08:50 UTC on 05 April 2024 – Customer impact began. 09:05 UTC on 05 April 2024 – Service monitoring detected high latency or timeout spikes in the UK South region. 11:45 UTC on 05 April 2024 – We identified that an issue with load balancing was affecting traffic between Azure Front Door Points of Presence (PoP) in UK South Region. 12:15 UTC on 05 April 2024 – We performed configuration changes in order to adjust load balancing, which resolved this issue. 13:18 UTC on 05 April 2024 – After monitoring, our telemetry confirmed that the issue was mitigated and full service functionality was restored. What happens next? Our team will be completing an internal retrospective to understand the incident in more detail. We will publish a Preliminary Post Incident Review (PIR) within approximately 72 hours, to share more details on what happened and how we responded. After our internal retrospective is completed, generally within 14 days, we will publish a Final Post Incident Review with any additional details and learnings.