Garmin Forerunner 27.09 complaints flare up again months later
Fresh complaints are surfacing around Garmin’s 27.09 firmware, nearly three months after the update first began rolling out across the Forerunner lineup. New posts on Reddit and Garmin’s own forums suggest some users are still dealing with unreliable heart rate and elevation data, bringing the issue back into focus.
The 27.09 story is back again
Back in January, reports first emerged that firmware version 27.09 was causing problems on several Forerunner models. At the time, complaints centred on step tracking, sleep detection, heart rate accuracy and general instability, with the Forerunner 165 appearing to be one of the models most frequently mentioned.
A fresh Reddit thread posted this week shows the frustration has not gone away. The user behind the post says their Forerunner continues to produce erratic heart rate readings and inaccurate elevation data. In one example, a completely flat route allegedly appeared as if it involved major climbing, which in turn affects training load, VO2 Max and recovery estimates that depend on that data.
That is what makes this more than a minor software annoyance. When core sensors are not behaving as expected, every metric built on top of them becomes harder to trust.
The frustration has shifted
What seems to be driving the latest backlash is not simply the existence of bugs, but the sense among some users that Garmin has not clearly communicated what is happening.
The latest discussion points to the fact that the Forerunner 165 later received a follow-up firmware update, while owners of other models such as the 255, 265, 955 and 965 feel they are still waiting for a comparable fix. That contrast is clearly adding to the frustration, particularly among owners of higher-end devices.
It creates an awkward perception issue for Garmin. When users of watches are still reporting heart rate and elevation inconsistencies months after rollout, questions naturally start to be asked about the update process and whether the issue has been fully identified.
Not everyone seems affected
At the same time, this does not appear to be a universal problem.
Even in the latest discussions, some users report that their watches are running 27.09 without any obvious issues. That mixed feedback suggests this may be one of those difficult firmware bugs that only appears under certain conditions, perhaps linked to individual hardware units, sensor calibration states or specific use cases.
That inconsistency is partly why the story remains newsworthy. Some runners are seeing no problems at all, while others say the update has had a noticeable impact on key metrics they rely on every day. It also makes the issue harder for Garmin to pin down, which may help explain why some users are still waiting for a clear resolution.
Subscribe to our monthly newsletter! Check out our YouTube channel.
And of course, you can follow Gadgets & Wearables on Google News and add us as a preferred source to get our expert news, reviews, and opinion in your feeds.
