Skip to main content

Is WHOOP Down?

No — WHOOP is up

We cannot measure WHOOP directly — it blocks automated checks — but WHOOP's own status page currently reports no issues.

Last checked · checks run every 6 hours

Official status page: https://status.whoop.com

Why there is no uptime figure on this page

The last time we fetched WHOOP's page directly, the origin answered and turned our client away rather than serving the page. That answer tells us the origin was reachable and responding, but it is a response about our automation, not about whether WHOOP works for you.

A percentage built from those checks would measure our own access, so we do not publish one. What this page does show is each region's most recent result and WHOOP's own status feed, which you can weigh yourself.

30-day history

Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: blocked from automated checks
Aug 1: blocked from automated checks
Aug 2: blocked from automated checks
Aug 3: blocked from automated checks
Aug 4: blocked from automated checks
Aug 5: blocked from automated checks
Aug 6: blocked from automated checks
Aug 7: blocked from automated checks
Aug 8: blocked from automated checks
Aug 9: blocked from automated checks
Aug 10: blocked from automated checks
Aug 11: blocked from automated checks
Aug 12: blocked from automated checks
Aug 13: blocked from automated checks
Aug 14: blocked from automated checks
Aug 15: blocked from automated checks
Aug 16: blocked from automated checks
Aug 17: blocked from automated checks
Aug 18: blocked from automated checks
Aug 19: blocked from automated checks
Aug 20: blocked from automated checks
Aug 21: blocked from automated checks
Aug 22: blocked from automated checks
Aug 23: blocked from automated checks
Jul 25 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
edge reachable

A static asset loaded in 23ms. That proves the edge is up, but not that the site works.

arn
edge reachable

A static asset loaded in 21ms. That proves the edge is up, but not that the site works.

bom
edge reachable

A static asset loaded in 28ms. That proves the edge is up, but not that the site works.

cdg
edge reachable

A static asset loaded in 18ms. That proves the edge is up, but not that the site works.

dfw
edge reachable

A static asset loaded in 21ms. That proves the edge is up, but not that the site works.

sin
edge reachable

A static asset loaded in 20ms. That proves the edge is up, but not that the site works.

sjc
edge reachable

A static asset loaded in 23ms. That proves the edge is up, but not that the site works.

syd
edge reachable

A static asset loaded in 14ms. That proves the edge is up, but not that the site works.

yyz
edge reachable

A static asset loaded in 19ms. That proves the edge is up, but not that the site works.

What WHOOP does

WHOOP sells a screenless fitness strap sold with a membership, measuring sleep, strain and recovery continuously. All of the readouts live in the companion mobile app rather than on the band itself, so the app is the only way to see anything the device records, and an outage removes the interface rather than the measurement.

What an outage looks like

The app opens but shows yesterday's recovery score, or a blank dashboard where today's metrics belong. Data will not sync from the strap, so the band fills with unsent readings. Login fails on a device that was signed out, or after an app update. Teams, coaching insights and third party integrations such as connected fitness apps stop updating while the core app is otherwise usable.

What to do about it

Check status.whoop.com, which lists Login, Data uploads and processing, Core app features, WHOOP AI, Teams and third party integrations separately, along with WHOOP Unite, the web app and the shop. Keep wearing the strap: it continues recording, and readings upload once processing recovers. Do not sign out to fix a sync problem, since Login is often the component that is failing.

Is it down for everyone, or just you?

If this page says WHOOP is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

WHOOP outage FAQ

Is my strap still recording while the app shows nothing?
Yes. The band collects data continuously and stores it until it can upload, and WHOOP tracks data uploads and processing as a component separate from the rest of the app. A blank or stale dashboard means the readings have not been received and processed, not that they were never taken. They generally appear once the backlog clears after recovery.
Should I sign out and back in to fix syncing?
No. Login is tracked as its own component and is frequently affected during an incident, so signing out risks not being able to sign back in until the outage ends. That turns a display problem into losing access to the app entirely. Force-closing and reopening the app, or waiting, is safer than clearing the session.
Will my recovery and sleep scores be wrong afterwards?
They are calculated from the stored readings once uploaded, so a delay generally shifts when a score appears rather than changing it. What can genuinely be missing is a period where the strap was not worn or was out of battery during the incident, which is a gap in collection rather than a processing delay. Charging on schedule matters more than the outage.
Do connected apps keep receiving my data?
Not necessarily. Third party integrations are listed as their own component, so exports to other fitness platforms can stop while the WHOOP app itself works. If a training app is missing WHOOP data but your dashboard looks current, the integration is the failure. Those usually backfill once restored, though the timing depends on the receiving service.
Can I see my data on the web instead?
There is a web app and it is tracked separately from the mobile app, so it is worth trying when the phone app is failing. Both read the same processed data, so if the failure is in uploads or processing rather than the interface, the web app shows the same stale figures. It helps for interface problems, not for data delays.

How we measure this

  • We request WHOOP's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where WHOOP publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it — and when WHOOP blocks our checks entirely, we report the vendor's own status directly.

Get alerted when WHOOP goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required