1 1 ms 1 ms <1 ms homeportal [192.168.100.254] 2 * 1137 ms 1117 ms wnpgmb0614w-ds01-0-2.dynamic.mtsallstream.net [220.127.116.11] 3 23 ms 22 ms 22 ms 10.7.0.9 4 21 ms 21 ms 21 ms be6294.cipc2-wpg.bb.allstream.net [18.104.22.168]
It is possible that you may see private address' when you perform a tracert. It is dependent on the route your trace takes. The majority of traces you run will have the same initial 4 or 5 hops regardless of where the destination is as these are hops on MTS's network. This being said they will sometimes change depending on the status or other occurrences on the network such as congestion or technical difficulties. Without knowing for sure, seeing the latency on that 2nd hop of over 1100 ms I would guess the IP or server you hit on that hop may be experiencing some high traffic or possibly even difficulties so that IP may change at one point to alleviate some load to it. David also makes a good point that many IP's are now becoming "private" from a server side due to the sheer number of devices out there now a days that require an IP address they are just running out and we need to ensure IP's are reserved for our backbone networking devices.