Crash reports collection Q1 2026

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.

HonzaS

Another spontaneous reboot today, the third since the FW was released. Vertical 2 announced an incoming call and then rebooted. I just sent the logs to Suunto.

stromdiddily

@HonzaS same behavior I saw for my reboots. Immediately following or during a watch notified phone call

stromdiddily

Crash AGAIN after missing a phone call, not once but twice on my run today. Same settings as last time, logs sent to Suunto at 9:20am ish CST @isazi @dimitrios-kanellopoulos

Custom Trail Run
No Guides
Suunto HRM

4 hours in, missed phone call, watch reset (logs sent here)

Started another activity, not 30 minutes in missed another phone call, watch rebooted. Didn’t bother with logs or starting another recording to finish my run.

The vertical 2 is getting shelved for the 100 in two weeks unless by some chance there’s a fix coming for these.

André Faria

@stromdiddily not a solution but rather a workaround/debug, what about not having notifications on the watch?

stromdiddily

@André-Faria normally yes for regular runs and training would work but not for the race w crew and whatnot.

HonzaS

Super Suunto, I have to congratulate you! Now you are completely on par with Garmin, which is why I switched to Suunto. Another restart today, riding my bike home from work. I stopped and pressed stop while the watch was in autopause mode. A restart followed. That wouldn’t be such a horror, but all the sport mode settings were lost and now are in factory defaults! Completely same behaving like Garmin, but with Garmin I had the option to restore the settings…

Just sent logs. @isazi @dimitrios-kanellopoulos

I use only Zone sense from Suunto+

HonzaS

If only we had some kind of feedback that they’re actually working on a fix. I don’t even know if anyone is looking into the logs we’ve submitted.

isazi

@HonzaS logs without a bug report to support are not checked, as far as I know. We try to help by forwarding requests from the forum (that is not a support forum) to the bug tracking system, but bugs in production are more valuable close to release date, as right now the development firmware is tens of releases ahead and bug reports on old firmware is not always useful.

isazi

@stromdiddily let me see what I can do to report this, cannot assure that a fix will come in two weeks, as far as I know unless there is a major problem there are only 3-4 releases per year.

isazi

@stromdiddily I miss the email associated with your Suunto account for the bug report. DM me if you can.

runyx17

I sent several logs and always emailed support@suunto.com as well. I never received a meaningful reply. A simple “we know about this and we are working on a fix” would have been enough.

In the end, I took the watch to a Suunto service center. Today is the 8th day and I still have no update on the resolution.

HonzaS

@isazi Thanks for answer! But I had the restart with settings lost yesterday, so I can’t be faster :-(.

So the right procedure is to send logs and sent email to support@suunto.com? For now it seems, that I have to wait for next release and hope it will be fixed.

isazi

@HonzaS is there a way to reproduce it? Does it always happen with autopause? If you have a good description and send the logs after the event I can create a bug report for you, or you can send the same information to support.

HonzaS

@isazi Unfortunately, it isn’t. It happens randomly. If I were able to reproduce it, I’d get back to you or direct to support email. Thank you for your willingness to help.