Current Hotmail service status summary
As of this check, Hotmail is operational for most users worldwide, with no broad outage reported on Microsoft 365 Service Health dashboards. Intermittent access issues can occur for individual accounts due to local network conditions, device settings, or account-specific problems such as cached credentials or security blocks. If you are unable to sign in or are experiencing slowness, the steps below will help you determine whether the issue is on your side or with the service, and how to resolve it quickly.
How to confirm whether Hotmail is down for everyone or only you
Check the official service status page
Visit the Microsoft 365 Service health page or the historical status dashboard to see if any planned maintenance, service incidents, or degraded components are currently affecting authentication, Exchange Online, or related services. Official status sources provide the most reliable evidence of a platform-wide Hotmail or Outlook.com outage.
Quick tests to isolate the cause
- Try signing in from an incognito or private browsing window to rule out cached extensions or expired tokens.
- Test the same account on a different device and network (for example, switch from Wi‑Fi to mobile data or use a phone hotspot).
- Ask a trusted contact or colleague who uses Microsoft accounts whether they are able to sign in successfully right now.
Common causes when Hotmail appears to be down for you
Network and connectivity issues
Slow or unstable connections, restrictive DNS settings, or ISP-level blocks can prevent successful authentication even when the service is fully operational. Problems resolving the login endpoint or timeouts contacting authentication servers often look like a service outage from the user’s perspective.
Account-level blocks and security rules
- Unusual sign-in locations or devices triggering risk-based policies.
- Expired or misconfigured email client credentials and app passwords.
- Password expiration, account compromise investigations, or manual security holds.
Client, browser, and configuration problems
Outdated browsers, extensions interfering with authentication flows, incorrect mail server settings (such as wrong SMTP or IMAP ports), or stale cached credentials in email apps can all create repeated sign-in failures that mimic a service disruption.
Step-by-step troubleshooting checklist
- Confirm current status on the Microsoft 365 Service health page.
- Switch to a different network (mobile hotspot or another Wi‑Fi) and try again.
- Sign in using a private/incognito window to eliminate local extension interference.
- Clear browser cache and cookies for the Microsoft sign-in domain, or remove and reconfigure email app accounts.
- Reset your password if you suspect it may be outdated or if you’ve been prompted to update it.
- Review account security notifications in your Microsoft account activity and unblock any risky sessions when safe.
- Temporarily disable VPNs or browser extensions that terminate or alter secure connections.
- If you use an email client, verify server settings (IMAP/SMTP ports, authentication, and TLS settings) and regenerate app passwords if two‑factor authentication is enabled.
Verification details and service information
Use the table below to understand key attributes of the Hotmail/Outlook.com authentication and delivery platform. These points are helpful when diagnosing access issues and when communicating with support teams.
| Attribute | Verified detail | Source type |
|---|---|---|
| Primary service name | Outlook.com (includes legacy Hotmail identities) | Official Microsoft product documentation |
| Authentication systems | Microsoft Entra ID (Azure AD) and legacy MSO endpoints | Microsoft platform architecture references |
| Webmail URL | https://outlook.live.com/owa | Public Microsoft login and service portal |
| SMTP submission port (TLS) | 587 | Microsoft 365 SMTP configuration guidance |
| IMAP port (SSL/TLS) | 993 | Microsoft 365 client and device setup standards |
| POP3 port (SSL/TLS) | 995 | Microsoft 365 legacy client configuration guidance |
| Admin status page | Microsoft 365 Service health & Microsoft Endpoint Manager admin centers | Microsoft admin portal and status dashboards |
Planned maintenance, updates, and how to anticipate them
Microsoft typically schedules maintenance for security updates, protocol enhancements, and infrastructure improvements with advance notifications sent to admin tenants and posted on the service health pages. Business and enterprise customers with admin consoles receive proactive banners and email advisories before maintenance windows that could affect sign-in flow or message delivery. While planned work is limited to defined timeframes, it can still cause temporary login or sync interruptions for any Hotmail or Outlook.com account.
When to escalate to Microsoft support
Contact Microsoft support if you are unable to sign in after completing the standard checks and fixes, if you suspect your account is compromised, or if you receive repeated security challenges that block access. Provide clear details such as sign-in timestamps, device and browser information, and any error codes to speed up diagnosis. For admin-managed domains, involve your organization’s IT team so they can check tenant policies, conditional access rules, and directory sync status.
Best practices to reduce future access issues
- Keep browsers and email clients updated to the latest supported versions.
- Use app passwords or modern authentication where required, and rotate credentials periodically.
- Review recent activity and active sessions in your Microsoft account periodically.
- Prefer official Microsoft login endpoints and avoid third-party sign-in intermediaries.
- Configure backup methods and recovery email/phone numbers in advance.
Summary and key takeaways
Hotmail (now part of Outlook.com) is generally online and operational, but individual users can experience sign-in or connectivity issues due to local network conditions, device settings, or account-specific security rules. Follow the verification steps and checklist above to quickly determine whether the platform is experiencing an incident or whether the problem is isolated to your environment. Use the documented ports, endpoints, and support escalation paths to resolve issues efficiently and reduce future disruptions.