Author Topic: Higher ping (Read 8864 times)

console · « **Reply #15 on:** September 15, 2007, 09:21:51 AM »

Krez, I tried some traceroutes from the server to your IP.

At least in the reverse direction, it does look like there's a roadrunner router near you that may be adding unexpected latency.

Here's one from tastyspleen.net:

traceroute to 68.201.xxx.xxx (68.201.xxx.xxx), 30 hops max, 38 byte packets
1 49.f8.1343.static.theplanet.com (67.19.248.73) 0.592 ms 0.609 ms 0.720 ms
2 gi4-8.dsr02.dllstx4.theplanet.com (67.19.255.173) 0.919 ms 0.497 ms 0.468 ms
3 po42.dsr02.dllstx3.theplanet.com (70.87.253.77) 197.167 ms 0.930 ms 20.207 ms
4 et3-1.ibr03.dllstx3.theplanet.com (70.87.253.21) 0.620 ms 2.365 ms 0.690 ms
5 * xe-4-4.r03.dllstx09.us.bb.gin.ntt.net (157.238.225.5) 1.159 ms 0.792 ms
6 ae-2.r21.dllstx09.us.bb.gin.ntt.net (129.250.2.173) 0.880 ms 0.963 ms 0.700 ms
7 pop1-dls-P3-2.atdn.net (66.185.133.93) 1.166 ms 1.793 ms 1.423 ms
8 bb2-dls-P0-0.atdn.net (66.185.133.82) 1.273 ms 1.436 ms 1.422 ms
9 pop2-dls-P1-0.atdn.net (66.185.133.99) 3.071 ms 1.156 ms 0.842 ms
10 RR-Houston.atdn.net (66.185.133.106) 1.014 ms 1.278 ms 1.208 ms
11 gig13-0-0.austtxrdcsc-rtr3.texas.rr.com (72.179.205.22) 5.821 ms 5.957 ms gig12-0-0.austtxrdcsc-rtr3.texas.rr.com (72.179.205.77) 6.301 ms
12 gig2-0-0.austtxrdcsc-rtr1.austin.rr.com (24.93.33.133) 6.171 ms 6.075 ms 5.990 ms
13 srp2-0.austtxrdc-rtr2.austin.rr.com (24.27.12.2) 7.496 ms 6.199 ms 6.229 ms
14 pos5-0.austtxrdc-rtr2.austin.rr.com (66.68.1.141) 43.038 ms 43.015 ms 43.034 ms
15 gig0-3.wcfltx01-ubr3.sw.rr.com (24.160.24.25) 29.217 ms 29.179 ms 28.959 ms
16 * * *

Here's one from east.tastyspleen.net:

traceroute to 68.201.xxx.xxx (68.201.xxx.xxx), 30 hops max, 38 byte packets
1 69.9.168.1 (69.9.168.1) 0.556 ms 0.402 ms 0.057 ms
2 0.fe0-3.esw7.lga1.us.voxel.net (69.9.166.37) 0.539 ms 0.602 ms 0.481 ms
3 5.ae0.cr2.lga1.us.voxel.net (69.9.164.62) 0.554 ms 0.358 ms 0.696 ms
4 0.te4-1.tsr1.lga3.us.voxel.net (208.122.44.38) 0.723 ms 0.627 ms 0.661 ms
5 tsic-1.lga3.us.voxel.net (213.248.95.45) 0.545 ms 0.716 ms 0.532 ms
6 aol-ic-122179-nyk-b1.telia.net (213.248.82.218) 1.491 ms 1.648 ms 1.235 ms
7 bb2-nye-P1-0.atdn.net (66.185.151.66) 0.759 ms 0.656 ms 0.628 ms
8 bb2-chi-P5-0.atdn.net (66.185.152.142) 22.392 ms 23.024 ms 22.114 ms
9 bb1-dls-P4-0.atdn.net (66.185.152.12) 41.339 ms 40.551 ms 40.489 ms
10 pop2-dls-P0-0.atdn.net (66.185.133.97) 42.048 ms 41.935 ms 41.971 ms
11 rr-Houston.atdn.net (66.185.132.26) 43.106 ms 42.458 ms 42.451 ms
12 gig13-0-0.austtxrdcsc-rtr3.texas.rr.com (72.179.205.22) 47.292 ms gig12-0-0.austtxrdcsc-rtr3.texas.rr.com (72.179.205.77) 46.872 ms 46.365 ms
13 gig2-0-0.austtxrdcsc-rtr1.austin.rr.com (24.93.33.133) 47.299 ms 46.980 ms 47.971 ms
14 srp0-0.austtxrdc-rtr2.austin.rr.com (24.27.12.34) 46.524 ms 46.662 ms 46.332 ms
15 pos5-0.austtxrdc-rtr2.austin.rr.com (66.68.1.141) 84.283 ms 84.037 ms 84.268 ms
16 gig0-3.wcfltx01-ubr3.sw.rr.com (24.160.24.25) 70.468 ms 70.795 ms 70.642 ms
17 * * *

I'm not 100% sure what to make of that, since on both occasions the highlighted router above was slower to respond to ping packets than to forward packets through. (Note that the following hop has lower times.) But that might be an indication the router is overloaded with traffic.

Hope this helps,

quadz

reaper · « **Reply #16 on:** September 15, 2007, 09:38:22 AM »

Quote from: quadz

Krez, I tried some traceroutes from the server to your IP.

At least in the reverse direction, it does look like there's a roadrunner router near you that may be adding unexpected latency.

Here's one from tastyspleen.net:

all the other routers show low latency, even to packets that are treated specially (sent to the CPU), except for that RR router near Krez. so it seems like a pretty safe bet, that's where the problem lies.

Quote from: krez

how can i get by this router to do a traceroute

when you intiiate traffic from your PC, it should be allowed back in. you probably have a private address (172,,192,,or 10), this gets changed to a public address that is on the internet when you connect out. traffic from the internet to you, would not work unless you configure it, but all traffic started at your PC should be allowed back in.

there could be an access-list filtering traffic coming in, or coming back, and we have to change that, or NAT (network address translation) is not working properly. you might want to paste the router make and model, but it looks like that router / circuit is your problem.

krez · « **Reply #17 on:** September 15, 2007, 12:22:16 PM »

excellent quadz, thanks. i pinged that ip you highlighted in yellow though, and i get around 6ms to it. hmm

console · « **Reply #18 on:** September 15, 2007, 01:05:12 PM »

Quote from: krez on September 15, 2007, 12:22:16 PM

i pinged that ip you highlighted in yellow though, and i get around 6ms to it.

What if you ping the router one hop further out (24.27.12.34) ?

krez · « **Reply #19 on:** September 15, 2007, 01:19:22 PM »

Quote from: console on September 15, 2007, 01:05:12 PM

Quote from: krez on September 15, 2007, 12:22:16 PM
i pinged that ip you highlighted in yellow though, and i get around 6ms to it.

What if you ping the router one hop further out (24.27.12.34) ?

45ms. thats it. thats the fucker thats causing my problems. i guess i should call the national helpdesk and ask them to fix it?

R1CH · « **Reply #20 on:** September 15, 2007, 04:15:24 PM »

Also, you might want to give my ftrace a program a try for tracing - it can use UDP which bypasses most routers that filter ICMP traces.
http://www.r1ch.net/stuff/ftrace/

To run in UDP mode put -u on the command line, eg
ftrace -u tastyspleen.net

or if using the GUI version just put:
-u tastyspleen.net

Pr0c3550r · « **Reply #21 on:** September 15, 2007, 06:57:17 PM »

Quote from: reaper on September 15, 2007, 07:50:14 AM

Quote from: processor
[/color]if you have a dynamic ip try releasing your ip and renewing it a few times and see if your ping comes back down, that works for me sometimes...I doubt they would have taken you off fast path, but thats possible...do you have dsl or cable? post some tracert's.

I guess that's possible, but it seems strange if you payed for something and they made a mistake they wouldn't notice. some providers you pay for a faster connection, they implement quality of service, and they do this on the source IP address (source based routing, and quality of service on the path).

a traceroute would definitly be good, i was mentioning earlier that sometimes the times are higher in the traceroute than they are to the destination, which usually shows even more during a problem. like below, hop 13 always showed me 36 ms, but many hops past 13 to google was always 22ms.

Quote from: processor
wtf?

krez · « **Reply #22 on:** September 16, 2007, 10:22:44 AM »

Ok, i unplugged my wii router so i can do tracerouts. Here are the results tracing to tourney1/ra2 server

Tracing route to 4a.f8.1343.static.theplanet.com [67.19.248.74]
over a maximum of 30 hops:

1 11 ms 6 ms 6 ms 10.93.64.1
2 32 ms 29 ms 28 ms gig1-0-0.wcfltx01-rtr1.sw.rr.com [24.160.24.50]

3 29 ms 29 ms 29 ms pos5-0.austtxrdcsc-rtr1.austin.rr.com [66.68.1.137]
4 29 ms 29 ms 29 ms gig2-0-0.austtxrdcsc-rtr3.texas.rr.com [24.93.33.134]
5 35 ms 33 ms 33 ms gig5-3-0.dllatxl3-rtr1.texas.rr.com [72.179.205.21]
6 37 ms 37 ms 38 ms xe-11-0-0.edge3.Dallas1.Level3.net [4.71.198.5]

7 * * * Request timed out.
8 34 ms 35 ms 34 ms THE-PLANET.car4.Dallas1.Level3.net [4.71.122.2]

9 35 ms 37 ms 38 ms te7-2.dsr01.dllstx3.theplanet.com [70.87.253.10]

10 40 ms 42 ms 44 ms po31.dsr01.dllstx4.theplanet.com [70.87.253.74]

11 36 ms 38 ms 37 ms gi1-0-1.car12.dllstx4.theplanet.com [67.19.255.46]
12 36 ms 36 ms 35 ms 4a.f8.1343.static.theplanet.com [67.19.248.74]

Trace complete.

krez · « **Reply #23 on:** September 16, 2007, 10:31:59 AM »

here is the pathping result

Tracing route to tastyspleen.net [67.19.248.74]
over a maximum of 30 hops:
0 jared.gt.rr.com [24.160.28.151]
1 10.93.64.1
2 gig1-0-0.wcfltx01-rtr1.sw.rr.com [24.160.24.50]
3 pos5-0.austtxrdcsc-rtr1.austin.rr.com [66.68.1.137]
4 gig2-0-0.austtxrdcsc-rtr3.texas.rr.com [24.93.33.134]
5 gig5-3-0.dllatxl3-rtr1.texas.rr.com [72.179.205.21]
6 xe-11-1-0.edge3.Dallas1.Level3.net [4.71.198.1]
7 * ae-24-52.car4.Dallas1.Level3.net [4.68.122.48]
8 THE-PLANET.car4.Dallas1.Level3.net [4.71.122.2]
9 te7-2.dsr02.dllstx3.theplanet.com [70.87.253.26]
10 po32.dsr02.dllstx4.theplanet.com [70.87.253.78]
11 gi1-0-2.car12.dllstx4.theplanet.com [67.19.255.174]
12 4a.f8.1343.static.theplanet.com [67.19.248.74]

Computing statistics for 300 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 jared.gt.rr.com [24.160.28.151]
0/ 100 = 0% |
1 6ms 0/ 100 = 0% 0/ 100 = 0% 10.93.64.1
0/ 100 = 0% |
2 29ms 0/ 100 = 0% 0/ 100 = 0% gig1-0-0.wcfltx01-rtr1.sw.rr.com [24.160.24.50]
0/ 100 = 0% |
3 29ms 0/ 100 = 0% 0/ 100 = 0% pos5-0.austtxrdcsc-rtr1.austin.rr.com [66.68.1.137]
0/ 100 = 0% |
4 29ms 0/ 100 = 0% 0/ 100 = 0% gig2-0-0.austtxrdcsc-rtr3.texas.rr.com [24.93.33.134]
0/ 100 = 0% |
5 36ms 0/ 100 = 0% 0/ 100 = 0% gig5-3-0.dllatxl3-rtr1.texas.rr.com [72.179.205.21]
0/ 100 = 0% |
6 41ms 0/ 100 = 0% 0/ 100 = 0% xe-11-1-0.edge3.Dallas1.Level3.net[4.71.198.1]
0/ 100 = 0% |
7 49ms 1/ 100 = 1% 1/ 100 = 1% ae-24-52.car4.Dallas1.Level3.net [4.68.122.48]
0/ 100 = 0% |
8 --- 100/ 100 =100% 100/ 100 =100% THE-PLANET.car4.Dallas1.Level3.net[4.71.122.2]
0/ 100 = 0% |
9 --- 100/ 100 =100% 100/ 100 =100% te7-2.dsr02.dllstx3.theplanet.com[70.87.253.26]
0/ 100 = 0% |
10 --- 100/ 100 =100% 100/ 100 =100% po32.dsr02.dllstx4.theplanet.com [70.87.253.78]
0/ 100 = 0% |
11 --- 100/ 100 =100% 100/ 100 =100% gi1-0-2.car12.dllstx4.theplanet.com [67.19.255.174]
0/ 100 = 0% |
12 35ms 0/ 100 = 0% 0/ 100 = 0% 4a.f8.1343.static.theplanet.com [67.19.248.74]

Trace complete.

reaper · « **Reply #24 on:** September 16, 2007, 05:05:27 PM »

your ping was 20 before and is now 35?

looks like if there is any time to be saved it's at your local connection to the cable company. you could see if they will make things faster for you.

krez · « **Reply #25 on:** September 17, 2007, 09:42:16 AM »

I talked to a fucker at the national helpdesk today. He pretty much told me that they wont do shit about that router because its connecting fine and not causing any connectivity problems. I will call my local cable office and bitch

reaper · « **Reply #26 on:** September 17, 2007, 10:55:16 AM »

Quote from: krez

I talked to a fucker at the national helpdesk today.

jägermonsta · « **Reply #27 on:** September 17, 2007, 01:16:21 PM »

sucks but I highly doubt complaining will do much to help you. They are going to put you through the same power cycle bullshit I'm sure you've already done and in the end, you'll get no help from them. Best you will get is a credit for your months bill, which I guess isn't so bad. Yeah I earning 15 ping sucks but your grand total is now like 34... can't see how 15ms effects a good player that much when your ping was already that low. Maybe I don't understand that since all q2 servers I play at avg 60-70 ping... 15 more ms on 70 ping would defenitly suck balls.

krez · « **Reply #28 on:** November 02, 2007, 10:53:54 AM »

Well my ping went up again, gaysauce. Unfortunately I dont have many choices for a diff isp, timewarner is a monopoly here.

jägermonsta · « **Reply #29 on:** November 02, 2007, 11:06:38 AM »

Is it 35 now instead of 20?

Author Topic: Higher ping (Read 8864 times)

El Box de Shoutamente