typhune's profile

New Poster

 • 

3 Messages

Wednesday, February 14th, 2024 8:23 PM

Closed

Bad routing in Virginia

I need to escalate a ticket to a network engineer at comcast / xfinity.  I am located in Northern Virginia, the home of 80+% of the internet traffic and datacenters.  Typically all pings / traceroutes are lightning quick due to the proximity of the edge servers here around Ashburn, VA

As of Feb 11 at exactly 7am, ping jumped from a rock solid 10ms to any local speedtest server to mid 30s and has stayed there since..  Performing traceroutes Now to a server sitting in ashburn now routes down through richmond, to Georgia, and back up to ashburn.  Something is clearly wrong with the routing at Comcast, and I wanted to escalate this.  I have a traceroute from my home to phoenixnap in ashburn.

traceroute to speedash.phoenixnap.com (131.153.128.2), 64 hops max, 52 byte packets

1  usg-3p (192.168.1.1)  1.242 ms *  0.574 ms

2  10.0.0.1 (10.0.0.1)  1.197 ms  1.344 ms  1.160 ms

3  c-73-12-76-1.hsd1.va.comcast.net (73.12.76.1)  4.360 ms  3.521 ms  4.659 ms

4  po-151-rur02.sterling.va.richmond.comcast.net (68.85.226.77)  2.172 ms  2.849 ms  2.093 ms

5  162.151.162.137 (162.151.162.137)  6.434 ms  7.233 ms  6.815 ms

6  * * be-31512-cs01.56marietta.ga.ibone.comcast.net (96.110.43.193)  19.429 ms

7  be-2103-pe03.56marietta.ga.ibone.comcast.net (96.110.37.82)  20.794 ms  20.045 ms  20.325 ms

8  ix-xe-4-2-1-0.tcore1.a56-atlanta.as6453.net (209.58.44.41)  19.219 ms

    ix-xe-9-0-0-0.tcore1.a56-atlanta.as6453.net (209.58.44.1)  20.249 ms  23.684 ms

9  if-ae-43-2.tcore2.a56-atlanta.as6453.net (64.86.113.150)  32.653 ms  32.489 ms  33.034 ms

10  if-bundle-21-2.qcore1.aeq-ashburn.as6453.net (216.6.87.38)  31.776 ms  32.753 ms *

11  if-ae-33-2.tcore1.aeq-ashburn.as6453.net (66.198.154.10)  31.908 ms  32.567 ms  32.884 ms

12  66.198.155.73 (66.198.155.73)  32.210 ms  31.820 ms  32.410 ms

13  eth.7.2.cr2.ash0.phoenixnap.com (199.201.104.74)  31.547 ms  32.312 ms  32.539 ms

14  * * *

15  131.153.128.2 (131.153.128.2)  32.567 ms  32.206 ms  32.009 ms

Contributor

 • 

168 Messages

9 months ago

@typhune - this could be a peering issue with Level3 in Sterling,VA that is why your traffic goes to Atlanta area to comeback to VA via as6453
Below is how I am able to reach 131.153.128.2 from the Beltway region -

traceroute to speedash.phoenixnap.com (131.153.128.2), 64 hops max, 52 byte packets
 1  home (192.168.0.1)  2.393 ms  1.982 ms  1.513 ms
 2  node (96.120.106.65)  12.170 ms  9.913 ms  9.044 ms
 3  po-301-1204-rur02.mtairy.md.bad.comcast.net (24.124.176.249)  9.757 ms  9.393 ms  11.420 ms
 4  po-2-rur01.mtairy.md.bad.comcast.net (68.85.67.13)  10.211 ms *  11.797 ms
 5  ae-32-ar01.capitolhghts.md.bad.comcast.net (69.139.246.121)  12.199 ms  11.524 ms  12.458 ms
 6  be-501-arsc1.capitolhghts.md.bad.comcast.net (96.110.235.17)  12.797 ms  13.791 ms *
 7  * * *
 8  ae2.3601.edge2.washington111.level3.net (4.69.136.66)  18.967 ms  13.872 ms  13.535 ms
 9  phoenix-nap.edge2.washington111.level3.net (4.39.9.250)  13.800 ms  13.959 ms  13.608 ms
10  eth.7.2.cr2.ash0.phoenixnap.com (199.201.104.74)  13.068 ms  13.905 ms *
11  * * *
12  131.153.128.2 (131.153.128.2)  14.648 ms  14.235 ms  13.509 ms

Contributor

 • 

168 Messages

typhune - Found this link on Arin with the public POC info, you might be interested in.

forum icon

New to the Community?

Start Here