Author Topic: traceroute to tastyspleen (Read 14721 times)

. · « **Reply #30 on:** January 28, 2008, 06:20:03 PM »

A few snapshots I took tonight. The first one I went into the yellow.

http://i88.photobucket.com/albums/k179/vvvSinfulvvv/yuck.jpg
http://i88.photobucket.com/albums/k179/vvvSinfulvvv/netgrapheww.jpg
http://i88.photobucket.com/albums/k179/vvvSinfulvvv/railz012808.jpg

This is a shot I took at gba server last night.

http://i88.photobucket.com/albums/k179/vvvSinfulvvv/gbapl.jpg

Now I am including tracert and ping information for gba's server as well because they, Vigilante's server, is through theplanet as well. So I had a theory that maybe the bad egg could be pinpointed through comparison of tracerts. My deduction is, including looking at others' tracerts as well, the problem may begin with the ip 70.87.253.XX(X).

console · « **Reply #31 on:** January 28, 2008, 07:29:43 PM »

Thanks Catalyst,

Much appreciated.

In your traceroutes, I'd bet the problem begins about hop 7:

xe-0-3-0.r21.chcgil09.us.bb.gin.ntt.net [129.250.3.221]

For some reason, your route to vigilante's server stays on att.net, but your route to tastyspleen crosses over to ntt.net. The packetloss shown in your traceroutes appears to begin after hop 7.

To everyone else with similar looking netgraphs, please send me a bunch of traceroutes like Catalyst did, it will help.

Thanks,

[BTF]Fatknitty · « **Reply #32 on:** January 28, 2008, 08:41:07 PM »

Thanks Cat, GAWD I love you

Fat

console · « **Reply #33 on:** January 28, 2008, 10:48:22 PM »

I have opened a trouble ticket with theplanet, providing them with Cat's and Knitty's traceroutes and netgraph screenshots.

Hopefully, since it appears ntt.net is peered directly with theplanet, they will have some chance of effecting a solution.

We'll see how it goes....

Thanks!

quadz

console · « **Reply #34 on:** January 29, 2008, 09:57:14 AM »

Ugh...

Quote from: theplanet

The route that is give the problem is mostly inbound from what I can see as the trace route from the server back shows it stayed in the att network on the way back and didn't go to ntt. You need to contact NTT with your trace routes to show the problem is in their network. I will send the ticket on to the network folks to see if there is any contracts they have that can help get it cleared up.

. · « **Reply #35 on:** January 29, 2008, 10:11:40 AM »

I am not surprised at their response. I'll try and come up with more info tonight. If we need to submit a trouble report to UTT, then I'll be happy to do so. I have NeoTrace, which can sometimes give contact info. Although I have not received responses back, I have had success in router issues getting cleared up for example cogentco. I figure it never hurts to try.

jägermonsta · « **Reply #36 on:** January 29, 2008, 11:07:21 AM »

Quote from: console on January 29, 2008, 09:57:14 AM

Quote from: theplanet
The route that is give the problem is mostly inbound from what I can see as the trace route from the server back shows it stayed in the att network on the way back and didn't go to ntt. You need to contact NTT with your trace routes to show the problem is in their network. I will send the ticket on to the network folks to see if there is any contracts they have that can help get it cleared up.

rempty.

Pr0c3550r · « **Reply #37 on:** January 29, 2008, 11:38:57 AM »

The connect has increased by 90+ @ DM , Mutant and Railz.

Oh Well, again

Peace

console · « **Reply #38 on:** January 29, 2008, 12:04:56 PM »

Quote from: [EoM] Pr0c3550r® on January 29, 2008, 11:38:57 AM

The connect has increased by 90+ @ DM , Mutant and Railz.

When this happens, please do some traceroutes...

Thanks,

Pr0c3550r · « **Reply #39 on:** January 29, 2008, 01:26:00 PM »

Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Peterpathping tastyspleen.net

Tracing route to tastyspleen.net [74.54..226]
over a maximum of 30 hops:
0 Peter-PC.bc.hsia.telus.net [75.154.116]
1 d66--8-254.bchsia.telus.net [66.8.254]
2 154.11.89.129
3 toroonnlbr00.bb.telus.com [154.11.11.66]
4 so-4-3-2.cr1.ord2.us.above.net [216.200.254.30]
5 so-3-0-0.cr1.dfw2.us.above.net [64.125.30.249]
6 64.124.79.77.theplanet.com [64.124.79.77]
7 te7-1.dsr02.dllstx3.theplanet.com [70.87.253.18]
8 7a.fd.5746.static.theplanet.com [70.87.253.122]
9 po2.car06.dllstx6.theplanet.com [12.96.160.40]
10 e2.ba.364a.static.theplanet.com [74.54.186.226]

Computing statistics for 250 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Peter-PC.bc.hsia.telus.net [7
5.154.116]
0/ 100 = 0% |
1 13ms 0/ 100 = 0% 0/ 100 = 0% d66--254.bchsia.telus.net [66
.8.254]
0/ 100 = 0% |
2 27ms 0/ 100 = 0% 0/ 100 = 0% 154.11.89.129
0/ 100 = 0% |
3 --- 100/ 100 =100% 100/ 100 =100% toroonnlbr00.bb.telus.com [154.11.
11.66]
0/ 100 = 0% |
4 135ms 5/ 100 = 5% 5/ 100 = 5% so-4-3-2.cr1.ord2.us.above.net [21
6.200.254.30]
0/ 100 = 0% |
5 165ms 3/ 100 = 3% 3/ 100 = 3% so-3-0-0.cr1.dfw2.us.above.net [64
.125.30.249]
0/ 100 = 0% |
6 162ms 1/ 100 = 1% 1/ 100 = 1% 64.124.79.77.theplanet.com [64.124
.79.77]
0/ 100 = 0% |
7 --- 100/ 100 =100% 100/ 100 =100% te7-1.dsr02.dllstx3.theplanet.com
[70.87.253.18]
0/ 100 = 0% |
8 --- 100/ 100 =100% 100/ 100 =100% 7a.fd.5746.static.theplanet.com [7
0.87.253.122]
0/ 100 = 0% |
9 --- 100/ 100 =100% 100/ 100 =100% po2.car06.dllstx6.theplanet.com [1
2.96.160.40]
0/ 100 = 0% |
10 162ms 0/ 100 = 0% 0/ 100 = 0% e2.ba.364a.static.theplanet.com [7
4.54.186.226]

Trace complete.

C:\Users\Peter

Interesting, I hope this helps

console · « **Reply #40 on:** January 29, 2008, 02:10:13 PM »

Quote from: [EoM] Pr0c3550r® on January 29, 2008, 01:26:00 PM

2 27ms 0/ 100 = 0% 0/ 100 = 0% 154.11.89.129
3 --- 100/ 100 =100% 100/ 100 =100% toroonnlbr00.bb.telus.com [154.11.11.66]
4 135ms 5/ 100 = 5% 5/ 100 = 5% so-4-3-2.cr1.ord2.us.above.net [216.200.254.30]

Thanks. In this case, the problem is between hops 2 and 4... crossing between above.net and telus.com.

I see that in the reverse direction as well:

traceroute to 75.154.xxx.xxx (75.154.xxx.xxx), 30 hops max, 52 byte packets 1 e1.ba.364a.static.theplanet.com (74.54.186.225) 0.529 ms 0.438 ms 0.389 ms 2 vl1.dsr01.dllstx2.theplanet.com (12.96.160.9) 0.255 ms 0.231 ms 0.248 ms 3 71.fd.5746.static.theplanet.com (70.87.253.113) 0.416 ms 0.388 ms 0.414 ms 4 et3-1.ibr03.dllstx3.theplanet.com (70.87.253.1) 0.391 ms 0.394 ms 0.369 ms 5 gw-cr2.dfw2.us.above.net (216.200.6.233) 0.542 ms 0.439 ms 0.457 ms 6 so-0-2-1.mpr2.ord2.us.above.net (64.125.30.254) 26.972 ms 26.811 ms 26.685 ms 7 telus-mfn.ord2.above.net (216.200.254.29) 101.319 ms 100.969 ms 112.366 ms 8 blackdiamond.mtl.total.net (154.11.89.161) 150.529 ms * 153.201 ms 9 * blackdiamond.mtl.total.net (154.11.89.161) 150.600 ms 156.400 ms 10 * * *

Unfortunately that part of the route is way beyond my meager influence...

I think you'd need to contact above.net....

Regards,

quadz

legendary fool · « **Reply #41 on:** January 29, 2008, 03:41:11 PM »

Tracing route to tastyspleen.net [74.54.186.226]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms homeportal [192.168.1.254]
2 10 ms 11 ms 11 ms adsl-70-133-159-254.dsl.ablntx.sbcglobal.net [70
.133.159.254]
3 11 ms 11 ms 10 ms dist2-vlan60.ablntx.sbcglobal.net [151.164.166.1
51]
4 10 ms 13 ms 10 ms bb2-g1-3-0.ablntx.sbcglobal.net [151.164.166.230
]
5 17 ms 17 ms 17 ms 151.164.93.73
6 14 ms 17 ms 17 ms 151.164.251.162
7 15 ms 16 ms 15 ms te7-1-10G.ar2.DAL2.gblx.net [67.16.129.117]
8 * 26 ms 17 ms The-Planet.GigabitEthernet7-3.ar2.DAL2.gblx.net
[64.208.170.198]
9 16 ms 17 ms 16 ms te7-2.dsr01.dllstx3.theplanet.com [70.87.253.10]

10 15 ms 17 ms 17 ms 76.fd.5746.static.theplanet.com [70.87.253.118]

11 * 17 ms 16 ms po1.car06.dllstx6.theplanet.com [12.96.160.8]
12 15 ms 15 ms 17 ms e2.ba.364a.static.theplanet.com [74.54.186.226]

Netgraph
http://img246.imageshack.us/my.php?image=netgraphei8.jpg

Pr0c3550r · « **Reply #42 on:** January 29, 2008, 03:59:46 PM »

Thanks for your time and effort.

Me thinks I gotta go back to Cable, It's always been very consistent.

dsl has proven that, from here anyways.

Peace

console · « **Reply #43 on:** January 29, 2008, 06:00:10 PM »

Quote from: legendary fool on January 29, 2008, 03:41:11 PM

http://img246.imageshack.us/my.php?image=netgraphei8.jpg

Thanks! I've added your netgraph and traceroute to the trouble ticket. You are not being routed through ntt.net, so it would appear the problem is more widespread...

[BTF]Fatknitty · « **Reply #44 on:** January 30, 2008, 06:49:55 AM »

Played a couple of games on vanilla few minutes ago and had no packet loss. Hopefully the problem was fixed.

Author Topic: traceroute to tastyspleen (Read 14721 times)

El Box de Shoutamente