Sending, receiving, and organizing email in Outlook.com
The current failure coincides with Microsoft’s November 12, 2026 service degradation, so stop device-level troubleshooting and wait until the public service-status page reports recovery before trying Outlook.com again.^1^
What to do now
- Monitor Service Health Status for Microsoft 365 and Outlook availability.^1^
- Once the incident is shown as resolved, wait several minutes and attempt one fresh Outlook.com sign-in.
- If necessary, use a private/InPrivate browser window only for that post-recovery test, so an existing failed session is not reused.
The BootResult: network, Failed to fetch, and StartupData entries indicate that Outlook Web could not retrieve the data required to start. Because the same account fails across all your devices during a reported service degradation, reinstalling applications, resetting devices, or repeatedly changing passwords is not an appropriate next step.
Microsoft’s Outlook.com known-issues guidance also directs users who cannot access Outlook.com to the public service-status page.^2^
If it still fails after Microsoft reports recovery
If the status page is healthy but the mailbox continues producing the same error across multiple devices and networks:
- Go to the Microsoft Support contact page: https://support.microsoft.com/en-us/home/contact
- Select Get Home Support.
- Enter Outlook.com or Hotmail.
- Select Contact support.
- Provide:
- The UTC timestamp
- Client ID and Session ID
-
BootResult: network -
esrc: StartupData -
TypeError: Failed to fetch - Confirmation that it occurs on multiple devices
This route is the documented fallback used for persistent Outlook.com startup failures that require account or mailbox investigation.^3^
Do not post new Client IDs or Session IDs publicly; provide them only through Microsoft’s support channel.
References