Tracert

Interesting, being on Riverside's earth station, traffic was sent to Denver, but apparently now, Viasat is allowing outside access for a DOS command like tracert. I've been using Google's DNS server, which years ago, was not possible. This trace goes to Germany...via Palo-Alto, San-Jose, New-York, etc... IP address (63.146.26.154: qwest) may be out of Los Angeles, according to one site. C:\>tracert 78.46.223.24 Tracing route to static.78-46-223-24.clients.your-server.de [78.46.223.24]over a maximum of 30 hops: 1 <1 ms <1 ms 1 ms router.asus.com [192.168.1.1] 2 635 ms 640 ms 647 ms 10.71.12.xx 3 631 ms 640 ms 639 ms 10.71.10.xx 4 658 ms 638 ms 638 ms 63.148.172.73 5 676 ms 670 ms 637 ms 63.148.172.73 6 * * * Request timed out. 7 632 ms 640 ms 641 ms 63.146.26.154 8 813 ms 795 ms 800 ms if-ae-6-2.tcore1.PDI-Palo-Alto.as6453.net [66.198.127.69] 9 789 ms 809 ms 791 ms if-ae-2-2.tcore2.PDI-Palo-Alto.as6453.net [66.198.127.2] 10 810 ms 799 ms 798 ms if-ae-5-2.tcore2.SQN-San-Jose.as6453.net [64.86.21.1] 11 813 ms 802 ms 797 ms if-ae-1-2.tcore1.SQN-San-Jose.as6453.net [63.243.205.1] 12 842 ms 799 ms 801 ms if-ae-0-2.tcore1.NTO-New-York.as6453.net [63.243.128.30] 13 814 ms 799 ms 799 ms if-ae-7-2.tcore1.N0V-New-York.as6453.net [63.243.128.26] 14 780 ms 799 ms 797 ms if-ae-2-2.tcore2.N0V-New-York.as6453.net [216.6.90.22] 15 782 ms * * if-ae-4-2.tcore2.L78-London.as6453.net [80.231.131.157] 16 810 ms 798 ms 799 ms if-ae-14-2.tcore2.AV2-Amsterdam.as6453.net [80.231.131.161] 17 809 ms 798 ms 799 ms if-ae-2-2.tcore1.AV2-Amsterdam.as6453.net [195.219.194.5] 18 814 ms 799 ms 799 ms if-ae-6-2.tcore1.FNM-Frankfurt.as6453.net [195.219.194.150] 19 810 ms 800 ms 799 ms if-ae-7-2.tcore1.FR0-Frankfurt.as6453.net [195.219.50.1] 20 784 ms 799 ms 799 ms 195.219.219.10 21 825 ms 786 ms 799 ms core22.fsn1.hetzner.com [213.239.245.17] 22 805 ms 789 ms 798 ms ex9k1.dc4.fsn1.hetzner.com [213.239.229.150] 23 822 ms 788 ms 798 ms static.78-46-223-24.clients.your-server.de [78.46.223.24] Trace complete.