Crash reports collection Q1 2026

[jjorgemoura]

Had a crash during my run today, using a Race 2. It crashed at just after 2Km into the run.
I had 3 S+ apps enabled (Cadence coach, ZoneSense and Running Economy) and was using a Polar H10 belt. Everything else were standard (no nav, battery on performance, feeling on, no music controls, etc).

When I realise the watch had crashed and restarted, I’ve started a new activity to continue my run. However, this time I unselected the ZoneSense app, while keeping the other 2 S+ apps and the HR belt. The remaining 10.4Km went well, no problems.

Hope this gets sorted soon by the team.

[orzechszek]

@jjorgemoura try to disable ZoneSense from your S+ apps. It seems it helps me with my Race S.

[runyx17]

I’m still experiencing random restarts on my Vertical 2. Yesterday, it happened three times in a single day. Fortunately, not during an activity. I have the latest firmware installed.
Question: Should I keep sending the logs, or is the cause of the problem already known?

[Speed Man]

Hi Suunto Team,

I encountered my first unexpected watch shutdown after updating to software version 2.56.18.

It happened during today’s run at 6.41 km while I was using SuuntoPlus Fused Zone together with a Suunto Heart Rate Belt.

Has anyone else experienced this issue? Is there a recommended fix or troubleshooting step? I’d really like to avoid this happening during an upcoming race.

Thanks in advance for your help

[elbee]

@runyx17 said:

I’m still experiencing random restarts on my Vertical 2. Yesterday, it happened three times in a single day. Fortunately, not during an activity. I have the latest firmware installed.
Question: Should I keep sending the logs, or is the cause of the problem already known?

Yes, keep sending logs unit suunto confirms they know the cause.
And send an email to support@suunto.com from the same email address as is configured in your suunto profile. That way they connect the logreport with your bugreport in email.

[stromdiddily]

First crash for me today, Suunto Vertical 2. I know it was a crash because it showed up in the Suunto App with 0 ascent/descent…should have had close to 2k feet of each at the point of the crash.

Custom trail running, no suunto guides/apps, no route loaded.
Coros HRM

Logs sent 1:35PM CST (crash was a few hours earlier but long run today).

[stromdiddily]

Back to back days with reboots in the middle of an activity. Logs sent at 930ish CST.

Custom run mode
No suunto apps or guides
Coros HRM

I had just received notification of a phone call on my watch and had accepted the call with my Wings headphones FWIW. Looked down in the middle of the call and had the “Suunto” logo staring up at me from my watch.

REALLY hope there’s something coming to address this. Back to back days on long runs 5 weeks out from Wasatch 100 miler. Not instilling a lot of confidence.

[safari]

Lately, these kinds of freezes have become more frequent. The watch freezes when I’m setting up exercise routines using the Suunto Plus options. It won’t turn on without a 12-second reset.

video
https://streamable.com/jnprg5

[runyx17]

Among other things, my watch Vertical 2 keeps restarting in the shower, even when the screen is locked.

I think this started happening after the latest firmware update. Before that, I always took a shower with the watch after working out at the gym and never noticed any restarts. Now it happens every single time.

I tested this at home to confirm.
https://streamable.com/o2d0i3

[elbee]

If (and so far that is a big IF) a new firmware release will be available for my race is I will be very hesitant to install it, reading all those crash reports after the new race 2/vertical 2 firmware. The bluetooth connection lost to heart rate sensors isn’t fixed anyway, so I might as well stay on the current firmware.