just curious. happens when the route approaches my local Comcast area.
1.ip-10-19-196-65.ec2.internal (0 ms)
2.ip-10-0-41-10.ec2.internal (0 ms)
3.ip-10-0-41-39.ec2.internal (0 ms)
4.ip-10-130-40-5.ec2.internal (0 ms)
5.100.64.12.198 (0 ms)
6.*
7.*
8.*
9.*
10.100.64.16.77 (0 ms)
11.205.251.245.120 (1 ms)
12.205.251.245.20 (1 ms)
13.xe-7-0-0.edge2.Washington1.Level3.net (1 ms)
14.xe-11-2-1.edge3.Washington1.Level3.net (1 ms)
15.vlan80.csw3.Washington1.Level3.net (2 ms)
16.ae-8-8.ebr1.Washington12.Level3.net (1 ms)
17.ae-2-52.edge2.Washington12.Level3.net (2 ms)
18.23.30.207.93 (4 ms)
19.23.30.207.93 (5 ms)
20.et-7-1-0-0-ar01.goodslettvll.tn.nash.comcast.net (25 ms)
21.et-7-1-0-0-ar01.goodslettvll.tn.nash.comcast.net (25 ms)
22.te-17-10-cdn05.ruralhillrd.tn.nash.comcast.net (40 ms)
23.c-98-240-12-138.hsd1.tn.comcast.net (35 ms)
24.c-98-240-12-138.hsd1.tn.comcast.net (35 ms)
25.my.domain (36 ms)
this is from the netalyzr, but command line traces show the same thing.
maybe some sort of internal vlan routing adds a hop or 2?
↧