The Basis Peak recall is the part of the Basis story that gets remembered, and it is also the part most often misremembered. The watch was not recalled because of a manufacturing batch. It was not recalled because of a charging cable. It was recalled because Intel concluded, after months of trying to fix the problem in software, that the battery inside the Peak could overheat under normal use and burn the person wearing it.

This page is the factual record. Dates, the language Intel used, the formal notice number, and what the company actually offered owners. If you came here from the parent archive page on the Basis Peak, this is the deep version of the recall section.

The timeline, in order

The recall is usually described as a June 2016 event. That is when the refund program started, but the chain of events runs back at least seven months earlier.

November 2015 — the firmware update. Intel pushed a firmware update for the Peak intended to improve optical heart-rate performance and tweak the device’s thermal management. The update was rolled out over the air to all Peaks then in service. Within weeks, the Basis support forum, the company’s social channels, and a handful of reviewer-adjacent blogs started showing reports of the watch running noticeably hot on the wrist. A small number of users reported skin irritation. Intel did not publicly link the two at the time.

March 2016 — the attempted fix. Intel issued a second firmware update intended to address the overheating reports. The change, described by the company at the time as a software adjustment to the device’s charging and thermal behavior, was supposed to keep the battery’s temperature inside a safer envelope. It did not. Burn and blister complaints continued through the spring of 2016, and the touchscreen-lag and HR-tracking issues that had dogged the watch since launch (cataloged in our Basis Peak retrospective review) did not help Intel’s case that the device was salvageable. We cover the deeper “why” of this failure mode in why the Basis Peak failed, but the short version is that a thermal problem in a sealed case with a non-replaceable cell is rarely fixable in firmware once it is in the field.

June 2016 — voluntary refund program begins. Intel announced that it could no longer guarantee the Peak would not overheat and that no further firmware fix was coming. The company stopped selling the watch, took down the product pages, and opened a refund portal for existing owners. The refund was full retail value with no return required. Customers were told to stop wearing the Peak immediately. This is the date most people now cite as “the recall,” and in commercial terms it was. Sales stopped, refunds opened, the product was effectively dead.

August 4, 2016 — the formal CPSC and Health Canada notice. The joint regulatory notice, US Consumer Product Safety Commission recall number 16-235 with a parallel Health Canada filing, made the recall official. The notice put the unit count at roughly 200,000 across the two countries (the bulk in the US) and used the language Intel and the CPSC had agreed on: “the battery in the watch can overheat, posing burn and blister hazards.” That phrasing matters because it became the de facto description of the failure mode in every subsequent press piece. At the time of the notice, Intel reported about two dozen confirmed burn or blister incidents and several reports of property damage.

December 31, 2016 — the cloud shutdown. Intel shut down the mybasis.com servers, removed the iOS and Android apps from the stores, and stopped honoring data exports. Anybody who had ignored the recall and kept wearing their Peak past New Year’s Eve 2016 ended up with a watch that could still take a heart-rate reading but had nowhere to send it. The shutdown is the canonical example we point to in our broader piece on wearables and cloud dependency. We go through the technical state of the device in detail in can you still use a Basis Peak.

What the refund actually looked like

The Basis Peak refund mechanic was unusual and worth recording, because it set a small precedent in wearable-recall practice.

Most consumer electronics recalls (the Galaxy Note 7 being the obvious comparator from the same year) require the customer to return the unit, often in fire-resistant packaging, in exchange for a refund or replacement. Intel did not ask for the Peak back. Owners submitted a claim with proof of purchase (a receipt, an order confirmation, or, for many people, a screenshot of the original Basis web order), and Intel issued the refund directly. The watch itself was the owner’s problem to dispose of.

That choice almost certainly came down to logistics and risk. Shipping 200,000 lithium-ion devices with a documented overheating defect through the postal system was not appealing to anyone. Not Intel, not USPS, not the airlines that carry their priority mail. Telling owners to dispose of the device locally, while paying full refund, sidestepped the entire return-shipment problem. It also meant that thousands of Peaks stayed in drawers instead of going through a return pipeline, which is part of why support questions about “I just found my old Peak” still come in to this site ten years later.

The refund was full purchase price. The Peak shipped at $199 at launch in November 2014 and had been discounted to about $169 by mid-2016; Intel paid the actual amount on the receipt, not a single fixed figure.

What Intel said, in Intel’s own words

Two phrases from the recall record are worth quoting directly, because they came up again later when other wearable makers had thermal issues.

The first is the hazard description: “the battery in the watch can overheat, posing burn and blister hazards.” This is the language in CPSC notice 16-235 and on Intel’s own Peak refund page from June 2016. It is narrower than “fire risk.” It specifies burns to the skin, not enclosure ignition. That distinction shows up in how Intel handled disposal. Owners were told to dispose of the device, not to treat it as a fire hazard requiring special packaging.

The second is the customer instruction: “stop using the device immediately.” The same notice told owners not to wait for a replacement, not to attempt repairs, and not to return the device to Intel. That phrasing reappeared almost verbatim in later wearable recalls from other manufacturers, which is probably the clearest indicator of how influential the Basis Peak case became internally at the CPSC.

What this teaches about wearable safety today

The Basis Peak recall sits at an awkward intersection: it was big enough to matter, small enough to be forgotten by most of the industry, and specific enough in its failure mode that you can draw real lessons from it. We do, on every modern device we cover.

Sealed cases are a design choice with a safety cost. The Peak’s case had no service hatch. You could not replace the battery. You could not crack it open without destroying it. That is now standard across the wearable category: the Apple Watch, every Fitbit since the Charge 2, the Oura Ring, every Whoop band, the Garmin Vivosmart line. The trade-off is water resistance, slim form factor, and lower cost. The cost on the safety side is that there is no field-level repair path. If the battery becomes unstable, the only options are a recall and disposal.

Firmware-driven thermal management has limits. Intel tried to fix the Peak’s overheating in software twice (November 2015 and March 2016) before concluding that it could not. The lesson modern wearable makers seem to have internalized is that thermal headroom has to be designed into the cell, the enclosure, and the charging stack from the start. Software is a last layer, not a fix-it-later layer. This shows up in modern devices through conservative charging curves: an Apple Watch will refuse to charge above certain temperatures, and a Fitbit Charge 6 throttles fast-charge speed based on enclosure temperature.

Non-replaceable batteries put a hard clock on the device. A lithium cell has a service life. In a watch you cannot open, the watch’s service life is the battery’s service life. The Peak made this concrete: a device that had no manufacturing defect at all in 2014 became, by 2016, a fire-and-burn risk that had to be pulled from the market. Every wearable now sold inherits this clock. We treat any wearable with an unusually thin profile (under 9 mm) and a sealed case as a device with a relatively short safe service window, regardless of what the marketing says.

The acquisition story behind all this is the subject of a longer piece on Intel’s Basis Science acquisition: Intel bought Basis Science in March 2014, reportedly for somewhere between $100M and $150M, and shut the line down 24 months after the launch of its only product. What is relevant to the recall specifically is that Intel had the financial latitude to walk away. A smaller company would have tried to ship a hardware revision, or limped along with a partial recall. Intel did neither. The decision to take a full refund posture without requiring returns is, in retrospect, the most defensible thing the company did with the Peak.

Where the record lives now

The original CPSC notice, 16-235, is still online at the agency’s recalls page, and it is the canonical source for the unit count, the hazard language, and the refund mechanic. The Health Canada notice from the same date is harder to find but archived. Intel’s own refund portal stopped accepting claims sometime in 2017; the page itself has been gone since the broader mybasis.com shutdown, but the Wayback Machine has snapshots from June through December 2016 if you want to see what the refund flow looked like.

If you owned a Peak and got the refund, you are done. If you owned one and never got around to filing, the money is no longer available; the device is still recalled and still unsafe to use. If you are reading this because you bought a “vintage” Peak on a resale site recently (and yes, despite Amazon and eBay’s flagging, listings still slip through), return it. The watch you have is not a working device. It is a 2014-vintage lithium battery in a case you cannot open, and it is one of the 200,000 units in CPSC notice 16-235. The list of things we’d actually buy in 2026 instead is short, and none of them are this watch.