Microsoft Outlook and 365 hit by global outage
Spotted 2026-11-13 03:07 (UTC+8) · original event 2026-11-12 · sources: Hacker News, Microsoft 365 Status (official), Downdetector, USA Today, Times Now · spreading on 4+ platformsHeat score
Rank score: 6040% — where it sits on the charts
Discussion score: 10040% — how much people are talking about it
Cross-platform score: 7020% — how many platforms it spread to
Composite heat score:58.0rank × 0.4 + discussion × 0.4 + cross-platform × 0.2 — includes a -20-point cooling decay (peak passed, attention fading).
Why it matters
Email is infrastructure until it stops; one Azure-linked failure locks millions out of work mail, calendars and files at once.The angle
The scale in numbers (128k Downdetector reports) and what Microsoft actually said; what breaks when Exchange Online goes downSuggested format: Short video · for General public, office workers, IT adminsEvidence chain
• HN #4 Ask HN 133 pts/45 cmt + HN #5 99 pts/26 cmt (2026-11-13, same event merged)• Downdetector: Outlook reports passed 80,000 by 1:10pm ET, ~128,000 by 1:20pm ET Nov 12• Microsoft 365 Status on X: investigating Exchange Online mailbox access issues in the Americas, incident EX1550543• Teams, OneDrive, Copilot, Microsoft Store also hit• Microsoft's own status page also down• 2026-11-13 04:07 update: HN #7, 198 pts/61 cmt + Ask HN #8, 257 pts/129 cmt• Ynet 2026-11-12: service restored after ~1 hr• no full root cause published yet• Downdetector peak ~128,874 reports• 2026-11-13 05:07 update: Ask HN #2, 328 pts/171 cmt + HN #21 Microsoft status quote, 9 pts• same Nov 12 incident (MO1550821/EX1550543, began 1:26 PM ET Nov 12)• Microsoft: elevated load from servers unexpectedly unavailable, NOT a traffic surge• separate Teams incident TM1550488 earlier Thursday• Downdetector ~128,874 Outlook reports peak• 2026-11-13 06:07 update: HN #7 'Service degradation on Microsoft 365' post, 302 pts/316 cmt• same Nov 12 incident (EX1550543/MO1550821), still unresolved as of 4:31 p.m. ET Nov 12 per Microsoft status• Microsoft: servers unexpectedly unavailable, not a traffic surge• no root cause named yet• BleepingComputer/WebProNews corroboration• 2026-11-13 07:07 update: HN #7 'Service degradation on Microsoft 365' post, 374 pts/364 cmt• same Nov 12 incident (EX1550543/MO1550821)• 2026-11-13 08:07 update: HN #7 'Service degradation on Microsoft 365' post, 432 pts/413 cmt• same Nov 12 incident (EX1550543/MO1550821)• 2026-11-13 09:07 update: HN #7 'Service degradation on Microsoft 365' post, 474 pts/442 cmt• same Nov 12 incident (EX1550543/MO1550821)• 2026-11-13 10:07 update: HN #9 'Service degradation on Microsoft 365' post, 520 pts/474 cmt• recovery into Nov 13, still not fully restored (EX1550543/MO1550821)• servers failed health checks, not a traffic surge• no full root cause yet• 2026-11-13 11:07 update: HN #10 'Service degradation on Microsoft 365' post, 559 pts/522 cmt• 2026-11-13 12:07 update: HN #11 'Service degradation on Microsoft 365' post, 608 pts/571 cmt• 2026-11-13 13:07 update: HN #10 'Service degradation on Microsoft 365' post, 652 pts/612 cmt• recovery into day 2 (2026-11-13): partial restoration, some servers back and stable, no full root cause published• Downdetector peak ~138k Outlook reports, 74 countries• 2026-11-13 14:07 update: HN #13 'Service degradation on Microsoft 365' post, 689 pts/648 cmt• search check 2026-11-13: still not fully resolved, gradual recovery• Microsoft says config updates a potential cause, no cyberattack indication• Downdetector peak ~138k Outlook reports, down to ~34.5k by Thu evening• outage also hit OpenAI/Anthropic connectors (Reuters)• 2026-11-13 15:07 update: HN #14 'Service degradation on Microsoft 365' post, 744 pts/679 cmt• HN #30 CNN live blog 'Global Microsoft Outage' (10 pts, same Nov 12 event)• 2026-11-13 16:07 update: HN #12 'Service degradation on Microsoft 365' post, 810 pts/713 cmt• HN #15 'Outlook/365 still down after 12 hours' (81 pts, same Nov 12 event)• HN #16 CNN live blog 'Global Microsoft Outage' (39 pts)• search corroboration 2026-11-13: still not fixed as of ~12:45 IST, restored servers go unresponsive again under traffic, partial recovery only, no root cause, no cyberattack• 2026-11-13 17:07 update: HN #12 'Service degradation on Microsoft 365' post, 855 pts/757 cmt• HN #11 'Outlook/365 still down after 12 hours' (166 pts, same Nov 12 event)• HN #17 CNN live blog 'Global Microsoft Outage' (65 pts, same event)• search corroboration 2026-11-13: still 'service degradation' as of 08:50 GMT, gradual recovery, no full root cause, no cyberattack• 2026-11-13 18:07 update: HN #13 'Service degradation on Microsoft 365' post, 886 pts/779 cmt• HN #12 'Outlook/365 still down after 12 hours' (265 pts/169 cmt, same Nov 12 event)• HN #17 CNN live blog 'Global Microsoft Outage' (89 pts, same event)• HN #29 'Microsoft says attempts to fix not going as expected' (46 pts, same event)• search corroboration 2026-11-13: still not fixed as of ~12:45 IST, Microsoft says fixes 'not taking as expected', alternate work streams, mail timeout extended to 48h, early stabilization signs, no cyberattack, no full root cause yet• 2026-11-13 19:07 update: HN #15 'Service degradation on Microsoft 365' post, 927 pts/803 cmt• HN #17 CNN live blog 'Global Microsoft Outage' (198 pts/38 cmt, same Nov 12 event)• HN #21 'Outlook/365 still down after 12 hours' (327 pts/232 cmt, same event)• search corroboration 2026-11-13: still 'service degradation' as of 08:50 GMT, Microsoft reported positive results for server stability after patching part of infrastructure, no time for full recovery, no root cause yet• one report cited access restored 05:33 UTC but official status still showed degradation at 08:50 GMT, so partial recovery only• 2026-11-13 20:07 update: HN #14 'Service degradation on Microsoft 365' post, 965 pts/828 cmt• HN #17 CNN live blog 'Global Microsoft Outage' (161 pts/86 cmt, same Nov 12 event)• HN #20 'Outlook/365 still down after 12 hours' (356 pts/250 cmt, same event)• search corroboration 2026-11-13: still 'service degradation' as of 12:45 IST / 06:17 UTC, partial recovery only, no root cause, no full-restoration timeline, email timeout extended to 48h• 2026-11-13 21:07 update: HN #14 'Service degradation on Microsoft 365' post, 1007 pts/848 cmt• HN #21 CNN live blog 'Global Microsoft Outage' (194 pts/110 cmt, same Nov 12 event)• HN #25 'Outlook/365 still down after 12 hours' (385 pts/268 cmt, same event)• 2026-11-13 22:08 update: HN #17 'Service degradation on Microsoft 365' post, 1043 pts/872 cmt• HN #23 CNN live blog 'Global Microsoft Outage' (218 pts/127 cmt, same Nov 12 event)• 2026-11-13 23:08 update: HN #20 'Service degradation on Microsoft 365' post, 1070 pts/888 cmt• HN #26 CNN live blog 'Global Microsoft Outage' (246 pts/147 cmt, same Nov 12 event)• 2026-11-14 00:07 update: HN #24 'Service degradation on Microsoft 365' post, 1083 pts/914 cmt• CNN live blog dropped out of HN top 30 this round• 2026-11-14 01:07 update: HN #27 'Service degradation on Microsoft 365' post, 1100 pts/932 cmt• 2026-11-14 02:07 update: HN #29 'Service degradation on Microsoft 365' post, 1123 pts/946 cmt• 2026-11-14 03:07 update: out of HN top 30 this round• 2026-11-14 04:07 update: The Register 2026-11-13 'Microsoft outage gives customers a crash course in dependence on Redmond' (HN #27, 21 pts), same 11-12 outage, merged not new row• row stays cooling• 2026-11-14 05:07 update: The Register 2026-11-13 outage follow-up (HN #26, 48 pts), same 11-12 outage, merged not new row• row stays cooling• 2026-11-14 06:07 update: HN #28 'Microsoft outage gives customers a crash course in dependence on Redmond' (76 pts), same 11-12 outage, merged not new row• row stays cooling• 2026-11-14 08:08 update: HN #25 'Microsoft outage gives customers a crash course in dependence on Redmond' (112 pts/37 cmt, The Register 2026-11-13), same 11-12 outage, merged not new row• row stays cooling• 2026-11-16 23:07 update: The Register 2026-11-16: Microsoft blames the outage on a software defect introduced in a July fix (HN #26, 21 pts/19 cmt, 50517321), same Nov 12-13 Microsoft 365 outage, merged not a new row• cooling row, score unchanged 58.0