WebsiteDown.org logoWebsiteDown.org

Live Domain Check

Is Outlook Down? Check outlook.office.com Status and Outages

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

Get official Outlook 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 Outlook Outages and Server Issues

Outlook disruptions typically appear as send/receive delays, reconnect loops, or sessions that drop unexpectedly.

For Outlook, early outage signals often show up as message delivery, session refresh, and attachment upload 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 Outlook Status, Support, and Social Channels

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

Official Outlook Social Profiles for Live Updates

For Outlook disruptions on outlook.office.com, social updates can help you confirm whether failures are platform-wide or route-specific.

Common Outlook Problem Patterns

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

Partial failure: Message delivery works, but errors appear in session refresh

For Outlook, this usually means a component-level incident on outlook.office.com, not full platform downtime. Validate message delivery and session refresh in the same session, then check send and receive as separate flows before resetting sessions.

Regional mismatch in session refresh and attachment upload

When the same action is up in one region but failing in another, route and edge behavior are the common causes. Re-run this outlook.office.com check after 2 to 5 minutes and compare web and mobile results on different networks.

4xx/5xx after sign-in during attachment upload

If authentication succeeds but post-login actions fail, policy, token, or backend dependencies may be unstable for Outlook. Before opening support, keep message IDs or request timestamps for support.

Intermittent up/down flips around presence updates

Flapping verdicts often happen during traffic rebalancing or partial recovery windows. For Outlook, avoid repeated reconnect loops while the service stabilizes, then run one final verification check for outlook.office.com.

How to Check if Outlook Is Down

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

1. Check in two places

Run outlook.office.com in WebsiteDown.org first, then open outlook.office.com in your own browser. If both checks fail at the same time, Outlook 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 outlook.office.com fails, this points to a partial endpoint issue.

4. Escalate with evidence

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

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

If Outlook Is Not Working Only For You, Start Here

Use these local troubleshooting steps after the down-check workflow when Outlook seems broken only for you. This section focuses on app, browser, account, and network fixes.

1. Compare browser sessions

Open outlook.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 outlook.office.com. Avoid repeated password or security resets until you confirm this is not a broader Outlook 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 Outlook support.

Frequently Asked Questions

Is Outlook down for everyone or just me?

Run the automatic multi-region check on this page for outlook.office.com. If most regions fail at the same time, Outlook 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 Outlook 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 Outlook 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 Outlook is not working?

Use this sequence for outlook.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