Skip to content

Outage tracker / WhatsApp

Is WhatsApp down?

I'm having a problem

Checks passingchecked 1 minute ago

Our checks of WhatsApp pass from all 10 regions we check.

As of Nov 5, 2026, 3:03 PM UTC, RealUptime's checks of WhatsApp passed in all 10 regions that returned a reading.

Front-door checks

Our checks of WhatsApp did not fail from two or more distant regions in the 89 days we have checked it (since Aug 8, 2026). This does not show WhatsApp works for users.

Email me when our checks of WhatsApp fail from two or more distant regions

One email when our checks of WhatsApp fail from two or more distant regions, and one when they pass, after you confirm the address. No account, no card.

This is our own reading from outside. It is not WhatsApp's official status.

our check readinglive · checked Nov 5, 2026, 3:03 PM UTC
US-East683 msChecks passing
US-West724 msChecks passing
Europe129 msChecks passing
Asia-Pacific1075 msChecks passing
US-Central826 msChecks passing
Canada1005 msChecks passing
UK537 msChecks passing
Southeast Asia1305 msChecks passing
Australia2774 msChecks passing
South America2046 msChecks passing
their status pagetheir claim, not our reading

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

WhatsApp response time, by region

US-East
957msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 736ms2026-10-08 UTC: p95 719ms2026-10-09 UTC: p95 753ms2026-10-10 UTC: p95 775ms2026-10-11 UTC: p95 600ms2026-10-12 UTC: p95 470ms2026-10-13 UTC: p95 481ms2026-10-14 UTC: p95 356ms2026-10-15 UTC: p95 352ms2026-10-16 UTC: p95 434ms2026-10-17 UTC: p95 841ms2026-10-18 UTC: p95 921ms2026-10-19 UTC: p95 779ms2026-10-20 UTC: p95 723ms2026-10-21 UTC: p95 678ms2026-10-22 UTC: p95 647ms2026-10-23 UTC: p95 620ms2026-10-24 UTC: p95 617ms2026-10-25 UTC: p95 595ms2026-10-26 UTC: p95 939ms2026-10-27 UTC: p95 663ms2026-10-28 UTC: p95 693ms2026-10-29 UTC: p95 691ms2026-10-30 UTC: p95 682ms2026-10-31 UTC: p95 822ms2026-11-01 UTC: p95 749ms2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.1s2026-11-05 UTC: p95 957ms
Oct 7Oct 21Nov 5
US-West
1.2sp95 · latest
2.5s1.3s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 494ms2026-10-08 UTC: p95 480ms2026-10-09 UTC: p95 1.0s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 413ms2026-10-12 UTC: p95 461ms2026-10-13 UTC: p95 524ms2026-10-14 UTC: p95 472ms2026-10-15 UTC: p95 460ms2026-10-16 UTC: p95 520ms2026-10-17 UTC: p95 2.0s2026-10-18 UTC: p95 2.3s2026-10-19 UTC: p95 2.3s2026-10-20 UTC: p95 2.2s2026-10-21 UTC: p95 2.0s2026-10-22 UTC: p95 2.2s2026-10-23 UTC: p95 2.2s2026-10-24 UTC: p95 2.1s2026-10-25 UTC: p95 2.1s2026-10-26 UTC: p95 2.2s2026-10-27 UTC: p95 2.2s2026-10-28 UTC: p95 2.1s2026-10-29 UTC: p95 2.1s2026-10-30 UTC: p95 2.1s2026-10-31 UTC: p95 2.0s2026-11-01 UTC: p95 2.3s2026-11-02 UTC: p95 2.1s2026-11-03 UTC: p95 1.6s2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 1.2s
Oct 7Oct 21Nov 5
Europe
708msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 406ms2026-10-08 UTC: p95 326ms2026-10-09 UTC: p95 326ms2026-10-10 UTC: p95 338ms2026-10-11 UTC: p95 286ms2026-10-12 UTC: p95 315ms2026-10-13 UTC: p95 274ms2026-10-14 UTC: p95 313ms2026-10-15 UTC: p95 313ms2026-10-16 UTC: p95 321ms2026-10-17 UTC: p95 335ms2026-10-18 UTC: p95 404ms2026-10-19 UTC: p95 484ms2026-10-20 UTC: p95 356ms2026-10-21 UTC: p95 352ms2026-10-22 UTC: p95 446ms2026-10-23 UTC: p95 406ms2026-10-24 UTC: p95 314ms2026-10-25 UTC: p95 420ms2026-10-26 UTC: p95 452ms2026-10-27 UTC: p95 409ms2026-10-28 UTC: p95 369ms2026-10-29 UTC: p95 379ms2026-10-30 UTC: p95 367ms2026-10-31 UTC: p95 344ms2026-11-01 UTC: p95 393ms2026-11-02 UTC: p95 674ms2026-11-03 UTC: p95 1.6s2026-11-04 UTC: p95 1.8s2026-11-05 UTC: p95 708ms
Oct 7Oct 21Nov 5
Asia-Pacific
2.0sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 776ms2026-10-08 UTC: p95 825ms2026-10-09 UTC: p95 832ms2026-10-10 UTC: p95 752ms2026-10-11 UTC: p95 790ms2026-10-12 UTC: p95 825ms2026-10-13 UTC: p95 849ms2026-10-14 UTC: p95 806ms2026-10-15 UTC: p95 925ms2026-10-16 UTC: p95 831ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.4s2026-10-23 UTC: p95 1.5s2026-10-24 UTC: p95 1.6s2026-10-25 UTC: p95 1.5s2026-10-26 UTC: p95 1.8s2026-10-27 UTC: p95 1.7s2026-10-28 UTC: p95 1.5s2026-10-29 UTC: p95 1.5s2026-10-30 UTC: p95 1.5s2026-10-31 UTC: p95 1.5s2026-11-01 UTC: p95 1.6s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 2.3s2026-11-04 UTC: p95 2.5s2026-11-05 UTC: p95 2.0s
Oct 7Oct 21Nov 5
US-Central
928msp95 · latest
2.5s1.3s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 466ms2026-10-08 UTC: p95 912ms2026-10-09 UTC: p95 485ms2026-10-10 UTC: p95 608ms2026-10-11 UTC: p95 416ms2026-10-12 UTC: p95 687ms2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 818ms2026-10-15 UTC: p95 561ms2026-10-16 UTC: p95 583ms2026-10-17 UTC: p95 772ms2026-10-18 UTC: p95 745ms2026-10-19 UTC: p95 786ms2026-10-20 UTC: p95 892ms2026-10-21 UTC: p95 949ms2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 959ms2026-10-24 UTC: p95 1.2s2026-10-25 UTC: p95 981ms2026-10-26 UTC: p95 1.1s2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 2.0s2026-10-29 UTC: p95 1.8s2026-10-30 UTC: p95 1.9s2026-10-31 UTC: p95 2.0s2026-11-01 UTC: p95 2.0s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 1.0s2026-11-04 UTC: p95 1.4s2026-11-05 UTC: p95 928ms
Oct 7Oct 21Nov 5
Canada
2.0sp95 · latest
2.5s1.3s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 905ms2026-10-09 UTC: p95 648ms2026-10-10 UTC: p95 503ms2026-10-11 UTC: p95 615ms2026-10-12 UTC: p95 530ms2026-10-13 UTC: p95 827ms2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.5s2026-10-16 UTC: p95 956ms2026-10-17 UTC: p95 1.8s2026-10-18 UTC: p95 2.1s2026-10-19 UTC: p95 2.2s2026-10-20 UTC: p95 2.0s2026-10-21 UTC: p95 2.1s2026-10-22 UTC: p95 2.0s2026-10-23 UTC: p95 2.0s2026-10-24 UTC: p95 2.0s2026-10-25 UTC: p95 2.0s2026-10-26 UTC: p95 2.0s2026-10-27 UTC: p95 1.6s2026-10-28 UTC: p95 1.9s2026-10-29 UTC: p95 1.9s2026-10-30 UTC: p95 1.8s2026-10-31 UTC: p95 1.7s2026-11-01 UTC: p95 2.0s2026-11-02 UTC: p95 2.1s2026-11-03 UTC: p95 1.6s2026-11-04 UTC: p95 1.0s2026-11-05 UTC: p95 2.0s
Oct 7Oct 21Nov 5
UK
1.4sp95 · latest
2.5s1.3s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 347ms2026-10-08 UTC: p95 449ms2026-10-09 UTC: p95 396ms2026-10-10 UTC: p95 424ms2026-10-11 UTC: p95 405ms2026-10-12 UTC: p95 398ms2026-10-13 UTC: p95 413ms2026-10-14 UTC: p95 428ms2026-10-15 UTC: p95 413ms2026-10-16 UTC: p95 442ms2026-10-17 UTC: p95 785ms2026-10-18 UTC: p95 736ms2026-10-19 UTC: p95 602ms2026-10-20 UTC: p95 618ms2026-10-21 UTC: p95 622ms2026-10-22 UTC: p95 704ms2026-10-23 UTC: p95 546ms2026-10-24 UTC: p95 505ms2026-10-25 UTC: p95 619ms2026-10-26 UTC: p95 620ms2026-10-27 UTC: p95 656ms2026-10-28 UTC: p95 746ms2026-10-29 UTC: p95 619ms2026-10-30 UTC: p95 726ms2026-10-31 UTC: p95 588ms2026-11-01 UTC: p95 576ms2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 2.0s2026-11-04 UTC: p95 2.1s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
Southeast Asia
2.1sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 958ms2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.6s2026-10-15 UTC: p95 1.4s2026-10-16 UTC: p95 1.5s2026-10-17 UTC: p95 1.9s2026-10-18 UTC: p95 2.1s2026-10-19 UTC: p95 2.3s2026-10-20 UTC: p95 1.8s2026-10-21 UTC: p95 2.1s2026-10-22 UTC: p95 1.7s2026-10-23 UTC: p95 1.9s2026-10-24 UTC: p95 1.6s2026-10-25 UTC: p95 2.1s2026-10-26 UTC: p95 2.0s2026-10-27 UTC: p95 1.8s2026-10-28 UTC: p95 1.8s2026-10-29 UTC: p95 1.5s2026-10-30 UTC: p95 1.7s2026-10-31 UTC: p95 1.6s2026-11-01 UTC: p95 2.0s2026-11-02 UTC: p95 1.6s2026-11-03 UTC: p95 1.9s2026-11-04 UTC: p95 2.0s2026-11-05 UTC: p95 2.1s
Oct 7Oct 21Nov 5
Australia
3.6sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.5s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 1.5s2026-10-15 UTC: p95 1.4s2026-10-16 UTC: p95 1.3s2026-10-17 UTC: p95 2.1s2026-10-18 UTC: p95 2.5s2026-10-19 UTC: p95 2.3s2026-10-20 UTC: p95 2.2s2026-10-21 UTC: p95 2.3s2026-10-22 UTC: p95 2.5s2026-10-23 UTC: p95 2.4s2026-10-24 UTC: p95 2.4s2026-10-25 UTC: p95 2.2s2026-10-26 UTC: p95 2.3s2026-10-27 UTC: p95 2.2s2026-10-28 UTC: p95 2.4s2026-10-29 UTC: p95 2.4s2026-10-30 UTC: p95 2.3s2026-10-31 UTC: p95 2.3s2026-11-01 UTC: p95 2.3s2026-11-02 UTC: p95 2.6s2026-11-03 UTC: p95 3.6s2026-11-04 UTC: p95 3.7s2026-11-05 UTC: p95 3.6s
Oct 7Oct 21Nov 5
South America
2.0sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 698ms2026-10-08 UTC: p95 653ms2026-10-09 UTC: p95 850ms2026-10-10 UTC: p95 847ms2026-10-11 UTC: p95 874ms2026-10-12 UTC: p95 824ms2026-10-13 UTC: p95 908ms2026-10-14 UTC: p95 841ms2026-10-15 UTC: p95 727ms2026-10-16 UTC: p95 733ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 8.5s2026-10-24 UTC: p95 1.5s2026-10-25 UTC: p95 1.4s2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 2.2s2026-10-29 UTC: p95 1.3s2026-10-30 UTC: p95 1.4s2026-10-31 UTC: p95 1.3s2026-11-01 UTC: p95 2.3s2026-11-02 UTC: p95 2.5s2026-11-03 UTC: p95 6.0s2026-11-04 UTC: p95 5.0s2026-11-05 UTC: p95 2.0s
Oct 7Oct 21Nov 5

Check your own site while you wait on WhatsApp

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 web 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.

  • WebprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • ChannelsUS-East: Checks passingUS-West: Awaiting dataEurope: Awaiting dataAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Awaiting dataSoutheast Asia: Awaiting dataAustralia: Checks passingSouth America: Checks passing
  • Click to chatUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • DownloadsUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 683msstatus code: 200checked: Nov 5, 2026, 3:02 PM 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
      Checks passinglatency: 724msstatus code: 200checked: Nov 5, 2026, 3:03 PM 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
      Checks passinglatency: 826msstatus code: 200checked: Nov 5, 2026, 3:03 PM 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
      Checks passinglatency: 1005msstatus code: 200checked: Nov 5, 2026, 3:03 PM 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
    Checks passinglatency: 2046msstatus code: 200checked: Nov 5, 2026, 3:03 PM 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 129msstatus code: 200checked: Nov 5, 2026, 3:03 PM 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
      Checks passinglatency: 537msstatus code: 200checked: Nov 5, 2026, 3:03 PM 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1075msstatus code: 200checked: Nov 5, 2026, 3:03 PM 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
      Checks passinglatency: 1305msstatus code: 200checked: Nov 5, 2026, 3:01 PM 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
      Checks passinglatency: 2774msstatus code: 200checked: Nov 5, 2026, 3:02 PM 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 probe events

No probe events on record yet for WhatsApp.

check 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 check readings and WhatsApp's own claim at the time, side by side.

Full check history for WhatsApp: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Put this badge in your README

WhatsApp uptime by RealUptime's checksLive, from this page's own readings.
[![WhatsApp uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is WhatsApp down?", https://realuptime.io/outages/whatsapp. The readings change with every check, so give the date you read them.

How our checks compare with WhatsApp's stated SLA

At or above your target

Our checks of WhatsApp failed for none over the last 30 days, which is 100% uptime by our checks. A 99.9% target allows 43 minutes over that period.

Our checks show no gap in this period. That does not rule out one you saw.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, 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

primary
https://web.whatsapp.com/
secondary
https://www.whatsapp.com/
secondary
https://api.whatsapp.com/send/?phone=14155238886
secondary
https://www.whatsapp.com/channel/0029Va7vMjc9WtC0o8iXG63t
secondary
https://www.whatsapp.com/download
RealUptime is not affiliated with WhatsApp; the name identifies what we checked, 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. What we check for WhatsApp is its front door only: a passing check means the endpoints above answered, not that the underlying product or account features work. Read the full methodology.