Can Spectrum Engineers look into the routing of Durango, CO Traffic?

durangouser

Hi,

Can Engineers please take a look at the routing of traffic in Durango, Co?

Currently all traffic routes through Seattle Washington before going to its final destination. This makes gaming almost impossible unless you are connecting to a server in Seattle. Here are some trace routes to show the issue.

Here is a tracert to a server located in Dallas, Tx

Tracing route to 174.127.113.123.static.midphase.com [174.127.113.123]

over a maximum of 30 hops:

 1   4 ms   8 ms   7 ms unknown [192.168.1.1]

 2   *    *    *   Request timed out.

 3  17 ms  16 ms  11 ms lag-63.durncocu02h.netops.charter.com [69.146.239.174]

 4  32 ms  20 ms  16 ms lag-10.durncocu01h.netops.charter.com [69.144.94.94]

 5  13 ms  15 ms  15 ms lag-27.gdjtco0602h.netops.charter.com [96.34.76.114]

 6  56 ms  62 ms  52 ms lag-24.msslmt33zp0.netops.charter.com [69.144.131.142]

 7  69 ms  74 ms  66 ms lag-702.bbr02sttlwa.netops.charter.com [69.144.130.200]

 8  68 ms  71 ms  66 ms lag-804.prr04sttlwa.netops.charter.com [96.34.3.161]

 9  77 ms  69 ms  70 ms lag-17.ear3.Seattle1.Level3.net [4.68.74.209]

 10   *    *    *   Request timed out.

 11  104 ms  107 ms  107 ms HOSTING-SER.ear5.Dallas1.Level3.net [4.7.207.6]

 12  108 ms  108 ms  106 ms 174.127.115.5.static.midphase.com [174.127.115.5]

 13  113 ms  112 ms  112 ms 174.127.113.123.static.midphase.com [174.127.113.123]

You can see it gets routed through seattle before traveling to Dallas instead of routing through Albuquerque or Denver which are much much closer to Durango and Dallas. Ping in game is about 105ms minimum

Heres a tracert to a server in Washington D.C. This one is especially ridiculous because the connection goes to Seattle then back to Denver before making its way to D.C.

Tracing route to 173.233.139.172 over a maximum of 30 hops

 1   1 ms   7 ms   7 ms unknown [192.168.1.1]

 2   *    *    *   Request timed out.

 3  16 ms  16 ms  15 ms lag-63.durncocu02h.netops.charter.com [69.146.239.174]

 4  16 ms  15 ms  16 ms lag-10.durncocu01h.netops.charter.com [69.144.94.94]

 5  12 ms  16 ms  24 ms lag-27.gdjtco0602h.netops.charter.com [96.34.76.114]

 6  44 ms  46 ms  43 ms lag-24.msslmt33zp0.netops.charter.com [69.144.131.142]

 7  61 ms  63 ms  63 ms lag-702.bbr02sttlwa.netops.charter.com [69.144.130.200]

 8  62 ms  64 ms  57 ms lag-804.prr04sttlwa.netops.charter.com [96.34.3.161]

 9  66 ms  65 ms  66 ms be-206-pe12.seattle.wa.ibone.comcast.net [71.25.198.17]

 10  55 ms  57 ms  55 ms be-2312-cs03.seattle.wa.ibone.comcast.net [96.110.34.137]

 11  57 ms  55 ms  56 ms be-1311-cr11.seattle.wa.ibone.comcast.net [96.110.47.202]

 12  91 ms  90 ms  89 ms be-301-cr11.champa.co.ibone.comcast.net [96.110.36.209]

 13  92 ms  81 ms  81 ms be-1211-cs02.champa.co.ibone.comcast.net [96.110.37.197]

 14  86 ms  80 ms  82 ms be-1213-cr13.champa.co.ibone.comcast.net [96.110.37.230]

 15  84 ms  88 ms  80 ms be-304-cr13.1601milehigh.co.ibone.comcast.net [96.110.36.206]

 16  83 ms  80 ms  84 ms be-1313-cs03.1601milehigh.co.ibone.comcast.net [96.110.39.105]

 17  86 ms  81 ms  85 ms be-1311-cr11.1601milehigh.co.ibone.comcast.net [96.110.39.74]

 18   *    *   104 ms be-302-cr21.350ecermak.il.ibone.comcast.net [96.110.37.149]

 19   *   116 ms   *   be-1221-cs22.350ecermak.il.ibone.comcast.net [68.86.82.245]

 20  113 ms  116 ms  113 ms be-1224-cr24.350ecermak.il.ibone.comcast.net [68.86.84.142]

 21  126 ms  124 ms  123 ms be-301-cr12.pittsburgh.pa.ibone.comcast.net [96.110.39.158]

 22  124 ms  129 ms  122 ms be-1212-cs02.pittsburgh.pa.ibone.comcast.net [96.110.38.149]

 23  130 ms  131 ms  130 ms be-1211-cr11.pittsburgh.pa.ibone.comcast.net [96.110.38.134]

 24  122 ms  122 ms  122 ms be-302-cr12.beaumeade.va.ibone.comcast.net [96.110.32.101]

 25  129 ms  122 ms  124 ms be-1112-cs01.beaumeade.va.ibone.comcast.net [68.86.84.145]

 26  124 ms  121 ms  127 ms be-3112-pe12.ashburn.va.ibone.comcast.net [96.110.34.114]

 27  127 ms  133 ms  132 ms 209.192.153.250

 28  135 ms  136 ms  136 ms 96.46.179.79

 29  136 ms  130 ms  132 ms 173.233.139.172

I also have coworkers that have spectrum and live ~30 minutes outside of town, and their connection gets routed through Denver as expected.

Can we please get someone to look into this?

Here is a photo of ping times to Azure Servers from Durango as well.

I will also add that I've had a truck come by my place when I first noticed this behavior just in case somehow it was something weird with my connection and the technician agreed with me that it was a Spectrum Routing Issue.

Also to note, all of these tracert's and ping tests were done with a wired connection.

Thank you.

James_M

@William_M wrote on 4/9/23

Yes, the fastest route is not always the most direct route. There may be congestion or other server/line issues on the more direct route, or there may be higher capacity lines or less stops over all if you go the wrong way first, however the overall ping does seem higher than normal.

If you run a tracert to 8.8.8.8 is it also that high? Will you please also run regular ping tests so we can see the min, max, and average ping?

Renee_T

Hello @durangouser

Welcome to our community! I apologize for any frustration. The path the connection takes is not something that we would be able to escalate as most of it is an automated process and in your second example the servers that are doing most of the routing after Seattle are Comcast servers, which we wouldn't be able to access. Most likely what is happening on the routing is that the hub servicing your immediate area is sensing that the Seattle connection is faster for you. While someone being about 30 minutes away from you may not seem like much distance wise, it is likely that they are on another hub entirely and that hub is routing traffic through Denver.

HT_Greenfield

None of those route traces show what carrier or route or how many hops or how much lag your gaming traffic is going to take from Charter Netops in either Seattle or Denver to the host server.

William_M

Yes, the fastest route is not always the most direct route. There may be congestion or other server/line issues on the more direct route, or there may be higher capacity lines or less stops over all if you go the wrong way first, however the overall ping does seem higher than normal.

If you run a tracert to 8.8.8.8 is it also that high? Will you please also run regular ping tests so we can see the min, max, and average ping?