# Whoop (5.0 / MG) at Boston: deployment

Canonical ID: `42f20210-aa50-4feb-a8dd-b8f542fd6a00`

Whoop 4.0 / MG aggregate global deployment. Whoop has hundreds of thousands of active subscribers. No site-specific tracking.

**Trust tier:** Catalog entry · 1 source · not yet field-verified

_Last updated: 2026-06-07_

- **Slug:** whoop-global-aggregate
- **Status:** operational
- **Model:** [Whoop (5.0 / MG)](/models/whoop-mg.md) (id: `82591feb-716d-4033-ae7e-611f253022cd`)
- **Company:** [Whoop](/companies/whoop.md) (id: `df3db3a4-f255-4eb2-b9a4-5f4e56a09ee7`)
- **Location:** [Boston](/locations/boston-ma.md) (id: `1cfe4d12-302a-462f-921f-564e35951774`)

## Verification log (0, append-only)

_No verifications recorded._

## Sources (1)

1. https://www.whoop.com/

## Common questions

### What is the Whoop (5.0 / MG) deployment at Boston?

Whoop (5.0 / MG), built by Whoop, is recorded as a deployment at Boston on the DEPLOY registry. Whoop operates the deployment directly.

### Who operates Whoop (5.0 / MG) at Boston?

Whoop, the manufacturer of Whoop (5.0 / MG), operates this deployment directly. This is a maker-deploys-its-own-product arrangement rather than a customer pilot.

### Have there been incidents at the Whoop (5.0 / MG) deployment at Boston?

No active incidents affecting this deployment are recorded on the DEPLOY registry. Absence of recorded incidents is not a guarantee no incident occurred; DEPLOY records only sourced incidents and suppresses retracted ones.


_API: GET /v1/robots/42f20210-aa50-4feb-a8dd-b8f542fd6a00 · feeds: GET /v1/feeds?deploymentId=42f20210-aa50-4feb-a8dd-b8f542fd6a00 · canonical URL: /deployments/whoop-global-aggregate_