Fitbit is Recalling the Ionic Smartwatch

Fitbit Announces Its Ionic Smart Watch

Fitbit announced today that it agreed to a recall of its third-generation smartwatch, Ionic, which dates back to 2017, after receiving 118 reports of burn injuries.

“The lithium-ion battery in the Ionic smartwatch can overheat, posing a burn hazard,” the U.S. Consumer Product Safety Commission revealed, noting that Fitbit sold over one million units of the Ionic in the United States and another 693,000 units internationally.

Windows Intelligence In Your Inbox

Sign up for our new free newsletter to get three time-saving tips each Friday — and get free copies of Paul Thurrott's Windows 11 and Windows 10 Field Guides (normally $9.99) as a special welcome gift!

"*" indicates required fields

This field is for validation purposes and should be left unchanged.

Fitbit will refund all Ionic users for their purchases. To get that started, you can call Fitbit toll-free at 888-925-1764 24 hours a day, 7 days a week. Or you can contact Fitbit online at help.fitbit.com/ionic, or register for the recall here.

Ionic was Fitbit’s third smartwatch: it released the Fitbit Surge in 2014 and then the Fitbit Blaze in 2016. It then release its first Versa smartwatch in 2018, followed by two upgraded versions, and then the Fitbit Sense in 2020.

Tagged with

Share post

Please check our Community Guidelines before commenting

Conversation 3 comments

  • wpcoe

    Premium Member
    02 March, 2022 - 7:00 pm

    <p>Thank heavens the Surge and Blaze didn’t also malfunction to live up to their names.</p>

    • Paul Thurrott

      Premium Member
      02 March, 2022 - 7:18 pm

      <p>lol nice</p>

    • nkhughes

      03 March, 2022 - 9:42 am

      <p>Nice one. </p><p><br></p><p>Funnily enough my Blaze died last year after about 4 years (I think). Screen lit up but nothing displayed. Sticking it in the charging cradle just resulted in it getting a bit too warm for comfort. A bit of internet searching pointed to the the battery being the culprit, and when I looked at what was involved in trying to fix it I decided no.</p>

Windows Intelligence In Your Inbox

Sign up for our new free newsletter to get three time-saving tips each Friday

"*" indicates required fields

This field is for validation purposes and should be left unchanged.

Thurrott © 2024 Thurrott LLC