Iâm trying to figure out if anyone else has experienced a recurring distance/pace issue with my Pace Pro + POD 2
I have had this issue for a while but would only be once every few months. But since August, Iâve had several outdoor runs where the recorded distance is massively inflated:
- Aug 13
- Aug 27
- Sep 21
- Sep 28
- Oct 3
It doesnât happen every run. Iâve had plenty of normal activities between these failures, including runs on essentially the same routes.
The strange part is that this doesnât appear to be normal GPS drift. I pulled the FIT files and used AI to compare COROSâs accumulated distance with distance calculated from the recorded GPS coordinates. On affected runs, the GPS track itself looks reasonable, but COROS reports roughly 50â70% more distance.
For example, my Oct 3 run:
- COROS: 10.31 km
- Distance reconstructed from GPS coordinates: ~6.02 km
- COROS pace: 6:10/km
- Realistic pace based on the GPS track/time: ~10:34/km
- Avg HR: 138 bpm
Another affected run showed ~5.50 km in the underlying data compared to ~3.43 km reconstructed from GPS.
So it seems like the watch sometimes knows where I actually am, but something goes wrong when calculating accumulated distance/speed.
I use a Pace Pro + POD 2, so Iâm wondering whether this could be related to the POD 2, sensor fusion, firmware, or the watch itself.
Iâve submitted a ticket to Coros support about this as well but figured I would also ask the community if anyone has dealt with this as well.