Garmin, Suunto, COROS and Wahoo Firmware Bugs: July 2026 Tracker

If you trained with a Garmin, Suunto, COROS, or Wahoo device in June or July 2026, there is a real chance a firmware update quietly broke something. Across three consecutive weekly Fix Files issues from The5kRunner (issues 5, 6, and 7, covering the weeks ending June 26 through July 17), a total of 63 confirmed faults were catalogued across the major platforms. That is not a typo. Sixty-three discrete bugs, across devices ranging from the Forerunner 165 to the Edge 1050, the Suunto Vertical 2 to the COROS Pace 3.

Garmin: The Widest Blast Radius

Garmin took the most hits, which partly reflects how many devices they ship and how many users actively report issues. The Forerunner 970 alone accumulated faults across elevation recording, treadmill distance calculation, HRV readings, metronome behavior, touchscreen responsiveness, and brightness control. Firmware version 17.33 specifically triggered mid-activity reboots on the FR970, which is about the worst time for a watch to crash. Garmin's Fenix 8 fared little better: pace freezing at 0:00 mid-run appeared in issue 6, battery drain hit with version 22.35, and crash reports continued into issue 7. The [Fenix 8 trail visibility issue we tracked earlier this year](/en/articles/fenix-8-pro-s-trail-visibility-issue-persists-2026-05-14) now sits inside a longer pattern of instability for that platform.

The Edge cycling computers were not spared. The Edge 1040, 840, and 540 all showed battery percentage errors on firmware 31.29. Version 31.30 then dropped Strava Live Segments, which is a feature that a significant portion of competitive cyclists rely on for training structure. The Edge 1050 stacked up its own specific issues: Varia RearVue 820 battery misreading, tone volume resetting after power cycles, ClimbPro gradient errors, and mid-ride reboots. For context, the Edge 1050 retails at around 650 euros. These are not budget devices with budget expectations. The Venu 4 added false sleep detection to the pile, meaning Garmin's health and recovery metrics were feeding athletes incorrect data during a period when recovery tracking is supposed to be the watch's strong suit.

Suunto and COROS: Fewer Devices, Still Real Problems

Suunto's issues clustered around two product lines. The Race S and Race 2 both lost pool swim distance in the week ending June 26, which is a fundamental failure for any watch positioning itself as a multisport tool. Pool swim distance is calculated from stroke count and pool length, so this is a software parsing error rather than a sensor fault. The Suunto Vertical 2 showed a black screen fault and battery reporting errors in issue 6, then returned in issue 7 with map loading, distance calculation, route following, and vibration problems. The Suunto 9 Baro and 9 Peak Pro also appeared in issue 7 with their own map and route bugs. Suunto's app version 6.10 added a route library fault on top of all that. Sticky notifications on the Race 2 and power meter dropouts rounded out a rough few weeks for Suunto users.

COROS had perhaps the most alarming single entry in the dataset. The COROS Pace and Apex lines were bricking after the May 2026 firmware update, as reported in issue 5. A bricked device is not a nuisance bug; it is a paperweight. COROS has built a loyal following among budget-conscious triathletes and ultra runners specifically because its firmware has historically been more stable than Garmin's. That reputation takes a hit when a firmware update permanently disables hardware. Issue 7 also flagged COROS Pace 3 dial failures, suggesting the platform's current firmware cycle has been unusually rough. We have been tracking a broader pattern of [Garmin firmware instability through 2026](/en/articles/garmin-firmware-bugs-in-2026-six-issues-and-confirmed-fixes-2026-06-14), but this COROS data suggests the problem is industry-wide right now.

Wahoo: Fewer Bugs, But High-Impact Ones

Wahoo appeared across all three issues, but with a smaller total count. The Kickr v6 dropout issue in Zwift, flagged in issue 5, matters enormously to cyclists using structured indoor training through winter and early season blocks. ANT+ and Bluetooth connectivity dropouts on a smart trainer break ERG mode, corrupt interval data, and make power-based training unreliable. The ELEMNT ROAM average power fault in issue 6 is a different category of problem: average power over a ride or segment is a core metric for cyclists tracking training load, and a miscalculation there flows directly into incorrect TSS figures. Wahoo SYSTM on Windows also appeared in issue 7. That is three separate product lines affected in three consecutive weeks.

What is missing from this picture is resolution timelines. The Fix Files format documents the fault and the best available workaround at time of publication, but confirmed firmware fixes from Garmin, Suunto, COROS, and Wahoo are not always listed with version numbers or release dates. For athletes making buying decisions right now, that uncertainty is frustrating. A Forerunner 970 at 599 euros or a Fenix 8 at 899 euros should not require workaround management. Polar, which did not appear in any of the three issues covered here, and Apple Watch, which similarly stayed off the bug tracker, look comparatively stable right now, though neither targets the same serious endurance athlete use case with the same depth of training features.

The bottom line: if you are currently running any of the affected Garmin Edge or Forerunner firmware versions, check The5kRunner's Fix Files before your next long session. If you are considering a new device purchase, the COROS bricking incident and the Suunto pool swim failure are worth weighing seriously. The Forerunner 970 remains the deepest training watch available for triathletes and runners in 2026, but it is clearly going through a turbulent firmware cycle. Patience, or a temporary rollback to a stable firmware version, is the most practical advice right now.