Owners of first generation Wahoo cycling computers have reported significant issues with their devices since the weekend, the tech company apologising and saying it is working to fix the problem.
Online forums have been full of cyclists reporting data and ride recording issues with their first generation Wahoo Elemnt, Bolt and Roam computers since the weekend, some seeing the wrong date of activities, others missing parts of their ride or not able to record at all.

On Monday, Wahoo first acknowledged the problem and has since provided an update stating it “now fully understands the root cause of the issue” and is “working around the clock on a fix so that users of these devices can continue enjoying riding with them again”.
There’s a certain irony in Wahoo saying it is “working around the clock”, considering the issue appears to be that devices are resetting to the year 2006 because the older devices use a “limited 10-bit system to track GPS time”.
As one reply on a Wahoo forum speculated, “GPS time is counted in ‘weeks’ starting from January 1980, but the counter is only 10 bits long, so it rolls over every 1024 weeks (~19.7 years). If a device’s firmware doesn’t handle that correctly, it can suddenly ‘think’ it’s back in 2006 (1024 weeks before today). Because the device thinks it’s 1st Jan 2006 it’s struggling to lock on to the GPS satellites.”
That would certainly explain why some users’ rides were dated 1 January 2006, others reporting being unable to use their computers at all or missing sections of their rides.

One Norfolk based user said their Roam V1 “went into complete meltdown” and kept losing satellite lock. “[It] told me the time was an hour earlier than it actually was and ended up showing 1st Jan 2006 on the finished ride,” the rider reported.
Another UK-based user replied: “I also ran into issues today with my Wahoo Elemnt Bolt v1 (bought in 2020). Same observations: date of my activity was set to 01/01/2006, current time was one [hour] earlier than it actually was, GPS tracker failing to register traces, so no registration of the actual trace, speed and gradient. Location was Belgium.
“I reinstalled the app on my smartphone completely. I did a factory reset of the device but nothing helped. I also think it’s something related to the latest device version. Fingers crossed it gets solved with the next system update.”
Other owners of the brand’s first generation computers reported dodgy GPS data, such as rides in England being tracked to Ireland, Scotland and other far away locations, as well as the aforementioned date and time inaccuracies. In some cases, users said their devices had become completely unusable.

Another British-based rider said: “Everyone had issues yesterday. My ride told me one section was 90 miles from where I was, and the other side of the English Channel, and my max speed was 197km/h! I didn’t know my sprint was that powerful.”
In a statement issued last night, a Wahoo spokesperson responded to the reports and suggested it “now fully understands the root cause of the issue”:
We deeply apologise to our valued customers for the inconvenience experienced over the past few days with the first generation Elemnt, Bolt, and Roam bike computers. We now fully understand the root cause of the issue relating to older first generation devices, which use a limited 10-bit system to track GPS time. We have been working around the clock on a fix so that users of these devices can continue enjoying riding with them again.
Given the age of these devices and the several upgrades to our product platform since, we are testing the firmware update to ensure it runs smoothly and hope to release it to users soon.
Thank you for your patience and understanding so far. Customers should keep an eye on this web page, which will be updated regularly.
The problem appears to have been widespread, affecting hundreds, if not thousands, of Wahoo’s customers. While there doesn’t appear to be much that can be done other than hope the promised fix is coming soon, one affected rider did share a way they managed to get their dodgy activity uploaded to Strava (if you can’t live without the kudos).
“Find some way to download the fit file (find your activity from Strava, or download directly from the device, or whatever). I plugged the Wahoo into my computer, it showed up as a drive and I went to the ‘exports’ folder. Then I found the file named ‘2006-01-01’.

“Delete the activity with the incorrect 1/1/2006 date from Strava. This is important — otherwise step 3 will get flagged as ‘duplicate’. Use fitfiletools.com to change the date, then I re-uploaded back to Strava.”
Have any of you experienced issues with your first generation Wahoo devices this week? Let us know in the comments and we’ll be sure to keep you updated with any news from Wahoo as soon as we have it.























26 thoughts on “Wahoo scrambles to fix significant “data and ride recording issues” after first generation Elemnt, Bolt, and Roam bike computers reset to 2006”
Both my wife and I use 1st
Both my wife and I use 1st gen Wahoos and both had issues during a charity ride on Sunday. Luckily we both knew our routes because the Wahoos were unusable. At one point mine had me doing 132mph. I defy even Pogacar to match that!
Pah – amateur! I had one of
Pah – amateur! I had one of those roadside matrix signs clock me at 188mph the other day.
I maxed out at 115mph on a
I maxed out at 115mph on a country lane on Sunday. I took a photo of my Wahoo just in case nobody believed that I could go that fast on a bike.
Reggie Perrin wrote:
A photo? Pah! It has to be on Strava or it didn’t happen…
Jogle wrote:
I maxed out at 115mph on a country lane on Sunday. I took a photo of my Wahoo just in case nobody believed that I could go that fast on a bike.
— Jogle A photo? Pah! It has to be on Strava or it didn’t happen…— Reggie Perrin
It is on Strava, but you have to scroll back 19 years to find it …
If I were a Wahoo user I
If I were a Wahoo user I would be encouraged by the company getting on with a fix fairly quickly. I still enjoy being at a stage where I’m amazed these wonderful devices work at all- I’ve just bought a 2 generations obsolete Garmin Forerunner 255 and it’s much better than I expected – the much disparaged ‘breadcrumb navigation’ works perfectly both on the road and on the fells once you have a route loaded, although it’s useless if you don’t as there are no ‘features’ on the map. However, I expect that one day this watch and the Edge 1040 will fail catastrophically, although I hope not at the same time. I am fairly confident that Garmin will then fix the problem rapidly.
well its nice of them to fix
well its nice of them to fix it of course, some might say thats the bare minimum they could do to support the own eco system and not wreck their reputation, but this sounds from the speculation to be a Y2K style bug, they didnt allocate enough memory to support an internal date counter.
which seems remarkable for stuff thats not even a decade old in lifespan yet, given we learnt those lessons three decades ago.
so no doubt it all bricks itself again in 2038.
stonojnr wrote:
If you’re still using your 1st gen Elemnt in 2038, I will be more than impressed.
it wont be the 1st gen stuff
it wont be the 1st gen stuff that breaks, that will be in landfill by then, the issue is youve got people coding stuff right now, that seem to have forgotten important lessons we learnt in software development in the 90s, and are making the same mistakes over and over again
Even though you goto any software developer conference there will be a TED talk style presentation on all the infamous goofs made with software and dates, Wahoo just got added to that list.
and thats what youll hit in 2038 because its exactly the attitude its been approached with, we’ll have replaced the hardware by then, it wont be our problem.
btw next time your on a Boeing 777, cross your fingers that theyve hit the power cycle button recently, because they made the same mistake on their internal clock software, and when it resets it, it switches the whole plane off, even when youre flying it.
stonojnr wrote:
i wonder if the Post Office Horizon systems still use unixware.
It’s the edge case everyone
It’s the edge case everyone ignores
stonojnr wrote:
I thought edge was the other lot?
You probably saw this
You probably saw this satirical history lesson on how the software industry seems to continually rediscover the same things … https://m.youtube.com/watch?v=8pTEmbeENF4&pp=0gcJCRsBo7VqN5tD
stonojnr wrote:
The 10-bit limit was part of the original GPS protocol, set sometime in the 80s, with the first Y2K-style rollover happening in 1999.
The last rollover was in 2019, so i guess somewhere in the software stack there’s a clause saying “every week before #332(ish) is 2019+, otherwise it’s 2006+”. The bug is not necessarily Wahoo’s (though maybe they could have been more on-the-ball). It could be in Android 7 (that it runs on afaik), or the firmware that came with the GPS unit they use.
So how have other GPS systems
So how have other GPS systems managed to avoid this issue ?
The point isn’t necessarily to allocate unlimited memory, its how you handle the rollover.
Not everyone did. And it
Not everyone did. And it looks like quite a few phone manufacturers were pushing out last minute updates before the problem hit. The rollover was in 2019, so Wahoo were caught out 6 years later.
My point was not that Wahoo didn’t make an error (they had a 6-year heads-up), but that it’s not just a case of Wahoo not allocating enough memory. The 10-bit limit came from the GPS protocol released in the 80s. It was a pre-Y2K, Y2K-style bug.
The rollover handling that just pushed the problem 6 years down the line wasn’t necessarily in code that Wahoo wrote themselves. It could have come from a supplier who said the 2019 rollover had “been handled”. But ultimately it’s their product, so it’s their job to make sure it works.
If I were a Wahoo user I
If I were a Wahoo user I would be encouraged by the company getting on with a fix fairly quickly
It appears I was rather under-critical!
Presumably related to this,
Presumably related to this, for the last few days, if I start at a location other than my home, any rides get recorded as ‘indoor cycling’
More annoyingly instead of showing my usual ‘pages’ I get a completely different set.
I have two Wahoo First
I have two Wahoo First Generation Elements. I loaded a 200km ride on one device and lent it to someone else to use on a camping trip in West Wales. It failed to work at all. He had to resort to strapping his phone to the handlebars and doing short sections on Google maps.
I tried to use the other device myself but it froze on the track and was unusable. I tried a factory reset and repairing it with my phone but it made no difference.
I have a Elemnt Roam bought
I have a Elemnt Roam bought in late 2021. It looks like mine isn’t suffering quite so badly as others, as the main problem is the speed on the display keeps going blank, along with a rather drunken looking route for any recorded rides.
I decided that due to the
I decided that due to the poor handling of an issue they should have seen coming, if it is not resolved, I will not go back to Wahoo and will look at alternative brands such as Garmin or may even go further left field!!
John Chisholm wrote:
Because Garmins never have issues. Oh.
Yep, just spent an hour
Yep, just spent an hour trying to get my Garmin Edge Remote to reliably connect with my Garmin 530.
Seem to have solved the problem of intermittent sensor dropouts by turning off Wifi on the 530 (shouldn’t need it as it’ll sync via Bluetooth to my phone anyway).Still flakey. I might have to resort to the “beta” firmware update. 😕
Firmware update has been
Firmware update has been released. Just updated now, fingers crossed good to go for a ride in morning..
Firmware update has been
Firmware update has been released. Just updated now, fingers crossed good to go for a ride in morning..
I have an ELEMNT v1 and did a
I have an ELEMNT v1 and did a 97-mile gravel ride last weekend and a group ride the Thursday before. Both rides seemed to disappear after ending them until I noticed two rides that were completed in January 2006(!). After reading about the firmware issue, I exported the files from the device with OpenMTP and changed the dates with FIT file tools and uploaded them to Strava. The GPS info for both seems to be correct.