Crash reports collection Q1 2026

Dimitrios Kanellopoulos

Hi there,

I see the concern that your V2 R1/R2 watches are crashes with the latest FW released.
Some people report its due to guides others have different report.

My task is to collected more detailed logs here so please:

After the crash (as soon as possible but dont stress about it) :

Open the app -> settings -> Send logs to Suunto

After that send me a private message with your email or account name used for the Suunto app. Do not share your email here in the forums as a post please. Use the chat function under my profile.

Thank you

runyx17

@Dimitrios-Kanellopoulos Thanks for that. I appreciate that you’re looking into it. Over the weekend, my V2 restarted twice, not in activity.

babychai

Actually few weeks ago happen to my SV 1 as well during hiking but did not manage to send logs.

sky-runner

@Dimitrios-Kanellopoulos I wanted to mention that I had one crash a a few weeks ago, for which I had uploaded the logs, and the crash was then reported into the system with help of @Egika . In my case it was a vanilla Run sport with nothing special about it and me not doing anything with the watch at the time of the crash. The only special thing was, perhaps, is that I used the Run sport for the first time on the watch, but previously I did a number of activities with a customized Trail Run sport.

If that helps, I can send you the details (crash time, etc) again in the chat.

PhilBee

@Dimitrios-Kanellopoulos have just uploaded logs, but the run in question was 2 runs ago. Vertical 2. customised run mode. run randomly ended early, but saved the run. result in app was missing distance & gps trace, missing total ascent/descent, missing pace zone info. gps trace up to that point was ok, including altitude data. custom run mode had: navigation off, battery on performance, touch on, S+ zonesense on, S+ HR zone duration on, S+ last km on, wrist HR on but HR strap (Coospo) connected

Adrian.S

I have reported too, logs are sent: https://forum.suunto.com/topic/15254/combining-2-workouts-into-1-my-suunto-froze-up-today-during-a-59-km-ultra-run

EzioAuditore

@Dimitrios-Kanellopoulos Another crash today at 11:45 CET. Logs sent at 11:52 CET. Watch used Vertical 2. I’ll send you my mail in PM.
So far with the current FW both my R2 and V2 are crashing every 3,4 runs.

Custom trail run mode
Runna guide selected
Navigation route selected without turn by turn
Burner and ZoneSense Plus apps
External Polar H10
V2 connected to Android (today’s logs sent) while R2 to iOS

Details: Upon receiving of the “thanks for running with runna” notification I was heading towards the end of the route and was waiting for the end notification. The runna notification never disappeared. What I have noticed is that the notifications with this FW are not going away automatically (most of the time but not always) until mid button pressed.

The details of the run in the application are missing: all the Suunto plus data (burner) and the asc/dsc are both 0. Technique part is missing too.

Any news of a hotfix coming or should I downgrade? I’ll be switching to the Ocean for now and the training season, if that doesn’t work back to the Forerunnner.

Thank for your help!

sky-runner

@dimitrios-kanellopoulos,

Vertical 2 crashed today 1h 15m into a long trail run.
I have uploaded the logs with relevant details via the Suunto App feedback feature - they’re is an option to include logs.

This was a second crash on my 90th Anniversary Vertical 2 since I got it. I am definitely concerned considering upcoming UTMB race in 3 months. I hope getting to the bottom of this is a priority for Suunto team.

I used a custom Trail Run mode, with navigation and Climb Guidance, and S+ Guide from Training Peaks, although it was a simple guide that only tracks time to completion. At the time of the crash I was most likely either on the map screen or on the climb guidance screen.

Also, external Coros armband HR sensor was connected, but I run with this sensor almost all the time.

The crash was around 14:00 Pacific Time, logs uploaded shortly after 16:00 Pacific Time.

sky-runner

I wonder if the crash I mentioned in the previous post could have been caused by me unintentionally rebooting the watch by pressing on the start button.

I always felt that on Vertical 2 the start button dangerously sticks out which makes it too easy to press. Honestly, this seems like a bad design. During activity we almost never need to press this button.

At the time of the crash I was using poles and climbing up on steep terrain which means my wrists were bent the way that the button could be pressed. Furthermore I wore half gloves that Leki poles attach to.

I have just done an experiment - started an activity, switched to the map screen, then pressed and held the start button - shortly after the watch has rebooted!

I think this needs to be addressed - either the timeout for the reboot - how long we need to hold the button - should be increased or perhaps there should be another way to prevent this when using poles. But again, I don’t know if that is what has actually caused a reboot but I can see that accidentally rebooting Vertical 2 is quite possible when using poles.

Any thoughts about this? Should I start a separate thread to discuss this?