Outlook.com: Personal Email Inaccessible Across Multiple Devices and Networks, HTTPS Connection Timeout

David Lamb 0 Reputation points
2026-11-12T20:27:58.3+00:00

My personal Outlook.com email account is inaccessible across multiple devices, including desktop computers, laptops, and mobile devices, using both local Wi-Fi networks and independent cellular data connections.

The Outlook.com website consistently returns ERR_TIMED_OUT, while the Outlook desktop application cannot connect, synchronize, send, or receive email.

The issue persists across different browsers, devices, and network connections, suggesting a potential Microsoft service-side or upstream connectivity problem rather than an isolated device or local network issue.

Troubleshooting Already Completed

  • Tested multiple browsers, including private/incognito mode.

Cleared browser cache and cookies.

Disabled browser extensions.

Restarted the computer.

Performed a Windows network reset.

Tested with TLS 1.3 post-quantum key agreement disabled.

Verified Outlook application settings.

Tested different devices and independent Wi-Fi and cellular connections.

Technical Diagnostic Results

DNS Resolution:

Resolve-DnsName outlook.live.com

DNS resolution succeeds through:

outlook.live.com → outlook.cloud.microsoft → fs.outlook.mira.tm.svc.cloud.microsoft

TCP Connectivity:

Test-NetConnection outlook.live.com -Port 443

Multiple IPv6 TCP connection failures.

Inconsistent IPv4 TCP connectivity.

One Microsoft IPv4 endpoint initially accepted a connection, but subsequent attempts timed out.

HTTPS Testing:

curl.exe -4 -I --connect-timeout 10 https://outlook.live.com/mail/
curl.exe -6 -I --connect-timeout 10 https://outlook.live.com/mail/

Both returned:

curl: (28) Connection timed out after approximately 10 seconds

Forced IPv4 testing against a previously reachable Microsoft endpoint also timed out before TLS negotiation.

Proxy Configuration:

No WinHTTP proxy or proxy environment variables detected.

Additional Information

Microsoft reported Microsoft 365 service degradation on November 12, 2026. It remains unclear whether this incident also affects personal Outlook.com accounts.

Question for Microsoft Support

Is Microsoft experiencing a consumer Outlook.com service disruption, regional routing failure, or infrastructure issue causing HTTPS connectivity timeouts across multiple device types and independent networks?

Can Microsoft confirm whether the reported Microsoft 365 service degradation also affects personal Outlook.com accounts?

If no outage is confirmed, what service-level diagnostics or escalation procedures are available?

Please consider the troubleshooting already completed before recommending repeated browser resets, network resets, or other basic client-side troubleshooting.My personal Outlook.com email account is inaccessible across multiple devices, including desktop computers, laptops, and mobile devices, using both local Wi-Fi networks and independent cellular data connections.

The Outlook.com website consistently returns ERR_TIMED_OUT, while the Outlook desktop application cannot connect, synchronize, send, or receive email.

The issue persists across different browsers, devices, and network connections, suggesting a potential Microsoft service-side or upstream connectivity problem rather than an isolated device or local network issue.

Troubleshooting Already Completed

Tested multiple browsers, including private/incognito mode.

Cleared browser cache and cookies.

Disabled browser extensions.

Restarted the computer.

Performed a Windows network reset.

Tested with TLS 1.3 post-quantum key agreement disabled.

Verified Outlook application settings.

Tested different devices and independent Wi-Fi and cellular connections.

Technical Diagnostic Results

DNS Resolution:

Resolve-DnsName outlook.live.com

DNS resolution succeeds through:

outlook.live.com → outlook.cloud.microsoft → fs.outlook.mira.tm.svc.cloud.microsoft

TCP Connectivity:

Test-NetConnection outlook.live.com -Port 443

Multiple IPv6 TCP connection failures.

Inconsistent IPv4 TCP connectivity.

One Microsoft IPv4 endpoint initially accepted a connection, but subsequent attempts timed out.

HTTPS Testing:

curl.exe -4 -I --connect-timeout 10 https://outlook.live.com/mail/
curl.exe -6 -I --connect-timeout 10 https://outlook.live.com/mail/

Both returned:

curl: (28) Connection timed out after approximately 10 seconds

Forced IPv4 testing against a previously reachable Microsoft endpoint also timed out before TLS negotiation.

Proxy Configuration:

No WinHTTP proxy or proxy environment variables detected.

Additional Information

Microsoft reported Microsoft 365 service degradation on November 12, 2026. It remains unclear whether this incident also affects personal Outlook.com accounts.

Question for Microsoft Support

Is Microsoft experiencing a consumer Outlook.com service disruption, regional routing failure, or infrastructure issue causing HTTPS connectivity timeouts across multiple device types and independent networks?

Can Microsoft confirm whether the reported Microsoft 365 service degradation also affects personal Outlook.com accounts?

If no outage is confirmed, what service-level diagnostics or escalation procedures are available?

Please consider the troubleshooting already completed before recommending repeated browser resets, network resets, or other basic client-side troubleshooting.

Outlook | Web | Outlook.com | Settings
0 comments

3 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Estrella721 48,020 Reputation points Independent Advisor
    2026-11-12T21:01:03.7533333+00:00

    Microsoft is currently experiencing a service disruption affecting Outlook and other Microsoft 365 services. The issue is on Microsoft's end, so there is nothing you need to do on your device or account for now. I recommend waiting until Microsoft resolves the issue and normal service is restored.

    You can follow the latest updates through the official channels below:

    Microsoft Service Status: https://status.cloud.microsoft/

    Microsoft 365 Status on X: https://x.com/MSFT365Status/status/2120938282204688468

    Was this answer helpful?

    0 comments
  2. David Lamb 0 Reputation points
    2026-11-12T20:32:47.9733333+00:00

    Thank you. The suggested troubleshooting has already been completed, and the issue persists across multiple devices, browsers, desktop email clients, and independent broadband and cellular networks.

    DNS resolves successfully, but IPv4 and IPv6 HTTPS connection attempts time out before TLS negotiation.

    I am requesting confirmation from a Microsoft support engineer whether this is a known Outlook.com consumer service incident or an infrastructure/routing issue.

    If no incident is currently identified, please advise how this case can be escalated to the Outlook.com service engineering team for investigation rather than repeating client-side troubleshooting.

    Was this answer helpful?

    0 comments

  3. AI answer

    2026-11-12T20:30:11.58+00:00

    The reported Microsoft 365 degradation does not by itself confirm an Outlook.com consumer outage; check the Outlook.com-facing Microsoft service-status page and, if no matching incident appears, open a personal-account support case with the timeout evidence you have already collected.

    What can be confirmed

    • Microsoft’s Outlook.com support article directs personal Outlook.com users experiencing access problems to the Service Health Status site and separately publishes known Outlook.com issues and workarounds.^1^
    • The Microsoft 365 admin-center dashboard is primarily the authoritative tenant-specific channel for organizational services such as Exchange Online. Administrators use Health > Service health, while the public service-status page is the fallback when the admin center is inaccessible.^2^
    • The available first-party information does not confirm that the November 12, 2026 Microsoft 365 degradation affects personal Outlook.com accounts or that your timeouts are a confirmed regional routing incident.
    • curl timing out before TLS negotiation shows that an HTTPS session was not established. It does not, by itself, identify whether the drop occurs in Microsoft infrastructure, an ISP/transit network, or another upstream path.

    Because the same failure occurs over independent Wi-Fi and cellular connections, browsers, devices, and Outlook clients, further cache clearing, browser resets, Outlook profile repair, or Windows network resets would not be useful at this stage.

    Check the consumer-facing incident channel

    1. Open Microsoft’s Service Health Status site from the link in the Outlook.com known-issues article.^1^
    2. Check for an incident explicitly naming Outlook.com, consumer email, sign-in, or mailbox access.
    3. Compare its:
      • start time,
      • affected region or user scope,
      • user-impact description,
      • current status.
    4. Recheck the Outlook.com known-issues article for a newly posted issue. The absence of an entry means only that no matching public incident is posted there; it does not prove that every Outlook.com endpoint is healthy.

    If you also administer a Microsoft 365 organization, check Microsoft 365 admin center > Health > Service health and open the incident details. Those details identify the affected service and user impact. If the organizational issue is not listed, an authorized admin can select Report an issue; Microsoft correlates those reports across organizations.^2^

    That tenant reporting workflow does not substitute for consumer Outlook.com support.

    Escalate the Outlook.com case

    Since Outlook.com itself is inaccessible, use Microsoft’s general support entry point and select the Personal account path. Describe the problem as an Outlook.com service-connectivity failure and request escalation for investigation of the consumer mailbox endpoint and regional HTTPS routing.^3^

    Include this compact diagnostic package:

    • Outlook.com address, entered only into Microsoft’s secure support form—not posted publicly.
    • Exact first occurrence and most recent occurrence in UTC.
    • Approximate location: country/region and city; do not publish a street address.
    • ISPs tested, distinguishing fixed broadband from cellular.
    • Affected URL: https://outlook.live.com/mail/.
    • Exact error: ERR_TIMED_OUT.
    • Confirmation that web, desktop, and mobile clients all fail.
    • DNS alias chain already obtained.
    • Test-NetConnection results for IPv4 and IPv6, including timestamps and remote IPs.
    • curl -4 and curl -6 output showing timeout before TLS negotiation.
    • Whether other Microsoft account services remain accessible.
    • Any support case number and any incident identifier displayed on the status page.

    Ask support to check:

    1. Whether the account or mailbox is affected by a current Outlook.com incident.
    2. Whether the destination IPs belong to an unhealthy or withdrawn service edge.
    3. Whether failures correlate by region, autonomous system/ISP, or consumer mailbox cluster.
    4. Whether mailbox-level diagnostics show a provisioning or backend access problem.
    5. Whether the case can be escalated to the Outlook.com service team if front-line support cannot reproduce it.

    If Microsoft-account authentication itself fails—not merely Outlook.com loading—the supported route is the Microsoft account sign-in helper. If authentication succeeds but Outlook.com remains inaccessible, use the Outlook.com support route; Microsoft documents in-product support under Help > Help > Still need help? > Yes when the mailbox interface is available.^4^

    References

    1. Fixes or workarounds for recent issues on Outlook.com | Microsoft Support
    2. How to check Microsoft 365 service health
    3. Contact Microsoft customer support | Microsoft Support
    4. How to get support for Outlook.com | Microsoft Support
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.