Hello @Jana_S 

Thanks for posting about this and apologies for any confusion.  I'm not aware of any recent changes with this, so I'm going to escalate this ticket to our Support Team so someone can take a look at your activities and troubleshoot with you.

This post has been escalated to our Support team. If you have a similar question please submit a support ticket and we will investigate further.

Just in case anyone else experiences this - Support replied and indeed it’s a bug, hopefully will be fixed soon:

This is a known issue specifically related to newer Apple Watch devices. Basically, we had them added into our device database but there was a separate database they needed to be added to which allows proper parsing of activity data in the FIT files Apple sends us. 
 
We hope to have this resolved as soon as possible.

Hi @Jane11 

I think it's related. I did 6 splits of 1km each and Strava shows them at a much faster pace than it was. I use an Apple Watch Ultra 1 (WatchOS: 10.0)

https://www.strava.com/activities/10257219674

Hi, a notification popped up on me that someone commented on my post - @rkleine, I think the issue you described is yet something else. The original bug I reported is already fixed, I’m not experiencing the problem anymore. But indeed what’s displayed on your run looks odd - the avg pace shown on the Strava record is 3:51/km (which seems to be correct - matches the Watch splits), but all the splits are well above that average… perhaps submit a support ticket..?

Hi @Jana_S Yep, the average pace is correct as you say. The bug apparently is only in the individual splits. Thank you very much for answering. I will submit a support ticket 🙌

Experiencing the same issue. Since Strava doesn't support the Apple Watch Ultra...I, too, am recording my runs with the native Apple Watch Workout app and importing from Apple Health to Strava via the iOS Strava app.

I create the support ticket #2801879:
-----------------------------------------------
I did 6 splits of 1km each and Strava shows them at a much faster pace than it was. I use an Apple Watch Ultra 1 (WatchOS: 10.0)

This happens when I record the workout on the Apple Watch Ultra using the Fitness App and in some of the segments I pause the workout and resume it a few seconds/minutes later. At the end of the workout it is synchronized with Strava and the segment that had a pause is the one that does not have the correct pace
Steps to reproduce the issue:

1. Start running workout on Fitness App
2. At kilometer 1.4, pause the training
3. Wait 2 minutes
4. Resume workout
5. Stop workout at kilometer 3
6. Sync training with Strava

The kilometer where the pause was is where Strava shows the pace poorly, it is always a stronger pace than the real one.

Furthermore this makes most PRs wrong, and some PRs are unrealistic. Also notice that the same thing happens to other users and that they have unrealistic PRs too

Still experiencing the same issue with my Apple Watch Ultra. When I pause during a run and then continue the workout all the pace data gets messed up in strava. No problem with Apple’s native fitness app but in strava I’ve got oddly low pace averages like 1”. It seems like the severity of deviation depends on how long you pause but still very annoying. All my PRs messed up, I see strange pace values like 4s . My 2 other friends also have Apple Watch Ultras and they also experience the same issue constantly. How’s that still not solved after a year !?

Emrah

Hi, this sounds like a different issue, not what I’ve originally reported in this thread. If you pause AW, walk around, and then continue, indeed Strava has problems processing the pause which actually included some moving (it's usually not a problem if you stay at the same spot during the pause).

You should be able to fix the activity using the “correct distance” option - note, it's only on the Strava website, not in the app:

Hi Jana,

Thanks a lot for your message.

I tried the suggestions you provided. While correcting the distance made the results slightly more reasonable in a few cases, it also affected the total distance and overall pace — and in most situations, it didn’t resolve the auto split pace issue.

Actually, I believe my issue is exactly the same as the last post shared by the user ‘rkleine’ about a year ago.

Here’s my fairly typical running scenario:

• I start a run using the native Fitness app on my Apple Watch Ultra.

• I run ~3 km.

• I pause the activity on the watch.

• I wait or walk for a few minutes.

• Then I resume and run another 2–3 km.

• I repeat this pause/resume cycle a couple of times before stopping the activity.

Everything looks perfectly fine in the Apple Fitness app — total distance, duration, and pace are all accurate.

When the data syncs to Strava, the overall distance and pace still match those in the Fitness app, so no issue there.

However, the 1 km auto split paces— in this example for the 3rd and 4th kilometers (where pauses/resumes occur) — are completely off. In some cases, the pace is reported as unrealistically fast, like under 1’00”/km. I don’t think moving or waiting on the same spot (which is rarely the case) make any significant difference.

Since the total metrics are accurate and only the split paces are skewed, it seems the problem lies in how Strava processes pause/resume within the splits.

Thanks again for looking into this. Let me know if there’s any other info I can provide.

Best,

Emrah

Hi ​@egokmen, no offence but the fact that the other user “hijacked” this old (and already resolved) topic with an unrelated issue isn't really a good reason to do the same  

Would you please create a new separate post (i.e. not a response) with all these details. Someone will hopefully be able to help. I don't know the answer and your question would remain buried at this old topic, likely unnoticed (I have seen it because I got a notification that someone replied to my old thread). Thanks.

Hi ​@Jana_S,

I noticed that after reading the previous posts and have already created a new thread:)

Thanks again.

PS: In case someone reads this, here is the link to the new topic.