Microsoft Azure

False positive — monitoring-location network issue, not a service outage. Platform probes reported 4 consecutive timeouts (N/A, 10s) from the primary monitoring location, but an independent direct check with a browser user-agent returns HTTP 200 for https://azure.microsoft.com, and third-party status aggregators (Entireweb, Instatus, IsDown, UptimeRobot) show Azure operational with no user reports. Resolved as not-a-real-outage.

False positive: probe recorded repeated 10s timeouts through 11:20-15:34 UTC but a direct check from outside the probe network returned HTTP 200 (slow, ~5-7s, typical for this page), confirming the site was reachable. Failure was on the probe path, not the service.

Resolved 2026-10-23: Microsoft announced Azure services restored to near-normal after the Oct 21 global outage (Azure Front Door impact). Fresh probe at 14:43 UTC returns HTTP 301 (operational), and independent status trackers (azuredown.com, isdown.app, statusgator) report all services operational as of Oct 23.

Service recovered. Resolved by admin via MCP.

False positive — verified healthy by direct browser-UA checks (all HTTP 200, normal pages); no outage reports or news; all three incidents fired within the same second on probe-side timeouts/redirect quirks, indicating a probe-infrastructure artifact, not a real outage. Auto-monitor will re-open if probes fail again.