Live  /  Providers  /  WhatsApp

WhatsApp

whatsapp.comNo open incidents

Independent assessment — SquidGrid is not affiliated with WhatsApp. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

Consumer platforms · SquidGrid tracks WhatsApp’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what WhatsApp is reporting

Current & recent incidents

Resolved

[Resolved]: Marketing Messages API for WhatsApp

2026-11-09 23:37 UTC · source

Resolved

[Low disruptions]: Marketing Messages API for WhatsApp

2026-11-09 18:15 UTC · source

Resolved

[Resolved]: Meta Business Agent Platform

2026-10-01 19:04 UTC · source

Resolved

[Low disruptions]: Meta Business Agent Platform

2026-10-01 18:43 UTC · source

Incident titles and states as published by the provider. Times in UTC.

Track record

SquidGrid has archived 4 incidents from WhatsApp’s own status page since 2026-10-01.

Computed by SquidGrid from the incidents WhatsApp published. Their own page shows only recent history; this archive keeps every one.

Independent path health

A status page tells you what WhatsApp has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

WhatsApp runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of WhatsApp is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with WhatsApp.