Update - COROS Server Outage
Server outage has been fixed.
This incident has been resolved.
12/26/2020, 15:00 PDT
COROS Server Outage
Server outage is currently affecting data syncing, account login and customized settings on the COROS app. Workout/daily tracking and other watch functions are not affected. Please don't uninstall the COROS app or reset your watch.
This incident is under investigation.
12/26/2020, 14:00 PDT
Update - Elevation/temperature issues affecting COROS PACE 2 watches
V2.34 firmware has been released to all COROS PACE 2 units.
This incident has been resolved.
12/23/2020, 19:30 PDT
Update - Elevation/temperature issues affecting COROS PACE 2 watches
Test firmware pushed to select units. The product team is closely monitoring the outcome of the test firmware.
Expecting to release a new firmware to fix this issue.
12/23/2020, 04:00 PDT
Elevation/temperature issues affecting COROS PACE 2 watches
Certain COROS PACE 2 (firmware V2.32 and V2.33) watches may experience zero or fluctuate elevation gain during outdoor workouts. Elevation and temperature widgets may remain constant for long period of time.
This incident is under investigation.
12/22/2020, 10:00 PDT
Update - GPX/KML/FIT file with no elevation data
Android app version: 2.2.15
iOS app version: 2.2.19
This incident has been resolved.
11/23/2020, 22:30 PDT
GPX/KML/FIT file with no elevation data
Currently we are experiencing bugs causing GPX, KML and FIT files exported from certain COROS Android app (V2.2.9) to not include any elevation data. Strava/TrainingPeaks integration, file export and Save Route features are affected.
iOS users, Android users (prior to V2.2.9) and certain Android users (V2.2.9) are not affected.
Expecting to release a new Android app version to fix this issue early next week.
11/19/2020, 18:30 PDT
Update - A potential integration issue affecting data syncing to Final Surge accounts
This incident has been resolved.
10/29/2020, 19:40 PDT
A potential integration issue affecting data syncing to Final Surge accounts
The workout data syncing from COROS to Final Surge is affected. Manual data upload to Final Surge is recommended before the issue is resolved. Please go to this blog for data export instructions on the COROS app.
This incident is under investigation.
10/29/2020, 10:20 PDT
Update - A potential GPS issue affecting COROS watches
Our team has identified the issue which was caused by inaccurate GPS satellite data. The issue will be fixed automatically on and after 8/22 12:00 AM local time.
This incident has been resolved.
8/21/2020, 19:25 PDT
A potential GPS issue affecting COROS watches
The GPS acquisition time for outdoor workouts may take substantially longer. GPS track may be way off/drifted or missing.
This incident is under investigation.
8/21/2020, 19:00 PDT
Update - A potential GPS issue affecting COROS watches
This incident has been resolved.
5/3/2020, 11:50 PDT
Update - A potential GPS issue affecting COROS watches
Our team has been working hard to try to identify the root cause of the GPS issue. Now we suspect it was due to invalid historical satellite data affecting models from other brands as well. We would like to receive help from our watch users by running a quick test.
- We have just updated the GPS satellite data on our server.
- Please open the COROS app and refresh your device’s GPS satellite data (this step is very important).
- COROS app > Device page > GPS Satellite Data.
- If it shows data is up to date, don’t worry as the app has refreshed your GPS satellite data automatically.
- Go out for a short walk or run (5-10min).
- If the issue remains, please submit a feedback on the COROS app (Profile page > Feedback > Send). Please answer the following question in the feedback to help expedite the investigation.
- Have you updated the GPS satellite data right before the test?
Thank you and we hope to get it solved as soon as possible.
5/1/2020, 10:00 PDT
A potential GPS issue affecting COROS watches
The GPS track for the first few miles may be way off or drifted. The remaining GPS track is unlikely to be affected.
This incident is under investigation.
4/30/2020, 07:30 PDT