I’ve had a quick look at the logs and it’s not actually a “glitch” but rather a loss of contact between the flight controller (i.e Pixhawk) and the GPS. The reason I say that is because it instantly and completely loses updates from the GPS. If it was a glitch then we would continue to get updates from the GPS but the position and velocity information would be bad.
This means, that when looking for the cause, we need to either look at some kind of physical problem (like the serial cable connecting the flight controller and GPS is bad).
If you’re using a Ublox, I think it might be a good idea to set the GPS_TYPE to “2”. This ensures tells the code that you’re always using a UBlox so if it does lose contact it should recover more quickly… I think.