"Microsoft said the latest Azure outage began at approximately noon ET on Oct. 29. However, Downdetector, which relies on user reports, showed the problems surfaced earlier, around 11:40 a.m. ThousandEyes, the Cisco network security company, " detected HTTP timeouts, server error codes, and elevated packet loss at the edge of Microsoft's network, preventing successful connections to affected services and frequently timing out or returning service-related errors.""
"However, Microsoft continued, "As recovery progresses, some requests may still land on unhealthy nodes, resulting in intermittent failures or reduced availability until more nodes are fully restored. This recovery effort involves reloading configurations and rebalancing traffic across a large volume of nodes to restore full operational scale. The process is gradual by design, ensuring stability and preventing overload as dependent services recover. We expect continued improvement across affected regions. This means we expect recovery to happen by 23:20 UT"
Microsoft Azure experienced a global outage beginning around noon ET on Oct. 29, with user reports indicating problems as early as 11:40 a.m. Customer-facing services were affected and monitoring showed HTTP timeouts, server error codes, and elevated packet loss at the network edge. Microsoft deployed a 'last known good' configuration, recovered nodes, and re-routed traffic through healthy nodes. Recovery involves reloading configurations and rebalancing traffic across many nodes to restore full operational scale, and is gradual by design to prevent overload. Intermittent failures and reduced availability persisted while nodes restored, with full recovery expected by 23:20 UT.
Read at ZDNET
Unable to calculate read time
Collection
[
|
...
]