Is Messenger down?

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.

SA

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.

Website (messenger.com) Up
Response time 843 ms
Last checked 2026-11-09 14:09:32 UTC
Current endpoint observation
EndpointStatusObserved
messenger.comOperational2026-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.

What this check can tell you

  • Check the official Meta status page before repeatedly reinstalling Messenger or changing account settings.
  • Compare Messenger on another device, browser, or network to identify whether the failure follows your account or connection.
  • A message stuck pending can result from an unstable connection, a temporary service issue, or a problem limited to one conversation.
  • If Messenger works in a private browser window, an expired session, cached data, extension, or content-blocking setting may be involved.
  • A clear status page does not rule out regional, account-specific, notification, or device problems.
Messenger live status check banner

About Messenger reliability

Understanding Messenger availability

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:

  • Several Messenger features fail across devices and networks: a wider service or connectivity problem is more plausible.
  • Only one phone, computer, or browser fails: investigate the app, browser session, cached data, or device settings.
  • Only one Wi-Fi or mobile connection fails: test another connection before changing account settings.
  • Only one conversation or recipient is affected: the problem may be limited to that chat or account interaction.
  • Chats load but notifications are delayed: check device notification and background-activity settings separately from Messenger availability.

How to troubleshoot Messenger

Troubleshooting Messenger problems

Check for a broader Meta incident

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.

Test the Messenger app and device

  • Force-close and reopen Messenger, then retry the affected conversation.
  • Restart the phone or computer if the app is frozen or notifications are delayed.
  • Check whether all conversations fail or only one chat does.
  • Install available Messenger or operating-system updates if the app is behaving abnormally.
  • If Messenger works on another device, the original device or its local app data is the stronger suspect.

Separate browser and session problems

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.

Test the network path

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.

Consider account or access-specific causes

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.

When messages are not sending

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.

When notifications are delayed

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.

Sources & references

Official source

  • Meta status — Check official Meta service-status information when Messenger appears broadly 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.

How this check works

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.

Embed this live status badge

Add this badge to a dashboard, documentation page, or blog. The badge reads the cached Erriscope observation and links back to this status page.

Messenger status on Erriscope
<a href="https://erriscope.com/status/messenger/"><img src="https://erriscope.com/status/badge/messenger.svg" alt="Messenger status on Erriscope" width="210" height="34"></a>

Frequently asked questions

Is this the same as Messenger's official status page?

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.

Why does this show "Up" when Messenger feels slow or broken for me?

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.

How often is this checked?

A check is refreshed after the two-minute cache expires. The displayed check time shows when the observation was made.

Does an API outage mean the whole product is down?

Not necessarily. Many services split their website and API onto separate infrastructure, so one can fail while the other keeps working.

Is Messenger down right now?

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.

Why is Messenger not sending messages?

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.

Why does Messenger work on my phone but not in my browser?

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.

How can I tell whether Messenger or my internet connection is the problem?

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.

Why are Messenger notifications delayed when chats still load?

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.

What should I do if the Meta status page shows no Messenger incident?

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.

← Back to all services

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.