Skip to content

Outage tracker / WhatsApp

Is WhatsApp down?

I'm having a problem

Partially degradedchecked moments ago

WhatsApp is answering our probes, but its API is running at least 3.4x its 7-day median from US-West. Everything else we check answered at its usual speed.

As of Sep 23, 2026, 9:12 AM UTC, WhatsApp answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 46 days we have measured WhatsApp (since Aug 8, 2026).

our independent probeslive · checked Sep 23, 2026, 9:12 AM UTC
US-East97 msOperational
US-West473 msDegraded
Europe256 msOperational
Asia-Pacific309 msOperational
US-Central134 msOperational
Canada121 msOperational
UK181 msOperational
Southeast Asia453 msOperational
Australia1515 msOperational
South America748 msOperational
their status pagetheir claim, not our reading

WhatsApp publishes no status feed we can read, so the only independent reading here is ours on the left.

WhatsApp response time, by region

US-East
288msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 572ms2026-08-26 UTC: p95 532ms2026-08-27 UTC: p95 545ms2026-08-28 UTC: p95 521ms2026-08-29 UTC: p95 614ms2026-08-30 UTC: p95 629ms2026-08-31 UTC: p95 552ms2026-09-01 UTC: p95 629ms2026-09-02 UTC: p95 527ms2026-09-03 UTC: p95 473ms2026-09-04 UTC: p95 343ms2026-09-05 UTC: p95 300ms2026-09-06 UTC: p95 564ms2026-09-07 UTC: p95 515ms2026-09-08 UTC: p95 572ms2026-09-09 UTC: p95 528ms2026-09-10 UTC: p95 503ms2026-09-11 UTC: p95 644ms2026-09-12 UTC: p95 649ms2026-09-13 UTC: p95 611ms2026-09-14 UTC: p95 674ms2026-09-15 UTC: p95 761ms2026-09-16 UTC: p95 774ms2026-09-17 UTC: p95 720ms2026-09-18 UTC: p95 698ms2026-09-19 UTC: p95 378ms2026-09-20 UTC: p95 276ms2026-09-21 UTC: p95 308ms2026-09-22 UTC: p95 314ms2026-09-23 UTC: p95 288ms
Aug 25Sep 8Sep 23
US-West
1.0sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 494ms2026-08-26 UTC: p95 543ms2026-08-27 UTC: p95 546ms2026-08-28 UTC: p95 616ms2026-08-29 UTC: p95 542ms2026-08-30 UTC: p95 475ms2026-08-31 UTC: p95 466ms2026-09-01 UTC: p95 432ms2026-09-02 UTC: p95 467ms2026-09-03 UTC: p95 570ms2026-09-04 UTC: p95 392ms2026-09-05 UTC: p95 449ms2026-09-06 UTC: p95 452ms2026-09-07 UTC: p95 454ms2026-09-08 UTC: p95 488ms2026-09-09 UTC: p95 568ms2026-09-10 UTC: p95 339ms2026-09-11 UTC: p95 293ms2026-09-12 UTC: p95 302ms2026-09-13 UTC: p95 256ms2026-09-14 UTC: p95 316ms2026-09-15 UTC: p95 443ms2026-09-16 UTC: p95 413ms2026-09-17 UTC: p95 209ms2026-09-18 UTC: p95 247ms2026-09-19 UTC: p95 305ms2026-09-20 UTC: p95 317ms2026-09-21 UTC: p95 359ms2026-09-22 UTC: p95 626ms2026-09-23 UTC: p95 1.0s
Aug 25Sep 8Sep 23
Europe
156msp95 · latest
500ms250ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 322ms2026-08-26 UTC: p95 332ms2026-08-27 UTC: p95 340ms2026-08-28 UTC: p95 290ms2026-08-29 UTC: p95 264ms2026-08-30 UTC: p95 233ms2026-08-31 UTC: p95 260ms2026-09-01 UTC: p95 329ms2026-09-02 UTC: p95 326ms2026-09-03 UTC: p95 346ms2026-09-04 UTC: p95 373ms2026-09-05 UTC: p95 301ms2026-09-06 UTC: p95 341ms2026-09-07 UTC: p95 325ms2026-09-08 UTC: p95 322ms2026-09-09 UTC: p95 353ms2026-09-10 UTC: p95 372ms2026-09-11 UTC: p95 376ms2026-09-12 UTC: p95 416ms2026-09-13 UTC: p95 390ms2026-09-14 UTC: p95 416ms2026-09-15 UTC: p95 403ms2026-09-16 UTC: p95 481ms2026-09-17 UTC: p95 150ms2026-09-18 UTC: p95 145ms2026-09-19 UTC: p95 144ms2026-09-20 UTC: p95 159ms2026-09-21 UTC: p95 160ms2026-09-22 UTC: p95 158ms2026-09-23 UTC: p95 156ms
Aug 25Sep 8Sep 23
Asia-Pacific
759msp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 1.3s2026-08-26 UTC: p95 1.5s2026-08-27 UTC: p95 1.7s2026-08-28 UTC: p95 1.8s2026-08-29 UTC: p95 1.9s2026-08-30 UTC: p95 1.9s2026-08-31 UTC: p95 1.8s2026-09-01 UTC: p95 1.8s2026-09-02 UTC: p95 2.3s2026-09-03 UTC: p95 1.9s2026-09-04 UTC: p95 922ms2026-09-05 UTC: p95 929ms2026-09-06 UTC: p95 1.3s2026-09-07 UTC: p95 1.4s2026-09-08 UTC: p95 1.5s2026-09-09 UTC: p95 1.5s2026-09-10 UTC: p95 1.5s2026-09-11 UTC: p95 1.6s2026-09-12 UTC: p95 1.6s2026-09-13 UTC: p95 1.5s2026-09-14 UTC: p95 1.3s2026-09-15 UTC: p95 1.3s2026-09-16 UTC: p95 1.5s2026-09-17 UTC: p95 1.4s2026-09-18 UTC: p95 1.4s2026-09-19 UTC: p95 863ms2026-09-20 UTC: p95 564ms2026-09-21 UTC: p95 756ms2026-09-22 UTC: p95 765ms2026-09-23 UTC: p95 759ms
Aug 25Sep 8Sep 23
US-Central
307msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 884ms2026-09-04 UTC: p95 594ms2026-09-05 UTC: p95 532ms2026-09-06 UTC: p95 446ms2026-09-07 UTC: p95 442ms2026-09-08 UTC: p95 434ms2026-09-09 UTC: p95 460ms2026-09-10 UTC: p95 443ms2026-09-11 UTC: p95 625ms2026-09-12 UTC: p95 688ms2026-09-13 UTC: p95 498ms2026-09-14 UTC: p95 497ms2026-09-15 UTC: p95 816ms2026-09-16 UTC: p95 486ms2026-09-17 UTC: p95 370ms2026-09-18 UTC: p95 336ms2026-09-19 UTC: p95 376ms2026-09-20 UTC: p95 345ms2026-09-21 UTC: p95 304ms2026-09-22 UTC: p95 466ms2026-09-23 UTC: p95 307ms
Aug 25Sep 8Sep 23
Canada
378msp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 962ms2026-09-04 UTC: p95 434ms2026-09-05 UTC: p95 435ms2026-09-06 UTC: p95 396ms2026-09-07 UTC: p95 653ms2026-09-08 UTC: p95 723ms2026-09-09 UTC: p95 742ms2026-09-10 UTC: p95 776ms2026-09-11 UTC: p95 880ms2026-09-12 UTC: p95 773ms2026-09-13 UTC: p95 713ms2026-09-14 UTC: p95 725ms2026-09-15 UTC: p95 955ms2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 681ms2026-09-19 UTC: p95 481ms2026-09-20 UTC: p95 621ms2026-09-21 UTC: p95 345ms2026-09-22 UTC: p95 660ms2026-09-23 UTC: p95 378ms
Aug 25Sep 8Sep 23
UK
580msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 382ms2026-09-04 UTC: p95 364ms2026-09-05 UTC: p95 383ms2026-09-06 UTC: p95 352ms2026-09-07 UTC: p95 354ms2026-09-08 UTC: p95 322ms2026-09-09 UTC: p95 441ms2026-09-10 UTC: p95 541ms2026-09-11 UTC: p95 475ms2026-09-12 UTC: p95 491ms2026-09-13 UTC: p95 403ms2026-09-14 UTC: p95 400ms2026-09-15 UTC: p95 405ms2026-09-16 UTC: p95 291ms2026-09-17 UTC: p95 296ms2026-09-18 UTC: p95 309ms2026-09-19 UTC: p95 355ms2026-09-20 UTC: p95 428ms2026-09-21 UTC: p95 708ms2026-09-22 UTC: p95 517ms2026-09-23 UTC: p95 580ms
Aug 25Sep 8Sep 23
Southeast Asia
1.2sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.1s2026-09-04 UTC: p95 1.1s2026-09-05 UTC: p95 940ms2026-09-06 UTC: p95 928ms2026-09-07 UTC: p95 951ms2026-09-08 UTC: p95 881ms2026-09-09 UTC: p95 916ms2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 1.0s2026-09-13 UTC: p95 932ms2026-09-14 UTC: p95 1.0s2026-09-15 UTC: p95 1.0s2026-09-16 UTC: p95 920ms2026-09-17 UTC: p95 1.0s2026-09-18 UTC: p95 1.0s2026-09-19 UTC: p95 963ms2026-09-20 UTC: p95 891ms2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 1.2s2026-09-23 UTC: p95 1.2s
Aug 25Sep 8Sep 23
Australia
1.5sp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.4s2026-09-04 UTC: p95 1.5s2026-09-05 UTC: p95 1.6s2026-09-06 UTC: p95 1.4s2026-09-07 UTC: p95 1.5s2026-09-08 UTC: p95 1.5s2026-09-09 UTC: p95 1.5s2026-09-10 UTC: p95 1.4s2026-09-11 UTC: p95 1.2s2026-09-12 UTC: p95 1.5s2026-09-13 UTC: p95 1.4s2026-09-14 UTC: p95 1.6s2026-09-15 UTC: p95 1.6s2026-09-16 UTC: p95 1.4s2026-09-17 UTC: p95 1.5s2026-09-18 UTC: p95 1.6s2026-09-19 UTC: p95 1.6s2026-09-20 UTC: p95 1.5s2026-09-21 UTC: p95 1.6s2026-09-22 UTC: p95 1.3s2026-09-23 UTC: p95 1.5s
Aug 25Sep 8Sep 23
South America
844msp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 903ms2026-09-04 UTC: p95 945ms2026-09-05 UTC: p95 1.0s2026-09-06 UTC: p95 989ms2026-09-07 UTC: p95 873ms2026-09-08 UTC: p95 947ms2026-09-09 UTC: p95 795ms2026-09-10 UTC: p95 903ms2026-09-11 UTC: p95 837ms2026-09-12 UTC: p95 886ms2026-09-13 UTC: p95 921ms2026-09-14 UTC: p95 880ms2026-09-15 UTC: p95 1.1s2026-09-16 UTC: p95 960ms2026-09-17 UTC: p95 777ms2026-09-18 UTC: p95 1.0s2026-09-19 UTC: p95 672ms2026-09-20 UTC: p95 938ms2026-09-21 UTC: p95 847ms2026-09-22 UTC: p95 862ms2026-09-23 UTC: p95 844ms
Aug 25Sep 8Sep 23

Is it WhatsApp, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not WhatsApp -- it cannot diagnose WhatsApp's own systems.

What we measured, function by function

WhatsApp answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: Degraded Answering, but 3.4x slower than its 7-day median.Europe: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    DegradedUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 97msstatus code: 400checked: Sep 23, 2026, 9:11 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach WhatsApp normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Degradedlatency: 473msstatus code: 400checked: Sep 23, 2026, 9:11 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach WhatsApp normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 134msstatus code: 400checked: Sep 23, 2026, 9:09 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach WhatsApp normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 121msstatus code: 400checked: Sep 23, 2026, 9:11 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach WhatsApp normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 748msstatus code: 400checked: Sep 23, 2026, 9:09 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach WhatsApp normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 256msstatus code: 400checked: Sep 23, 2026, 9:12 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach WhatsApp normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 181msstatus code: 400checked: Sep 23, 2026, 9:08 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach WhatsApp normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 309msstatus code: 400checked: Sep 23, 2026, 9:11 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach WhatsApp normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 453msstatus code: 400checked: Sep 23, 2026, 9:09 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach WhatsApp normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 1515msstatus code: 400checked: Sep 23, 2026, 9:08 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach WhatsApp normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using WhatsApp, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We started counting reports for WhatsApp on September 15, 2026.

Recent outages

No outages on record yet for WhatsApp.

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring WhatsApp since August 8, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for WhatsApp covering any window you pick, with our measurements and WhatsApp's own claim at the time, side by side.

Full availability history for WhatsApp: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching WhatsApp, and again when they can reach it again. That is our own measurement from ten regions, not WhatsApp's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

WhatsApp uptime measured by RealUptimeLive, from this page's own readings.
[![WhatsApp uptime measured by RealUptime](https://realuptime.io/outages/whatsapp/badge.svg?days=30)](https://realuptime.io/outages/whatsapp)
<a href="https://realuptime.io/outages/whatsapp"><img src="https://realuptime.io/outages/whatsapp/badge.svg?days=30" alt="WhatsApp uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What WhatsApp's SLA implies, from our measurement

At or above your target

We measured none of downtime for WhatsApp over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from WhatsApp's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: live API
https://graph.facebook.com/v19.0/
secondary
https://web.whatsapp.com/
secondary
https://www.whatsapp.com/
RealUptime is not affiliated with WhatsApp; the name identifies what we measured, and nothing here speaks for WhatsApp's own team. We send a single web request to WhatsApp from 10 regions on our own schedule and time the response. We do not see inside WhatsApp's systems, do not use an account or real transaction, and are not the same signal WhatsApp's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for WhatsApp is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.