Thread: Tracert's

Yeah, I turned of QoS in the router after posting. IDK if that was the issue, maybe I will get on later in the week.

-H

Yeah, I turned of QoS in the router after posting. IDK if that was the issue, maybe I will get on later in the week.

-H

Tracing route to c-74-91-120-45.internap-dallas.nfoservers.com [74.91.120.45]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms RT-C0C1C02ABB8D [192.168.0.1]
2 10 ms 10 ms 10 ms 98.245.224.1
3 12 ms 15 ms 10 ms xe-9-0-1-0-sur02.aurora.co.denver.comcast.net [68.85.220.241]
4 12 ms 11 ms 14 ms ae-24-0-ar01.aurora.co.denver.comcast.net [162.151.50.33]
5 15 ms 21 ms 16 ms he-3-7-0-0-cr01.denver.co.ibone.comcast.net [68.86.87.89]
6 10 ms 9 ms 17 ms xe-0-0-1-0-pe01.910fifteenth.co.ibone.comcast.net [68.86.84.22]
7 20 ms 19 ms 40 ms dvr-edge-13.inet.qwest.net [72.164.247.149]
8 * * * Request timed out.
9 30 ms 32 ms 33 ms 67.133.189.94
10 83 ms 435 ms 35 ms border2.pc-1-bbnet1.ext1a.dal.pnap.net [216.52.191.25]
11 714 ms 244 ms 34 ms c-74-91-120-45.internap-dallas.nfoservers.com [74.91.120.45]

Trace complete.

Trace to the TPG BF4 server, note the 435, 714, and 244ms pings at the final two stops on the route.