DEPLOYDatabase

Incident · Recall

Fitbit Ionic burn-hazard recall (~1M US units); $12.25M CPSC penalty in 2025

SCOPE CAP-FLAG: this concerns the discontinued Fitbit Ionic (FB503) standalone smartwatch, a different product generation than current Fitbit trackers, recorded under the fitbit-tracker maker entity. On Mar 2 2022 ~1.0M US units (~1.7M global) were recalled for lithium-ion battery overheating (115 US overheating reports, 78 burns incl. second/third-degree).

In 2025 Fitbit/Google agreed a $12.25M CPSC civil penalty for failing to immediately report the defect during 2018-2020. The most physically-harmful biometric incident in the cohort (real burn injuries).

Occurred 2022-03-02 · Fitbit (Charge / Sense / Versa) at Global · Fitbit · Global · Biometric wearables

How to read this record

Incident records on DEPLOY are compiled from public sources (regulatory filings, news reports, and operator disclosures) and reflect what has been reported and tracked to date. They are not legal findings, determinations of fault, or safety ratings, and may be updated as new information is verified. See the sources below for the underlying references.
Track Fitbit Ionic burn-hazard recall (~1M US units); $12.25M CPSC penalty in 2025

Machine-readable surfaces

Outcomes (2)

  • regulatory actionverified
  • bodily injuryreported

Revision history (2)

  • 2026-06-05 · outcome_class
  • 2026-06-05 · outcome_class

Outcome rows carry verification_posture independently. Revision events carry basis (verified_court_filing, verified_insurance, reported_press, estimate, undisclosed). The framework records outcomes only when verifiable; absence is honest absence, not a claim of no-impact.

Sources (2)

  1. CPSC (recall) · https://www.cpsc.gov/Recalls/2022/Fitbit-Recalls-Ionic-Smartwatches-Due-to-Burn-Hazard-One-Million-Sold-in-the-U-S
  2. CPSC (penalty) · https://www.cpsc.gov/Newsroom/News-Releases/2025/Fitbit-Agrees-to-Pay-12-25-Million-Civil-Penalty-for-Failure-to-Immediately-Report-Serious-Burn-Hazard-with-Ionic-Smartwatches

Common questions

What happened in Fitbit Ionic burn-hazard recall (~1M US units); $12.25M CPSC penalty in 2025?
SCOPE CAP-FLAG: this concerns the discontinued Fitbit Ionic (FB503) standalone smartwatch, a different product generation than current Fitbit trackers, recorded under the fitbit-tracker maker entity. On Mar 2 2022 ~1.0M US units (~1.7M global) were recalled for lithium-ion battery overheating (115 US overheating reports, 78 burns incl. second/third-degree). In 2025 Fitbit/Google agreed a $12.25M CPSC civil penalty for failing to immediately report the defect during 2018-2020. The most physically-harmful biometric incident in the cohort (real burn injuries).
When did this incident occur?
The incident is recorded as occurring on March 2, 2022 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.
What robot was involved in Fitbit Ionic burn-hazard recall (~1M US units); $12.25M CPSC penalty in 2025?
Fitbit (Charge / Sense / Versa) by Fitbit is the recorded robot involved in this incident at Global.
Has anyone responded to Fitbit Ionic burn-hazard recall (~1M US units); $12.25M CPSC penalty in 2025?
No responses to this incident are recorded on the DEPLOY registry. Operators, manufacturers, or affected parties can submit responses to the editorial team; absence is not a guarantee no response was issued.
What is the current status of Fitbit Ionic burn-hazard recall (~1M US units); $12.25M CPSC penalty in 2025?
This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.
Methodology: Verified · 2 sources (no primary) · last reviewed 2026-07-21

Verification posture

Verified

Low confidence

Review state

Stable

Last reviewed 2026-07-21

Sources by quality tier

2
unclassified
Unclassified source

The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.

Methodology surface for Fitbit Ionic burn-hazard recall (~1M US units); $12.25M CPSC penalty in 2025.

Deploy Watch

Track this incident.

We notify you when the regulator updates the record, the remedy status changes, or a related incident surfaces.

Canonical ID 319d4efa-4c90-406f-a92d-580900b58eee