WhatsApp, Discord and Messenger hit by Panne Facebook from 15h40
panne facebook struck WhatsApp, Discord and Messenger at the same time from 15h40, with users reporting errors, failed connections and messages stuck on send. Several people also said Messenger could not be accessed from 15h42.
That overlap matters because WhatsApp and Messenger sit inside Meta, while Discord does not. When two Meta services fail alongside an independent platform, the pattern points readers away from a single app setting and toward a broader service problem.
WhatsApp and Messenger
The first complaints appeared at 15h40, which gave the outage a clear start point for anyone trying to work out whether the problem was local or wider. The reports were not limited to one app, and that made the interruption visible across different messaging habits at once.
Users described connection failures and sent messages that stayed stuck, which means the basic handoff between the app and the service was not completing cleanly. For anyone trying to keep a conversation moving, the immediate effect was not just slow delivery but no delivery at all.
Discord joins Meta apps
Discord was in the same failure window, even though it is independent of Meta. That removes the simplest explanation that the trouble was confined to one company’s ecosystem and raises the likelihood of a wider disruption affecting multiple services at once.
By 15h42, several users were already saying they could not access Messenger. That two-minute gap between the first reports and the access failures gives the outage a fast-moving profile, which is exactly the kind of detail people checking their own devices need.
Meta has not explained it
No platform involved had said what caused the bug at the time of the reports, so users were left with symptoms rather than a fix or a cause. The practical move for affected people was simple: try again later and avoid assuming the fault was on a single phone or account.
The unanswered question is whether the disruption stayed limited to these three services or widened further after 15h42, because the first wave of reports only shows where the failure was seen, not where it ended.
