Menu
What's new

Tracert

d00b

d00b

The 47 Ronin
Tracing route to c-66-151-138-51.managed-vds.internap-sj.nfoservers.com [66.151.
138.51]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.0.1
2 7 ms 9 ms 8 ms 10.98.192.1
3 8 ms 8 ms 8 ms 192.168.22.97
4 21 ms 21 ms 19 ms 192.168.100.118
5 * * * Request timed out.
6 41 ms 40 ms 66 ms ae-2-3514.edge2.Atlanta4.Level3.net [4.69.150.16
5]
7 141 ms 138 ms 140 ms gtt-level3.Atlanta4.level3.net [4.68.63.158]
8 181 ms 178 ms 178 ms xe-11-3-0.sjc10.ip4.gtt.net [89.149.182.69]
9 182 ms 180 ms 182 ms internap-gw.ip4.gtt.net [77.67.70.26]
10 182 ms 181 ms 180 ms border1.t3-1-bbnet1.sje003.pnap.net [66.151.144.
27]
11 179 ms 180 ms 180 ms c-66-151-138-51.managed-vds.internap-sj.nfoserve
rs.com [66.151.138.51]

Trace complete.


What does all this shit mean and did I do it correctly? haha First time doing this for me, so I'm trying to figure it all out.
 
I was talking to the people at cable one and they're sending out a technician today to check it out. I would normally ping around 75-80, same as @DeSiRe. since shes near by. but I'm randomly going up 100 ping these past few days.
 
That mid span POP is a problem, not responding (5 * * * Request timed out), need to get that POP id. Run some more tracert at different times and get that POP to respond. Internap sure seems to be mugging it for you a bit, but until that other POP is dealt with, hard to say.


Also toss up a tracert to Google.
 
Tracing route to c-66-151-138-51.managed-vds.internap-sj.nfoservers.com [66.151.
138.51]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 7 ms 6 ms 8 ms 10.98.192.1
3 8 ms 8 ms 8 ms 192.168.22.97
4 23 ms 20 ms 20 ms 192.168.100.118
5 * * * Request timed out.
6 42 ms 39 ms 45 ms ae-2-3514.edge2.Atlanta4.Level3.net [4.69.150.16
5]
7 41 ms 44 ms 40 ms gtt-level3.Atlanta4.level3.net [4.68.63.158]
8 79 ms 79 ms 77 ms xe-7-2-0.sjc10.ip4.gtt.net [89.149.184.150]
9 82 ms 85 ms 79 ms internap-gw.ip4.gtt.net [77.67.70.26]
10 82 ms 79 ms 78 ms border1.t3-1-bbnet1.sje003.pnap.net [66.151.144.
27]
11 79 ms 82 ms 81 ms c-66-151-138-51.managed-vds.internap-sj.nfoserve
rs.com [66.151.138.51]

Trace complete.

I ran this at 5:50 AM (3:30 for you guys) and that's my typical ping, however, 5 still times out.

And @Fasttrak, here's a tracert to google.

Tracing route to google.com [64.233.176.139]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms 192.168.0.1
2 12 ms 9 ms 7 ms 10.98.192.1
3 25 ms 9 ms 12 ms 192.168.22.97
4 20 ms 21 ms 21 ms 192.168.100.118
5 23 ms 21 ms 31 ms 9-1-21.ear1.Dallas1.Level3.net [4.34.191.37]
6 21 ms 20 ms 31 ms Google-level3-3x10G.Dallas.Level3.net [4.68.70.1
66]
7 33 ms 21 ms 23 ms 72.14.233.67
8 21 ms 21 ms 20 ms 72.14.237.221
9 41 ms 39 ms 39 ms 209.85.254.102
10 43 ms 41 ms 39 ms 209.85.248.57
11 * * * Request timed out.
12 40 ms 38 ms 39 ms 64.233.176.139

Trace complete.
 
@d00b - it looks like level3's connection looks acceptable right now, but that might be different during high traffic periods (like 7pm-12am, EST).
 
You must log in or register to reply here.
Top