WebsiteDown.org logoWebsiteDown.org

Live Domain Check

Is Microsoft 365 Down? Check office.com Status and Outages

Check if Microsoft 365 is down right now (office.com). Run a live multi-region check to see whether Microsoft 365 is offline for everyone or just you.

Get official Microsoft 365 outage status updates, support links, and targeted troubleshooting steps in one page.

Related hosts:
Ready

Running automatic check…

Checking reachability from multiple regions.

Checked -
Verdict -
Response Time -
Final URL -
Regional checks 8 regions
Rate:

No ratings yet.

About Microsoft 365 Outages and Server Issues

Microsoft 365 outages are often partial, affecting collaboration flows before the full interface becomes unavailable.

For Microsoft 365, early outage signals often show up as permission checks, notification delivery, and search indexing before a full failure. If results are mixed, use the website outage triage guide, the HTTP status codes guide, and the DNS troubleshooting guide to isolate provider incidents from local network issues.

Official Microsoft 365 Status, Support, and Social Channels

Use these official Microsoft channels to confirm outages, maintenance notices, and recovery progress for Microsoft 365.

Official Microsoft 365 Social Profiles for Live Updates

Official Microsoft 365 social profiles can confirm workspace-impacting incidents on office.com, including login, sync, and collaboration disruptions.

Common Microsoft 365 Problem Patterns

Use these service-specific patterns to identify likely root cause quickly and choose the right next step.

Partial failure: Permission checks works, but errors appear in notification delivery

For Microsoft 365, this usually means a component-level incident on office.com, not full platform downtime. Validate permission checks and notification delivery in the same session, then retry in a private browser and compare workspace-level status updates.

Regional mismatch in notification delivery and search indexing

When the same action is up in one region but failing in another, route and edge behavior are the common causes. Re-run this office.com check after 2 to 5 minutes and retest on mobile data versus office/VPN routing.

4xx/5xx after sign-in during search indexing

If authentication succeeds but post-login actions fail, policy, token, or backend dependencies may be unstable for Microsoft 365. Before opening support, save the exact action, status code, and timestamp.

Intermittent up/down flips around background exports

Flapping verdicts often happen during traffic rebalancing or partial recovery windows. For Microsoft 365, pause non-critical retries to avoid duplicated edits or notifications, then run one final verification check for office.com.

How to Check if Microsoft 365 Is Down

Practical steps to follow when office.com seems down. Use this checklist to confirm whether Microsoft 365 is down for everyone or only for you.

1. Check in two places

Run office.com in WebsiteDown.org first, then open office.com in your own browser. If both checks fail at the same time, Microsoft 365 is likely down beyond your local device.

3. Isolate network path

Test related hosts such as www.microsoft.com, portal.office.com. If they work while office.com fails, this points to a partial endpoint issue.

4. Escalate with evidence

Capture final URL, status code, and response time for office.com, then share those details with Microsoft 365 support for faster triage and recovery.

How to check if Microsoft 365 is down (office.com): 4-step workflow.
WebsiteDown.org incident workflow for troubleshooting office.com availability issues.

If Microsoft 365 Is Not Working Only For You, Start Here

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.

1. Compare browser sessions

Open office.com in your current browser, then test in a private window or second browser. If only one session fails, the issue is usually local cache, cookie, or extension state.

2. Reset account session once

Sign out and sign back in one time, then retry the failing action on office.com. Avoid repeated password or security resets until you confirm this is not a broader Microsoft 365 issue.

3. Remove network interference

Temporarily disable VPN, proxy, private DNS, and filtering extensions. Then switch between Wi-Fi and mobile data to isolate route-level differences.

4. Capture support-ready evidence

Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Microsoft 365 support.

Frequently Asked Questions

Is Microsoft 365 down for everyone or just me?

Run the automatic multi-region check on this page for office.com. If most regions fail at the same time, Microsoft 365 is likely experiencing a broader outage or partial incident.

If only one or two regions fail, the issue is usually local to your network path (DNS resolver, ISP route, VPN/proxy, or firewall). Re-check after 2 to 5 minutes and compare Wi-Fi with mobile data.

Where can I find real-time Microsoft 365 outage updates?

Use the Status, Support, and Live Update Links section above. Start with vendor status and support sources, then compare with live social updates.

Official status dashboards are authoritative but can lag during the first minutes of an incident, so combining both sources gives faster signal.

Why is Microsoft 365 down for me but up for others?

That pattern usually points to route-specific or account-specific issues rather than a global outage. Common causes include:

  • Stale DNS cache or resolver mismatch
  • ISP route differences or regional peering congestion
  • VPN/proxy filtering, WAF policy, or geo restrictions
  • Session, cookie, or temporary rate-limit edge cases

Test from a second network and capture the exact error code before resetting credentials.

What should I do first if Microsoft 365 is not working?

Use this sequence for office.com:

  1. Run the live check
  2. Review official status/support updates
  3. Test from another network
  4. Record status code and final URL for escalation
  5. Only then clear DNS/cache if the issue appears local