Graphical Tracert shows HopOne has a loop
Very interesting. Of course my providors phone is busy right now, so I can't do jack.
In theory, though... shouldn't the non-graphical tracert done the same thing as soon as it hit one of the same machines this route hit?
For example... why does this graphical trace loop back and forth betwwen two hopone IPs while the tracert I posted earlier apparently resolved to the destination IP at a point past this trace?
Or do the different traces mean they're frantically trying to fix it and the routing is being reconfigured as I'm doing these traces?