Distance/Time correct but Map missing a portion of the track?

[staceymk11]

I've only had my FitBit Blaze for a couple of weeks and so far have had no problems at all... but today I took a hike and connected my blaze to my phone's GPS before I started, all seemed just fine. But looking at it on the app and on the website, I see that the map is weird. It's missing data (following the map, elevation, etc) for the first two miles and yet my time/distance/pace/heartrate all recorded. 

You can see what I mean in the image: 

And here's a zoom in that shows what it should have tracked. 

Has this happened to anyone else? Missing portions of a track instead of having extra lines, zig zags, etc (which seems to be more typical!)?

I've read that a lot of the accuracy of GPS has to do with your phone rather than with the FitBit.. okay... so what can I do to try to prevent this from happening again? Any advice or suggestions? 

The FitBit connected with no problems, the app was open, my GPS settings all appear to be what they should be (according to previous posts along these lines), the phone was in a pocket at my waist and I have not had any problems with it tracking accurately using RunKeeper in the past. 

Any suggestions are appreciated. 

[John917]

The only  thing I can think of is that GPS signals are not perfect and for whatever reason (storms, structures in the way, mountains, etc you may have lost the signal. If it is a one time event, then it was one of those flukes, particularly since most of the run was recorded. You might see if the problem repeats itself in the same location. If the problem continues, poarticularly if it is in an area where the signal would not be hindered by buildings or perhaps other extraneous signals, then someone with more knowledge of GPS than I is going to have to help you.