Skip to content

Outage tracker / WhatsApp

Is WhatsApp down?

Short linkrlup.io/down/whatsapp

I'm having a problem

Operationalchecked moments ago

We reached WhatsApp from all 10 regions we check.

As of Oct 5, 2026, 9:04 PM UTC, WhatsApp answered RealUptime's probes in all 10 regions that returned a reading.

Reachability verified

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

Email me the next time we see WhatsApp go down

Measured by our own probes from ten regions, not WhatsApp's status page. One email when a measured outage opens and one when it closes, after you confirm the address. No account, no card.

our independent probeslive · checked Oct 5, 2026, 9:04 PM UTC
US-East938 msOperational
US-West417 msOperational
Europe286 msOperational
Asia-Pacific139 msOperational
US-Central277 msOperational
Canada488 msOperational
UK367 msOperational
Southeast Asia281 msOperational
Australia1349 msOperational
South America156 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
727msp95 · 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-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 327ms2026-09-24 UTC: p95 419ms2026-09-25 UTC: p95 320ms2026-09-26 UTC: p95 319ms2026-09-27 UTC: p95 501ms2026-09-28 UTC: p95 449ms2026-09-29 UTC: p95 397ms2026-09-30 UTC: p95 511ms2026-10-01 UTC: p95 596ms2026-10-02 UTC: p95 682ms2026-10-03 UTC: p95 732ms2026-10-04 UTC: p95 699ms2026-10-05 UTC: p95 727ms
Sep 6Sep 20Oct 5
US-West
556msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-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 800ms2026-09-24 UTC: p95 374ms2026-09-25 UTC: p95 617ms2026-09-26 UTC: p95 557ms2026-09-27 UTC: p95 469ms2026-09-28 UTC: p95 478ms2026-09-29 UTC: p95 381ms2026-09-30 UTC: p95 392ms2026-10-01 UTC: p95 489ms2026-10-02 UTC: p95 485ms2026-10-03 UTC: p95 457ms2026-10-04 UTC: p95 484ms2026-10-05 UTC: p95 556ms
Sep 6Sep 20Oct 5
Europe
376msp95 · 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-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 162ms2026-09-24 UTC: p95 213ms2026-09-25 UTC: p95 374ms2026-09-26 UTC: p95 430ms2026-09-27 UTC: p95 360ms2026-09-28 UTC: p95 394ms2026-09-29 UTC: p95 359ms2026-09-30 UTC: p95 355ms2026-10-01 UTC: p95 402ms2026-10-02 UTC: p95 330ms2026-10-03 UTC: p95 332ms2026-10-04 UTC: p95 321ms2026-10-05 UTC: p95 376ms
Sep 6Sep 20Oct 5
Asia-Pacific
855msp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 884ms2026-09-24 UTC: p95 710ms2026-09-25 UTC: p95 590ms2026-09-26 UTC: p95 709ms2026-09-27 UTC: p95 775ms2026-09-28 UTC: p95 731ms2026-09-29 UTC: p95 798ms2026-09-30 UTC: p95 765ms2026-10-01 UTC: p95 855ms2026-10-02 UTC: p95 827ms2026-10-03 UTC: p95 809ms2026-10-04 UTC: p95 818ms2026-10-05 UTC: p95 855ms
Sep 6Sep 20Oct 5
US-Central
1.2sp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 691ms2026-09-24 UTC: p95 830ms2026-09-25 UTC: p95 450ms2026-09-26 UTC: p95 487ms2026-09-27 UTC: p95 505ms2026-09-28 UTC: p95 414ms2026-09-29 UTC: p95 495ms2026-09-30 UTC: p95 467ms2026-10-01 UTC: p95 564ms2026-10-02 UTC: p95 552ms2026-10-03 UTC: p95 497ms2026-10-04 UTC: p95 413ms2026-10-05 UTC: p95 1.2s
Sep 6Sep 20Oct 5
Canada
1.1sp95 · 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-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 378ms2026-09-24 UTC: p95 515ms2026-09-25 UTC: p95 474ms2026-09-26 UTC: p95 394ms2026-09-27 UTC: p95 559ms2026-09-28 UTC: p95 454ms2026-09-29 UTC: p95 390ms2026-09-30 UTC: p95 497ms2026-10-01 UTC: p95 692ms2026-10-02 UTC: p95 564ms2026-10-03 UTC: p95 712ms2026-10-04 UTC: p95 453ms2026-10-05 UTC: p95 1.1s
Sep 6Sep 20Oct 5
UK
319msp95 · 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-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 525ms2026-09-24 UTC: p95 544ms2026-09-25 UTC: p95 458ms2026-09-26 UTC: p95 491ms2026-09-27 UTC: p95 554ms2026-09-28 UTC: p95 552ms2026-09-29 UTC: p95 526ms2026-09-30 UTC: p95 494ms2026-10-01 UTC: p95 431ms2026-10-02 UTC: p95 393ms2026-10-03 UTC: p95 396ms2026-10-04 UTC: p95 374ms2026-10-05 UTC: p95 319ms
Sep 6Sep 20Oct 5
Southeast Asia
1.1sp95 · 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-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.3s2026-09-24 UTC: p95 818ms2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 1.0s2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 1.0s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 997ms2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.0s2026-10-05 UTC: p95 1.1s
Sep 6Sep 20Oct 5
Australia
1.3sp95 · 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-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.5s2026-09-24 UTC: p95 1.5s2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.5s2026-09-27 UTC: p95 1.6s2026-09-28 UTC: p95 1.5s2026-09-29 UTC: p95 1.4s2026-09-30 UTC: p95 1.6s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.3s2026-10-03 UTC: p95 1.3s2026-10-04 UTC: p95 1.6s2026-10-05 UTC: p95 1.3s
Sep 6Sep 20Oct 5
South America
807msp95 · 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-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 835ms2026-09-24 UTC: p95 917ms2026-09-25 UTC: p95 835ms2026-09-26 UTC: p95 971ms2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 1.0s2026-09-29 UTC: p95 873ms2026-09-30 UTC: p95 982ms2026-10-01 UTC: p95 831ms2026-10-02 UTC: p95 834ms2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 951ms2026-10-05 UTC: p95 807ms
Sep 6Sep 20Oct 5

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 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: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIUS-East: OperationalUS-West: OperationalEurope: 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
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 938msstatus code: 200checked: Oct 5, 2026, 9:04 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
      Operationallatency: 417msstatus code: 200checked: Oct 5, 2026, 9:01 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
      Operationallatency: 277msstatus code: 200checked: Oct 5, 2026, 9:01 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
      Operationallatency: 488msstatus code: 200checked: Oct 5, 2026, 9:02 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
    Operationallatency: 156msstatus code: 200checked: Oct 5, 2026, 8:59 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 286msstatus code: 200checked: Oct 5, 2026, 9: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
      Operationallatency: 367msstatus code: 200checked: Oct 5, 2026, 9: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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 139msstatus code: 200checked: Oct 5, 2026, 9:04 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
      Operationallatency: 281msstatus code: 200checked: Oct 5, 2026, 9:03 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
      Operationallatency: 1349msstatus code: 200checked: Oct 5, 2026, 9:01 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 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.

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

primary
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. What we check for WhatsApp proves reachability only: the endpoints above answer, but that does not confirm the underlying product or account features work. Read the full methodology.

Related services

BlueskyDiscordFacebookGoogle MeetInstagram