Incidents

Azure-related incidents from the last 90 days, comparing early-warning detection with the first customer report.

Incidents (90 days)

Detected before customer report

6 / 8

Median lead time

2h 08m

Detected late or missed

Incident history

Incident	Severity	Region	Indicator	Clusters	Customer reported (UTC)	Lead time	Root cause
INC-2026-0412 Managed-disk throttling on zone 1 disk cohort	Sev1	East US 2eastus2	Storage / Data-Path	3	Sep 28, 2026 09:05	+2h 25m	Azure storage scale unit degradation (Microsoft confirmed, tracking ID 7KQ2-1PX)
INC-2026-0398 L32s_v3 allocation failures during scale-out	Sev2	West Europewesteurope	Compute Capacity & Provisioning	1	Sep 19, 2026 14:20	+1d 22h	Regional capacity constraint for the L-series SKU in zone 2
INC-2026-0377 Unplanned host reboot after platform maintenance	Sev2	East US 2eastus2	Azure Platform Events	2	Sep 8, 2026 03:40	+3h 10m	Host maintenance overran its window; VMs redeployed
INC-2026-0361 Cross-AZ packet loss on service-to-storage path	Sev3	Southeast Asiasoutheastasia	Network / Connectivity	1	Aug 30, 2026 11:15	+0h 35m	Degraded inter-zone link, resolved by Microsoft networking
INC-2026-0344 Storage account latency spike	Sev3	Central UScentralus	Storage / Data-Path	1	Aug 21, 2026 16:50	−0h 20m	Short-lived partition server failover
INC-2026-0329 Shared storage latency across four clusters	Sev1	East US 2eastus2	Customer Impact (Cross-Cluster)	4	Aug 12, 2026 13:30	+1h 50m	Common storage scale unit behind four independent clusters
INC-2026-0310 DNS resolution delays in region	Sev2	West US 2westus2	Azure Platform Events	2	Jul 30, 2026 08:00	+1h 05m	Azure DNS incident announced via Service Health
INC-2026-0296 ExpressRoute circuit flaps to customer site	Sev2	North Europenortheurope	Network / Connectivity	1	Jul 18, 2026 10:25	Not detected	Customer-side ExpressRoute provider issue, outside probe coverage

Lead time is how long before the first customer report the early-warning risk reached High or Critical. Negative values were detected after the report.