Is Messenger not working? Check for a wider Meta incident first, then compare the problem across devices, networks, browsers, and conversations. These checks help show whether Messenger is broadly unavailable or whether the cause is local, account-specific, or limited to one chat.
Site Administrator
Last reviewed: September 25, 2026
LATEST RECORDED STATUS
Up Messenger’s website appeared to be up and responding normally at the last check.
| Endpoint | Status | Observed |
|---|---|---|
| messenger.com | Operational | 2026-11-09 14:09 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 Messenger’s official status page. official status page.

Messenger problems can occur at several different scopes. A service-wide incident may affect sending, conversation loading, login, and notifications together. A local app, browser session, account, network, or individual conversation may produce only one symptom.
Use the official Meta status page to look for a broader incident, but treat a clear status page as only one piece of evidence. Regional, short-lived, account-specific, or device-specific problems may not appear there.
The failure pattern provides useful clues:
Open the official Meta status page and compare any incident timing with when Messenger stopped working. If sending, loading, login, and other Messenger functions fail across multiple devices and networks, a broader service problem is more likely. Wait for recovery rather than making repeated local changes.
If no matching incident is listed, continue with the comparisons below. Status information may not include every regional, account-specific, or short-lived problem.
For Messenger in a browser, reload the page and try a private window or another browser. If the private window works, an expired session, cached data, browser extension, or content-blocking setting may be interfering. Sign in again only through the normal Messenger site, and avoid repeatedly submitting credentials when login is failing.
Try another Wi-Fi network or a mobile connection. If a VPN, proxy, or restrictive firewall is in use, temporarily disable it only if permitted by your organization or network policy, then retry. If Messenger works on the alternate connection, investigate the original network, DNS resolution, filtering, or firewall instead of treating the issue as a Messenger-wide outage.
A refused connection, timeout, DNS failure, or gateway error describes a failure somewhere along the connection path; it does not by itself confirm a Messenger outage.
If Messenger loads but login, sending, notifications, or one feature fails for only one account, the cause may be account-specific. Check for an on-screen explanation, confirm that the correct account is being used, and avoid repeated login attempts that could trigger additional verification steps.
Check whether the message is pending, failed, or appears sent but is not being seen. Confirm the connection, retry once, and test another conversation if appropriate. If other chats work but one recipient or thread does not, treat the issue as an isolated conversation or account interaction until broader evidence appears.
If conversations load normally but alerts arrive late, check the device's notification permissions, background-activity restrictions, and battery-saving settings. Compare notification behavior with messages viewed directly in Messenger; delayed alerts do not necessarily mean that Messenger itself is unavailable.
Use the status page alongside direct testing on another device or network. A clear status page does not rule out a local, regional, browser, network, account-specific, or conversation-specific problem.
Every time this page loads, our server makes its own request to messenger.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 Messenger'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 Meta status page for current service information, then compare Messenger on another device or network. If no incident is listed, the problem may still be regional, account-specific, browser-related, or limited to your connection.
Possible causes include an unstable connection, a temporary service problem, an app issue, account-specific access, or a failure limited to one conversation. Check whether the message is pending or failed, test another network, and try a different chat.
The browser may have an expired session, cached data, an extension conflict, or a browser-specific problem. Try a private window and another browser. If those work, investigate the original browser rather than assuming Messenger is down.
Compare Messenger on another device and another network. Failure across devices and connections makes a broader service problem more plausible. If Messenger works on an alternate connection, investigate the original Wi-Fi, mobile network, DNS, VPN, proxy, or firewall.
Notifications can be affected separately from chat loading. Check notification permissions, background-activity restrictions, and battery-saving settings on the device, then compare alerts with messages viewed directly in Messenger.
Test the app or site on another device and connection, try a private browser window if relevant, and check whether every conversation is affected. These comparisons help distinguish a local, network, browser, account, or isolated-chat problem from a wider outage.
This is a live connectivity check from our server, not an official statement from Messenger. A down result may also reflect a regional or partial outage.