WhatsApp Business Platform's Meta Business Agent Platform broke for 24 minutes on 1 October 2026. Meta's own status page logged it as a single incident starting at 18:43 UTC, and the fault sat on Meta's side, not yours.
Started
18:43 UTC
Duration
Lasted 24m
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's status page shows one incident on this day, titled "Outage in WhatsApp Business Platform - Meta Business Agent Platform", starting at 18:43 UTC and lasting 24 minutes. There is only one update on record, posted at the start of the incident, describing "low disruptions" on the Meta Business Agent Platform. That update said engineering teams were investigating and promised another update within 4 hours or sooner if more information became available. No such follow-up update appears in the record, and no closing or resolved message is logged either, despite the incident's listed duration of 24 minutes. Meta did not name specific components as affected in this filing, and the components_affected list is empty. No user reports were filed during the window, so there is no independent account of what businesses using the Agent Platform actually saw. One filing from Meta is what this page has to go on, and it is thin: a single status update, graded by Meta itself as "low disruptions", a severity label that describes how Meta chose to frame it rather than how much it affected your product. Meta's history shows 13 incidents in the last 90 days with a median duration of 3 hours 22 minutes, so a 24 minute incident sits well under that median. Across all time, Meta has logged 571 incidents at a rate of 14.3 per month, so a short incident on the Business Agent Platform is not unusual for this provider.
Learning
UptimeRobot's own probes recorded 2 incidents on Meta in the last 30 days, resolved, with a median duration of 55 minutes, which is a different slice of Meta's infrastructure measured from the outside rather than Meta's own internal report on this specific platform. Both readings can be correct at once: your outward-facing checks against Meta's endpoints can stay green while a backend component like the Business Agent Platform fails, because the failure sits inside Meta's systems that handle message routing and automation logic, not in the public API surface your probes necessarily touch. This is the general shape of a provider-side outage: the part that breaks is often not the part you are watching, because you can only watch what you can reach from outside. Watching your own endpoints would have told you your product was up, which is true, but it would not have told you why messages sent through the Agent Platform were failing to send, because that fault lived entirely on Meta's side of the line. If you run a product that depends on WhatsApp Business messaging, this incident is a reminder that your monitoring covers your half, and Meta's status page covers theirs, but neither alone tells the full story. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
