Garmin, Suunto, Wahoo Bug Report: Week of 4 September 2026

Twenty-one bugs. One week. If you train with Garmin, Suunto, or Wahoo hardware, the first week of September 2026 was a rough one. From sensors going completely dead to watches crashing mid-race at UTMB, the fix files this week read like a stress test that nobody signed up for.

Garmin: The Longest Bug List

Garmin took the bulk of the hits, with fourteen separate issues logged. The most serious: Fenix 8 sensors dying entirely after software update 22.41. That means no optical PPG heart rate from the wrist, no SpO2 readings, nothing. For athletes relying on the wrist sensor during long training blocks, that update effectively bricked a core feature on a watch that retails above $900. Fenix 8 buttons also locked up on the morning report screen, and alarms were disabling themselves overnight, which is the kind of thing that ruins race-day wake-ups.

The Edge 850 problems deserve their own paragraph. That head unit managed to accumulate five distinct bugs in a single week: map panel refusing to stay in North Up orientation, home screen defaulting to Everyday Rest mode instead of the correct profile, screen flickering black on firmware 32.20, a weather temperature field displaying minus 43C (nobody is cycling in that), and Battery Save Mode disabling itself on the same firmware version. The minus 43C reading is almost certainly a sensor parsing error on the barometric or ambient temp input, not actual measured temperature. The flickering black screen on 32.20 is the kind of regression that suggests the firmware release skipped a display driver validation step.

Two more Garmin issues worth flagging for cyclists specifically. The Edge 1040 was recording incorrect power data from Vector 3 pedals. Vector 3 pedals send power via ANT+ using a standard power meter profile, so this points to either a parsing error in the firmware or a calibration offset being applied incorrectly after an update. Wrong power data corrupts training load calculations, TSS, everything downstream. Separately, the Forerunner 970 pace was flatlining after each lap press, which kills pacing feedback mid-race. Garmin Connect web also refused to open multisport sub-activities, blocking post-race analysis for triathletes at a critical time in the racing season.

Suunto: Five Bugs Including a Race-Week Crash

Suunto logged five issues, and the most damaging one is the Vertical 2 crashing during UTMB. UTMB is a 170km mountain ultra. A GPS watch crashing mid-race is not an inconvenience, it is a safety and tracking failure. Athletes use these devices for navigation and emergency contacts use them for live tracking. The Vertical 2 also recorded zero distance on open water swim sessions, which points to a GPS or accelerometer processing fault specific to that activity mode. Open water swim tracking relies on GPS since wrist-based optical sensors cannot provide distance data from stroke counting alone with acceptable accuracy over long distances.

The Race 2 had two separate problems: display and battery drain issues on software 2.56.18, and sensors dropping out entirely after hotfix 2.56.28. That second one stings because hotfixes are supposed to solve problems, not create new ones. The Race S had Runna training plan sync failing, which disrupts structured training for athletes who use that integration daily. Suunto's software release cadence has been aggressive in 2026, and these bug clusters suggest QA is not keeping pace.

Wahoo Rounds Out a Bad Week

The [Wahoo ELEMNT Bolt V3](/en/articles/wahoo-files-itc-complaint-to-block-jetblack-victory-trainer-imports-2026-05-16) losing all sensor and phone pairing is a significant failure. The Bolt V3 pairs sensors via ANT+ and Bluetooth simultaneously. Losing both at once suggests a firmware-level reset of the pairing database rather than a single protocol failure. For a cyclist mid-training block, rebuilding all sensor pairings (power meter, heart rate strap, radar, Di2) is a 20-minute problem that should never happen from a software update.

What is missing from all three brands this week is any kind of proactive communication. None of these companies pushed alerts to affected users before the issues were crowd-sourced on forums and aggregated by sites like The5kRunner. Garmin has a known beta testing program; it is unclear how firmware 32.20 shipped with this many Edge 850 regressions. Coros and Polar have had quieter bug weeks by comparison, though Polar's update cadence is slower which reduces exposure. Whoop, operating on a different model with no GPS and cloud-dependent recovery scoring, avoided hardware bugs entirely this week but faces its own software reliability questions.

Bottom line: if you are a Fenix 8 user, hold on firmware 22.41 until Garmin pushes a patch. Edge 850 owners on 32.20 should check Garmin's beta forums before any critical rides. Suunto Vertical 2 athletes doing mountainous ultras or open water swims need a backup device right now. The Forerunner 970 pace bug matters most for competitive runners using lap splits in races. None of these issues are acceptable at the price points involved, and all three brands owe their users faster patch turnaround than they are currently delivering.