If a PingProbe within a Traceroute gives a Timeout event the measurement stores random IPs for the hop because the PingProbe-struct itself is not initialized and filled with random memory garbage. This leads to the following database entries:
Hop 2, 7 and 10 had timeouts, but we see IPs for these hops (0.0.0.0 or "" would be better). The IPs are most likely not on the path, except we route through the United States Postal Service ;)
If a PingProbe within a Traceroute gives a Timeout event the measurement stores random IPs for the hop because the PingProbe-struct itself is not initialized and filled with random memory garbage. This leads to the following database entries:
"834044";"10.0.0.1";1;580;726;667.333333333333;62.9567752950825;3;67100 "834045";"56.43.162.179";2;0;0;0;0;0;67100 "834046";"88.134.222.86";3;8697;14462;12445.6666666667;2653.24208385808;3;67100 "834047";"88.134.193.202";4;15242;17721;16299.6666666667;1044.20634401871;3;67100 "834048";"88.134.193.207";5;17382;18936;17975.6666666667;685.352626187534;3;67100 "834049";"88.134.193.208";6;11956;16018;13411.3333333333;1847.36521084008;3;67100 "834050";"16.171.164.179";7;0;0;0;0;0;67100 "834051";"88.134.202.112";8;14558;15552;15138.3333333333;422.565445292824;3;67100 "834052";"209.85.142.17";9;15560;17366;16565;751.274916392129;3;67100 "834053";"56.43.162.179";10;0;0;0;0;0;67100 "834054";"66.249.94.86";11;13634;27519;18735;6238.14464938628;3;67100 "834055";"72.14.236.223";12;20370;24813;22321;1853.74809507657;3;67100 "834056";"64.233.175.30";13;20389;27292;23612.6666666667;2836.49740975652;3;67100 "834057";"173.194.112.145";14;21743;27519;24883.3333333333;2384.89137884495;3;67100
Hop 2, 7 and 10 had timeouts, but we see IPs for these hops (0.0.0.0 or "" would be better). The IPs are most likely not on the path, except we route through the United States Postal Service ;)