Is Outlook not loading, syncing, or sending messages? Check Microsoft’s Microsoft 365 service status first, then compare the affected action in another browser, device, or network. These tests help distinguish a broader Outlook incident from an account, connection, or local browser problem.
Site Administrator
Last reviewed: September 25, 2026
LATEST RECORDED STATUS
Up Outlook’s website appeared to be up and responding normally at the last check.
| Endpoint | Status | Observed |
|---|---|---|
| outlook.com | Operational | 2026-11-09 15:00 UTC |
Is it working for you?
0 recent reports — more reports are needed for a useful trend.
For the full picture, including partial or regional outages a single external check may miss, see Outlook’s official status page. official status page.

Outlook availability is not a single yes-or-no condition. The web interface may open while sign-in, sending, receiving, folder loading, or another mail function is unavailable. An issue can also affect one account, region, browser, device, or network without being a broad Outlook outage.
The official Microsoft 365 service-status page is the best place to check Microsoft’s published incident information. If it shows an Outlook-related incident, repeated browser changes are unlikely to resolve the underlying service problem. If no relevant incident appears, compare the same action across another browser, device, or network before concluding that Outlook is down.
When reporting the problem, record the affected action, exact error message, start time, account scope, browser, device, and network. This information helps distinguish a service-wide issue from authentication, connectivity, or local configuration problems.
Open the official Microsoft 365 service-status page and look for an incident affecting Outlook or a related Microsoft 365 service. If Microsoft reports an active issue, avoid repeatedly changing local settings and retry after the incident information changes.
If no relevant incident is listed, test the same Outlook action on another network or device. A problem that affects several environments is less likely to be limited to one browser or connection.
A successful test in a private window or different browser points toward cached data, an extension, or browser configuration. Failure across browsers and devices warrants another service-status check.
Read the exact authentication message and confirm that the account identifier and password are entered correctly. Test the account in another browser or device. If other users can sign in but one account cannot, an account-specific authentication or verification issue is more plausible than a general outage.
Use Microsoft’s normal account-recovery or support process when the message indicates an account, authentication, or verification problem. Do not give passwords or verification codes to anyone offering unofficial assistance.
Identify whether the problem affects all mail, one folder, one conversation, new messages, or only sending. Reload Outlook and, when sending is the affected action, try a small new test message. If the same mail operation fails on more than one device or network, check the Microsoft 365 status page for a partial incident affecting Outlook functions.
Try a private window, another browser, or another device. A result that changes between browsers points toward extensions, cached data, cookies, or browser settings. A result limited to one device may indicate local software, device configuration, or connectivity conditions.
Test Outlook on another network, such as a mobile connection. If the result changes, investigate DNS, proxy, firewall, filtering, or other network conditions. Corporate and school networks may apply access policies; contact the relevant network administrator when only that network is affected.
Preserve the exact text for a specific connection or browser error and use guidance for that error rather than applying unrelated fixes. Record the affected page or action, time, browser, device, and network when asking for support.
For account, authentication, browser, or connectivity problems, consult Microsoft’s support and product documentation for the exact message and access method involved.
Every time this page loads, our server makes its own request to outlook.com (and its API domain, when applicable) and reports what it got back — a real HTTP response, a timeout, or a connection failure. That result is cached for up to 2 minutes.
This confirms external reachability; it does not test every feature, region, account, or network path. Cross-check the official status page when one is available.
No. This is a live, one-off connectivity check run from our own server, not Outlook's own incident reporting. Their official status page can show partial, regional, or component-level issues our single external check cannot detect.
A basic reachability check confirms that the server responded to our request. It does not test every feature, region, ISP, browser, or account-specific issue.
A check is refreshed after the two-minute cache expires. The displayed check time shows when the observation was made.
Not necessarily. Many services split their website and API onto separate infrastructure, so one can fail while the other keeps working.
Check the official Microsoft 365 service-status page for current incident information. If no incident is listed, test Outlook in another browser, on another device, or over another network because the issue may be account-specific or local.
The issue may be limited to your account, browser, device, or network. Compare the same account in a private window, another browser, and another connection. If it fails everywhere, an account or service-side cause becomes more likely.
The interface and mail synchronization are separate functions. Check whether the problem affects all mail or only one folder or conversation, reload Outlook, and test on another browser or device. If the problem follows you across environments, check Microsoft 365 service status for an Outlook-related incident.
Loading the interface does not confirm that sending is available. Check the exact send error, try a new test message, and compare the result on another device or network. A persistent failure across environments may indicate an account or service issue rather than a browser problem.
Check whether other websites load and test Outlook on another network. If multiple websites fail, investigate the connection, DNS, proxy, firewall, or filtering. If only Outlook fails while other sites work, check the official service status and compare another browser or device.
Include the exact error message, affected action, start time, whether sign-in succeeds, and whether the issue occurs in another browser, device, or network. Do not include your password or security codes.
This is a live connectivity check from our server, not an official statement from Outlook. A down result may also reflect a regional or partial outage.