My first attempt seemed to not complete (i was feeding it into a text file, so i couldn't watch it)
Tracing route to sprinter-source.com [64.71.133.115]
1 6 ms 2 ms 1 ms 192.168.0.1
2 4 ms 3 ms 5 ms XXXgw66.tukw.qwest.net [63.231.XXX]
3 8 ms 4 ms 4 ms tukw-agw1.inet.qwest.net [71.217.186.9]
4 34 ms 6 ms 4 ms sea-brdr-02.inet.qwest.net [67.14.41.190]
5 6 ms 24 ms 22 ms 10ge2-11.core1.sea1.he.net [72.52.83.9]
6 22 ms 21 ms 22 ms 100ge11-1.core1.sjc2.he.net [184.105.223.217]
The next two (one on screen, then another file capture) did complete, but there was a noticeable pause after lines 6 and 7:
Tracing route to sprinter-source.com [64.71.133.115]
1 14 ms 2 ms 2 ms 192.168.0.1
2 4 ms 3 ms 4 ms XXXXgw66.tukw.qwest.net [63.231.XXX]
3 4 ms 6 ms 5 ms tukw-agw1.inet.qwest.net [71.217.186.9]
4 4 ms 4 ms 11 ms sea-brdr-02.inet.qwest.net [67.14.41.190]
5 17 ms 32 ms 33 ms 10ge2-11.core1.sea1.he.net [72.52.83.9]
6 29 ms 32 ms 22 ms 100ge11-1.core1.sjc2.he.net [184.105.223.217]
7 28 ms 26 ms 23 ms 10ge1-1.core1.fmt1.he.net [72.52.92.109]
8 23 ms 23 ms 29 ms sprinter-source.com [64.71.133.115]
Tracing route to sprinter-source.com [64.71.133.115]
1 2 ms 1 ms 1 ms 192.168.0.1
2 5 ms 6 ms 4 ms XXXXgw66.tukw.qwest.net [63.231.XXX]
3 4 ms 4 ms 4 ms tukw-agw1.inet.qwest.net [71.217.186.9]
4 8 ms 4 ms 4 ms sea-brdr-02.inet.qwest.net [67.14.41.190]
5 16 ms 23 ms 24 ms 10ge2-11.core1.sea1.he.net [72.52.83.9]
6 23 ms 31 ms 23 ms 100ge11-1.core1.sjc2.he.net [184.105.223.217]
7 33 ms 23 ms 29 ms 10ge1-1.core1.fmt1.he.net [72.52.92.109]
8 23 ms 24 ms 27 ms sprinter-source.com [64.71.133.115]
... and the command in Windows is "tracert sprinter-source.com"
(tests run at 3pm PST Jan 9th)
By the 3rd (and a 4th) test, there was no delay after 6&7
A ping test got 40 millisec for the first probe, 22 ms thereafter.
--dick