Live - 300+ check locations
Is Messenger down right now?
HostTracker's monitoring network reached messenger.com and completed a full check without errors. It has been up for 15h 33m.
Stop finding out from a search - HostTracker's website monitoring checks the services you depend on from 300+ locations and alerts you the moment one changes.
Up
for 15h 33m
- Last check
- just now
- Next check
- -
- HTTP
- OK
Checking messenger.com right now
A fresh check, started when you opened this page - each probe runs its own independent DNS, TCP, TLS and HTTP request. Anonymous runs sample the network; a signed-in account checks from more locations.
How Messenger has behaved
Every figure here comes from HostTracker's own checks of messenger.com, not from the vendor's status page.
Response time
616ms avg · 764ms peak
What we check
-
HTTP609 ms average, every 10 minutesOK
-
Ping24 ms average, every 10 minutesOK
-
Page Speed1703 ms average, every 15 minutesOK
90-day uptime
100.000% over 2 measured days · 0 incidents
- Operational
- Degraded
- Down
- No data
Incident history
Last 90 daysNo incidents recorded in the last 90 days.
About Messenger outages
Written by the HostTracker monitoring team · updated from live probe data.
Messenger is Meta's standalone messaging app, split out from the main Facebook app years ago but still running on the same shared Meta backend infrastructure as Facebook, Instagram, and WhatsApp, which is the key thing to understand about how it fails. A deep infrastructure incident at Meta can take down Messenger alongside its sibling apps at once, a pattern seen in several major past outages. But Messenger also has product-specific pieces that fail on their own: message delivery and sync, voice and video calling, and Facebook-linked login for accounts tied to a Facebook profile. It's common for the app to open and the chat list to load fine while new messages won't send, or for calls to fail to connect while text messaging keeps working normally, both signs of a narrower incident rather than a full Meta-wide outage.
Common causes of Messenger downtime
Not sure whether it's Messenger or your own connection? Read the full breakdown in our website down checker guide for a general walkthrough of diagnosing any outage, from DNS failures to expired certificates.
Backend infrastructure incidents shared with Facebook, Instagram, and WhatsApp under Meta that can take out Messenger and its sibling apps at the same time
Message-delivery or sync issues that leave the app open and the chat list visible but new messages not sending or arriving
Voice and video calling failures that are separate from text messaging, so calls can drop or fail to connect while chat keeps working
Login issues tied to a linked Facebook account, since Messenger's authentication for those accounts depends on Meta's shared identity system
Regional network or DNS issues making messenger.com or the app unreachable from specific countries or ISPs without affecting other regions
Other services we track
AWSOperational
G
InstagramOperational
X
AmazonOperational
T
ShopifyOperational
DHostTracker has monitored websites and online services since 2004 and is trusted by 500,000+ sites today, covering 14 check types from 300+ global locations. Want the same multi-location confirmation and instant alerts for your own site or any service you depend on? Getting started costs nothing - start a free monitor or compare plans and pricing.
Questions people ask during an outage
The live probe run on this page tests messenger.com from a broad sample of HostTracker's 300+-location monitoring network - many independent networks at the same moment, rather than just your own connection. If every location fails to reach it, the outage is real and affects everyone; if only a few locations fail while most load normally, the problem is local to those regions or networks rather than Messenger being fully down. A single refresh from your own browser can never make that distinction, because it only ever tests from one vantage point on one network.
Yes. HostTracker lets you add any URL - including third-party services you depend on, not just your own website - as a monitored target, and notifies you automatically the moment it becomes unreachable. Before sending an alert, HostTracker re-verifies a failure from multiple locations in its 300+-location network, so you're notified about real, confirmed outages rather than a single location's momentary blip. The free plan checks two monitors every 30 minutes indefinitely at no cost; paid plans check as often as once a minute, with alerts available through SMS, email, voice call, and several messenger apps.
No - as of the most recent check, messenger.com is responding normally to HostTracker's monitoring network, and has been up for 15h 33m. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.
No - as of the most recent check, messenger.com is responding normally to HostTracker's monitoring network, and has been up for 15h 33m. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.
No - as of the most recent check, messenger.com is responding normally to HostTracker's monitoring network, and has been up for 15h 33m. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.
No - as of the most recent check, messenger.com is responding normally to HostTracker's monitoring network, and has been up for 15h 33m. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.
Often, but not always. Messenger and Facebook share Meta's underlying infrastructure, so a deep infrastructure incident can take out both at once, which is the pattern behind several major past outages. But Messenger and Facebook also each have product-specific components, so it's possible for only one to be affected while the other works normally.
It usually points to a message-delivery problem rather than the whole app being unreachable. The app can open, load your chat list, and let you type normally while the backend responsible for actually delivering messages is degraded, which is a distinct failure from the app not loading at all.
Yes, Messenger supports standalone accounts, but many users still have their Messenger identity tied to a Facebook login. If Meta's shared authentication layer has an incident, sign-in can fail for Facebook-linked Messenger accounts even when the messaging backend itself is healthy.
Voice and video calling run on different infrastructure than text messaging, so it's a known pattern for calls to drop or fail to connect while sending and receiving text messages keeps working normally. That points at a calling-specific incident, not a full Messenger outage.
Monitor your website from 300+ locations
Start a free trial and get instant alerts when your site goes down - verified from multiple locations before you're notified.
- Trusted since 2004
- 500,000+ websites monitored
- 300+ checkpoints worldwide