User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Health
weightwatchers.com · Health
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 557 ms · 6 min ago.
No status feed
WW (WeightWatchers) does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 12:30 | 0 | 0.0 | 989 ms | 0 |
| 12:45 | 0 | 0.0 | 467 ms | 0 |
| 13:00 | 0 | 0.0 | 781 ms | 0 |
| 13:15 | 0 | 0.0 | 553 ms | 0 |
| 13:30 | 0 | 0.0 | 501 ms | 0 |
| 13:45 | 0 | 0.0 | 690 ms | 0 |
| 14:00 | 0 | 0.0 | 531 ms | 0 |
| 14:15 | 0 | 0.0 | 1067 ms | 0 |
| 14:30 | 0 | 0.0 | 470 ms | 0 |
| 14:45 | 0 | 0.0 | 577 ms | 0 |
| 15:00 | 0 | 0.0 | 451 ms | 0 |
| 15:15 | 0 | 0.0 | 563 ms | 0 |
| 15:30 | 0 | 0.0 | 565 ms | 0 |
| 15:45 | 0 | 0.0 | 524 ms | 0 |
| 16:00 | 0 | 0.0 | 388 ms | 0 |
| 16:15 | 0 | 0.0 | 463 ms | 0 |
| 16:30 | 0 | 0.0 | 469 ms | 0 |
| 16:45 | 0 | 0.0 | 743 ms | 0 |
| 17:00 | 0 | 0.0 | 669 ms | 0 |
| 17:15 | 0 | 0.0 | 323 ms | 0 |
| 17:30 | 0 | 0.0 | 428 ms | 0 |
| 17:45 | 0 | 0.0 | 547 ms | 0 |
| 18:00 | 0 | 0.0 | 1377 ms | 0 |
| 18:15 | 0 | 0.0 | 376 ms | 0 |
| 18:30 | 0 | 0.0 | 463 ms | 0 |
| 18:45 | 0 | 0.0 | 407 ms | 0 |
| 19:00 | 0 | 0.0 | 506 ms | 0 |
| 19:15 | 0 | 0.0 | 623 ms | 0 |
| 19:30 | 0 | 0.0 | 481 ms | 0 |
| 19:45 | 0 | 0.0 | 1254 ms | 0 |
| 20:00 | 0 | 0.0 | 552 ms | 0 |
| 20:15 | 0 | 0.0 | 668 ms | 0 |
| 20:30 | 0 | 0.0 | 442 ms | 0 |
| 20:45 | 0 | 0.0 | 1124 ms | 0 |
| 21:00 | 0 | 0.0 | 376 ms | 0 |
| 21:15 | 0 | 0.0 | 459 ms | 0 |
| 21:30 | 0 | 0.0 | 557 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for WW (WeightWatchers) yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when WW (WeightWatchers) goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send WW (WeightWatchers) alerts to Slack, Discord or a webhook — free.
We track WW (WeightWatchers) (weightwatchers.com) as part of the Health group. Live checks and user reports.
WW (WeightWatchers) has no official status feed we can read, so this page relies on our own checks and user reports.
Common problems for health services: patient portal and member sign-in failures, prescription refills or appointment booking not going through, and app errors.
Measured uptime from our checks: 100% over 1 day of checks. No public incidents logged since monitoring began 1 day ago.
Response time over the last 24 hours: 595 ms average, 245–2049 ms range across 68 successful checks.
Checks are succeeding and user reports are near the baseline.
We have not recorded a public WW (WeightWatchers) incident since monitoring began 1 day ago.
From our own checks: 100% over 1 day of checks.
595 ms on average over the last 24 hours (245–2049 ms).
Not one we can read. This page uses independent checks of weightwatchers.com and user reports.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For health services, watch for patient portal and member sign-in failures, prescription refills or appointment booking not going through, and app errors. If many people report WW (WeightWatchers) here at once, the problem is on WW (WeightWatchers)'s side.