Sending, receiving, and organizing email in Outlook.com
The most likely immediate resolution is to wait for Microsoft’s current Outlook service disruption to clear and monitor the Microsoft Service Health Status page, because widespread Outlook access failures were reported on November 13, 2026.^1^
What to do now
- Check the Microsoft Service Health Status site. Microsoft directs Outlook.com users there when they cannot access the service.^2^
- If Outlook is shown as degraded, no local repair is required. Retry after Microsoft marks the incident resolved.
- Do not repeatedly reset your password unless Microsoft reports an authentication problem. Your message shows Outlook Web failing to retrieve its startup data (
BootResult: networkandFailed to fetch), not an explicit incorrect-password error.
If service health shows no incident
Determine whether the failure is local:
- Open Outlook.com in an InPrivate/Incognito window.
- If that works, disable ad-blocking extensions such as AdBlock or uBlock, then clear the Outlook/Microsoft site cookies in the normal browser session. Microsoft notes that these blockers can prevent Outlook.com from loading.^3^
- Update and test with a supported current browser:
- Windows: Edge, Firefox, or Chrome
- macOS: Edge, Safari 16 or later, Firefox, or Chrome
- Test from another device and another connection, such as a phone using mobile data rather than the same Wi-Fi.
- Works on mobile data: investigate the original network, DNS filtering, VPN, proxy, or firewall.
- Fails on multiple devices and unrelated networks: the problem is more likely with the service or mailbox than with one browser.
If it continues after the outage is resolved
Use Microsoft’s sign-in troubleshooter if the Microsoft account itself cannot sign in.^4^
If the account signs in elsewhere but the mailbox still fails on multiple browsers, devices, and networks, contact Outlook.com support using Microsoft’s can’t sign in support route. Include:
- The UTC timestamp
- Client ID and Session ID
-
BootResult: network -
esrc: StartupData -
TypeError: Failed to fetch - The browsers, devices, and networks tested
Do not post the session and client identifiers publicly again; provide them only in the private Microsoft support case.
References