Microsoft 365 service status
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Live Domain Check
Run a live reachability check for office.com. Compare the regional responses with the problem you see in Microsoft 365.
Find Microsoft 365 help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
Microsoft 365 service health can be tenant-specific, and Exchange, Teams and SharePoint may not fail together.
The checker above requests office.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Microsoft 365 action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Distinguish Microsoft account access from mail, storage and meetings using the relevant product check: Outlook status check, OneDrive status check, Microsoft Teams status check. Compare results separately; these links do not establish a shared outage.
Looking for another service? Browse work app checks.
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
An authorised administrator may need tenant-specific Service Health and support.
Open the website in your browser and compare it with the result above.
Open Microsoft 365 help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.
Tenant/product, affected user scope, client, UTC window and relevant incident/correlation ID.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to Microsoft 365.
These are troubleshooting comparisons, not claims that Microsoft 365 is currently experiencing a particular incident.
Identify the affected app and ask an authorised administrator to compare tenant Service Health with the user report.
Check whether two users in the same organisation reproduce the same action on web and desktop clients.
A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
Use these local troubleshooting steps after the down-check workflow when Microsoft 365 seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open office.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader Microsoft 365 issue.
If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Microsoft 365 support.
Run the office.com check and compare its original timestamps and responses with your actual error. Microsoft 365 service health can be tenant-specific, and Exchange, Teams and SharePoint may not fail together.
Use the community buttons on this page to share whether the service works for you. For help from Microsoft 365, use the official help/reporting resource linked above. An authorised administrator may need tenant-specific Service Health and support.
Identify the affected app and ask an authorised administrator to compare tenant Service Health with the user report. Check whether two users in the same organisation reproduce the same action on web and desktop clients.
Tenant/product, affected user scope, client, UTC window and relevant incident/correlation ID.