Meta favicon

Meta outage on 2026-11-09

metastatus.com
November 2026 9 Minor incident

Meta's WhatsApp Business Platform had trouble sending messages through the Marketing Messages API and WhatsApp Cloud API for 5 hours 27 minutes on 9 November 2026. The fault sat on Meta's side, in the API layer that businesses use to send messages, not in any individual product built on top of it.

Started

18:15 UTC

Duration

Lasted 5h 27m

Source

IsDown

Next time

Meta is degraded. Is your product working?

An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.

50 monitors for your own websites. No card.

What happened?

Meta logged one incident on 9 November 2026, affecting the WhatsApp Business Platform's Marketing Messages API for WhatsApp alongside the WhatsApp Cloud API. It started at 18:15 UTC, which Meta's own update timestamps as 10:15 AM PST, and lasted 5 hours 27 minutes before resolution. Meta's single posted update describes the problem as "low disruptions impacting sending messages" and says engineering teams were investigating, with a promise of further updates "if additional information is available". No further updates were published in this window, so that one filing is the entire public record for the incident. Meta did not name a root cause, a scope of affected accounts, or a percentage of failed sends. The incident page lists no components as formally affected, which is a gap in Meta's own tracking rather than a sign the issue was contained. No user reports were filed during this window, so there is no independent account from businesses sending WhatsApp marketing messages to corroborate or expand on Meta's description. Over the trailing 90 days, Meta has logged 9 incidents on this platform with a median duration of 1 hour 45 minutes, meaning this outage ran well past the typical length for this service. Across all time, Meta has recorded 573 incidents at a pace of roughly 14 per month, which puts WhatsApp Business Platform disruptions on a fairly regular cadence rather than as a rare event.

Learning

If you send marketing or transactional messages through WhatsApp's Business Platform, this incident is a reminder that the failure sits inside Meta's sending infrastructure, a layer you cannot see or probe from your own systems. Your application can report healthy, your queue can accept messages, and the API call can return successfully, while the actual delivery to WhatsApp users stalls somewhere inside Meta's pipeline. That is exactly the shape of this incident: Meta called it "low disruptions impacting sending messages" without giving a cause, and no component list confirms what broke underneath. Watching your own endpoints only tells you that your side of the integration is up, it says nothing about whether Meta is actually delivering what you send it. Over the last 30 days, UptimeRobot's own monitoring recorded 2 incidents on this provider with a median duration of 2 hours 55 minutes, both resolved, which is a separate signal from Meta's own incident log and worth comparing rather than discarding. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.