Connectivity
Connectivity and managing Your Comcast Business network
Male IT Specialist Holds Laptop and Discusses Work with Female Server Technician. They're Standing in Data Center, Rack Server Cabinet is Open.
Highlighted
gstanley79
Contributor

Inefficient routing, 3 miles apart.

It seems there is misconfigured routing topology between my  home business and another comcast business customer (whom is a Fire Department I am employed at). 

 

traceroute to 24.126.13.81 (24.126.13.81), 30 hops max, 60 byte packets
 1  router.asus.com (10.1.1.1)  2.545 ms  2.531 ms  2.522 ms
 2  68.33.199.1 (68.33.199.1)  25.909 ms  25.902 ms  25.895 ms
 3  te-1-1-sr01.inwood.wv.bad.comcast.net (68.87.130.113)  34.413 ms  34.408 ms  34.402 ms
 4  te-8-4-ur01.martinsburg.wv.bad.comcast.net (69.139.175.141)  22.129 ms  22.134 ms  22.124 ms
 5  po-120-ur01.catharpin.va.bad.comcast.net (68.87.128.5)  22.110 ms  22.736 ms  22.730 ms
 6  ae-5-0-ar04.manassascc.va.bad.comcast.net (68.85.67.117)  23.975 ms  17.955 ms  17.944 ms
 7  xe-11-0-0-0-sur01.martinsburg.wv.bad.comcast.net (68.85.67.45)  20.340 ms  19.394 ms  19.381 ms
 8  te-1-0-0-ten01.martinsburg.wv.bad.comcast.net (68.86.252.106)  23.991 ms te-3-0-0-ten01.martinsburg.wv.bad.comcast.net (68.86.252.110)  23.954 ms te-1-0-0-ten01.martinsburg.wv.bad.comcast.net (68.86.252.106)  24.066 ms
 9  * * *
10  * * *

 

This is effecting my ability to work remotely with a GUI due to the increase in latency, I have to lower my graphical NoMachine settings in order to view things without delay. My IP address is 68.33.199.201. 

 

The return path is about the same as well. 

 

 

 

 

0 Kudos
1 REPLY 1
Ropeguru
New Contributor

Re: Inefficient routing, 3 miles apart.

You cannot always trust the reverswe lookups on the hops. Sometimes IP's get moved around and rDNS does not get updated.

 

Looking at your traceroute, y are 25ms between your location and the first hop on Comcast's side. Between the first hop on their side at 25ms and the last hope, there is no latency increase. I see the last hop as 24ms so I do not see any latency or routing issue here.