User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Social
whatsapp.com · Social
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Tests whatsapp.com from your browser and compares it with our checks, the official status, and user reports.
Press Run testNothing leaves your browser except a request to the site and to us.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 355 ms · 5 min ago.
No status feed
WhatsApp does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 12:00 | 0 | 0.0 | 277 ms | 0 |
| 12:15 | 0 | 0.0 | 261 ms | 0 |
| 12:30 | 0 | 0.0 | 444 ms | 0 |
| 12:45 | 0 | 0.0 | 394 ms | 0 |
| 13:00 | 0 | 0.0 | 355 ms | 0 |
One report per service every 10 minutes from this network. No account.
Get an email when WhatsApp goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Checks are succeeding and user reports are near the baseline.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.