Garmin and Suunto Firmware Bugs: July 2026 Tracker

Two consecutive weeks of endurance tech bug reports, covering the fortnight ending 24 July 2026, paint a messy picture for Garmin and Suunto users right now. The5kRunner's Fix Files issues 7 and 8 logged a combined 33-plus distinct faults across watches, cycling computers, and training software. If your Fenix 8 is randomly rebooting or your Suunto Race 2 is stuck in an update loop, you are not alone.

Garmin Watch Bugs: Fenix 8, Forerunner 970, Enduro 3

The Fenix 8 AMOLED is the single most troubled device across both issues. Firmware 21.39 triggered crashes, and 22.35 introduced random reboots plus lost step counts, meaning the optical PPG sensor data is recording but the software is dropping it. The Fenix 8 Pro adds two more problems: courses loaded via Explore are arriving silently with no notification, and phantom distance is accumulating while the watch is stationary, which points squarely at a GPS or accelerometer fusion error rather than anything to do with the barometric altimeter. The Enduro 3 shares the music-skip reboot bug with the Fenix 8 Pro, which suggests a common firmware module is the culprit. For context, the Coros Vertix 2S has had a much cleaner firmware run over the same period, and Polar's Grit X2 Pro has not generated comparable crash reports this cycle.

The Forerunner line is not clean either. The Forerunner 970 is showing pace dropping to zero mid-run, a GPS signal parsing issue that is genuinely disruptive for anyone doing interval work where pace is the primary feedback metric. The Forerunner 570 is hitting a boot loop, which is a hard blocker. These join the elevation, sleep, HRV, metronome, touchscreen, and brightness faults already documented in issue 7. We covered earlier Garmin firmware patterns in [our June 2026 bug tracker](/en/articles/garmin-firmware-bugs-in-2026-six-issues-and-confirmed-fixes-2026-06-14), and the volume has clearly accelerated since then.

Garmin Edge Cycling Computers: 540 to 1050

Garmin's Edge range is taking hits across the board. The Edge 850 has two separate faults: a boot loop triggered by loading courses, and GPS signal loss during standby, both of which are serious for any cyclist who pre-loads routes the night before a ride. The Edge 1040 is suffering from slow map refresh, which is less critical but annoying on technical terrain where you need ClimbPro to update quickly before a climb. The Edge 1050 has the longest fault list: Wi-Fi connectivity dropping, sensor reconnection failures, ClimbPro errors, map data field issues, and a TopoActive freeze that locks the unit. A Wahoo Bolt 3 or a Hammerhead Karoo 3 would not have most of these issues right now, though Wahoo has its own software troubles as we noted in [our Garmin and Wahoo bug roundup from June](/en/articles/garmin-and-wahoo-bugs-june-2026-six-issues-tracked-2026-06-18). Issue 7 also flagged Edge 1040, 840, and 540 firmware crashes and reboot loops, plus navigation and gradient calculation bugs that affect ClimbPro accuracy on longer rides.

Suunto Vertical 2, Race 2, and Legacy Devices

Suunto's problems are fewer in total count but some are hard blockers. The Vertical 2 and Race 2 are both stuck in update loops, meaning users cannot progress to the latest firmware at all. That is a significant issue for a premium watch sitting in the 600-700 euro bracket. The Race 2 also appeared in issue 7 alongside the original Suunto Race for map, distance, route, and vibration faults. Firmware 2.56.18 added a readability problem: map labels in light mode are difficult to read in daylight, which is a regression for outdoor navigation use. The Tide widget stuck on "Updating" is a minor annoyance by comparison. Suunto's pace of firmware fixes has historically been slower than Garmin's, so users waiting on resolution should check Suunto's release notes closely before updating. The Suunto Vertical, 9 Baro, and 9 Peak Pro were also in the issue 7 fault list, suggesting this is not purely a new-hardware problem.

What is missing from both issues is any confirmed fix timeline from either brand. The5kRunner documents workarounds, and some of those are solid, but Garmin in particular has not publicly acknowledged several of the Fenix 8 and Edge 1050 faults listed here. Whoop 5.0 and Apple Watch Ultra 3 users are not facing anything comparable in terms of crash frequency right now, partly because those devices run simpler firmware stacks with fewer navigation and GPS features exposed. The [Fenix 8 Pro trail visibility problem](/en/articles/fenix-8-pro-s-trail-visibility-issue-persists-2026-05-14) we flagged in May has still not been fully resolved, which adds to a growing list of outstanding Fenix 8 issues.

The honest verdict: if you are mid-training-block and relying on a Fenix 8 AMOLED, Forerunner 970, or Edge 1050, hold firmware updates unless the release notes specifically address a bug affecting you. For Suunto Race 2 users caught in the update loop, the workaround documented at The5kRunner is currently the best available option. Athletes shopping now would be better served by a Coros Pace 3 or Polar Vantage V3 at the same price tier until Garmin stabilises the 22.x branch. Experienced users who need the Garmin ecosystem features should wait two to three weeks before updating any device in this list.