Before posting a new question, please check out our Internet / WiFi and Spectrum TV App troubleshooting pages for common issues, as well as useful information to include in your post.

Advanced Search Options


We have advanced search options to make it easier to locate posts, questions and answers on this community.
More information can be found at Advanced Search Options
If you are looking for something specific, please check if someone else has already asked or answered the same question.

Why is charter routing me to Chicago?

effeffeffeff Posts: 1 Newcomer
edited June 7 in Connectivity May 04, 2022

I'm in Rensselaer NY, and I'm connecting to a server in New York City.

Why is the tracert going to Chicago? Is there anything I can do about this?


Best Answer

  • RAIST5150RAIST5150 Posts: 858 Contributor
    edited May 4 May 04, 2022 Answer ✓

    Looks like Spectrum does not have a direct peering arrangement with the end point's ISP and the route lookup's BGP query is directing you to Level3 to complete the route, which happens to point you to a Chicago on-ramp for that exchange.


    A similar thing happens here in Florence, SC... could bounce a state or two away to hit a server that is literally physically less than 2 miles down the road that is hosted on ATT (I know the details because I was on the implementation team for the project back in the day).


    Nothing new... dates back over a decade. Unless a shorter or more direct route ever gets announced, it will likely persist.

    Traced it just now and it sends me south to Atlanta for the handoff to Level3, then it shoots back across South Carolina to NYC. Routing across the web can be every bit as screwy as the US Postal Service.


    traceroute to 192.223.27.134 (192.223.27.134), 30 hops max, 60 byte packets

     1 (redacted) 9.691 ms 9.620 ms 9.584 ms

     2 lag-63.flrnscwk02h.netops.charter.com (174.111.74.94) 29.959 ms 29.936 ms 29.912 ms

     3 lag-34.clmcsc3001r.netops.charter.com (24.31.196.212) 11.751 ms 15.442 ms 15.387 ms

     4 lag-42.rcr01chrcnctr.netops.charter.com (24.93.64.180) 17.463 ms 17.700 ms 17.921 ms

     5 lag-24.atlngamq46w-bcr00.netops.charter.com (66.109.6.34) 30.560 ms lag-14.atlngamq46w-bcr00.netops.charter.com (66.109.6.82) 30.513 ms lag-24.atlngamq46w-bcr00.netops.charter.com (66.109.6.34) 30.495 ms

     6 lag-303.pr2.atl20.netops.charter.com (66.109.9.105) 29.796 ms lag-0.pr2.atl20.netops.charter.com (66.109.5.125) 47.100 ms lag-302.pr2.atl20.netops.charter.com (66.109.9.103) 47.551 ms

     7 ae-10.edge4.Atlanta2.Level3.net (4.68.37.73) 50.013 ms 28.426 ms 27.401 ms

     8 ae1.3511.edge2.NewYork6.level3.net (4.69.209.78) 31.358 ms 34.524 ms 34.495 ms

     9 INTERNAP-NE.edge2.NewYork6.Level3.net (4.30.176.170) 34.991 ms 34.948 ms 34.941 ms

    10 border1-po1-bbnet1.nyj004.pnap.net (216.52.95.46) 34.208 ms border2-po2-bbnet2.nyj004.pnap.net (216.52.95.110) 34.305 ms border2-po1-bbnet1.nyj004.pnap.net (216.52.95.47) 34.158 ms

    11 inap-b2.e8.router.nyc.nfoservers.com (104.153.107.254) 34.060 ms 34.051 ms inap-b1.e9.router.nyc.nfoservers.com (162.248.95.254) 36.499 ms

    12 v-192-223-27-134.unman-vds.inap-nyc.nfoservers.com (192.223.27.134) 34.921 ms 34.898 ms 34.368 ms

This discussion has been closed.