unplayable high ping at offpeak time

coldwind · Post by **coldwind** » Mon Dec 24, 2007 1:33 am

this happens for more than 2 weeks.

as soon as the time passed 12am, the wow's ping was over 2000.

i did the tracert to some proxy server:

racing route to s16.s5proxy.com [202.167.234.161]

over a maximum of 30 hops:

1 19 ms 19 ms 19 ms 220.233.1.196

2 * * * Request timed out.

3 22 ms * 22 ms 10.0.1.1

4 22 ms 19 ms 19 ms 220.233.2.38

5 29 ms * 21 ms 203.166.92.57

6 20 ms 19 ms 19 ms 210.80.33.189

7 48 ms 19 ms 19 ms 210.80.33.218

8 19 ms 19 ms 19 ms 203.103.244.210

9 * * 140 ms 129.250.4.193

10 179 ms 168 ms 139 ms 129.250.3.181

11 188 ms 189 ms * 129.250.4.54

12 189 ms * 189 ms 203.131.240.122

13 208 ms 199 ms 199 ms 203.131.241.198

14 188 ms * * 202.177.216.33

15 188 ms 189 ms 189 ms 202.167.234.161

Trace complete.

but there is no problme at all during peak time.

I need it to be fixed asap.

netsurfer · Post by **netsurfer** » Mon Dec 24, 2007 11:07 am

Hello,

These ping delays are normal. The later servers are overseas and that's why they are a bit slow. I am currently with AAPT (adsl1 512/128) and did the tracert from my PC and the following is what I got (I removed my home point).

You can do traceroutes from some websites to compare. Go to www.geektools.com and select traceroute.

Tracing route to 202.167.234.161 over a maximum of 30 hops

1 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
2 18 ms 19 ms 20 ms loopback100.cor13.syd.connect.com.au [210.8.1.242]
3 18 ms 19 ms 20 ms ge-0-1-1.dst2.syd.connect.com.au [203.63.170.254]
4 20 ms 19 ms 19 ms ge-0-1-1.bdr5.syd.connect.com.au [203.63.170.227]
5 20 ms 19 ms 19 ms so1-0-0.sybr4.global-gateway.net.nz [203.96.120.121]
6 20 ms 20 ms 19 ms 202.68.65.229
7 219 ms 177 ms 183 ms ge-0-0-0.r01.sydnau01.au.bb.gin.ntt.net [202.68.64.225]
8 252 ms 212 ms 272 ms p4-1-3-0.r00.tokyjp01.jp.bb.gin.ntt.net [129.250.4.161]
9 254 ms 213 ms 229 ms ae-1.r20.tokyjp01.jp.bb.gin.ntt.net [129.250.3.214]
10 298 ms 300 ms 289 ms as-1.r00.newthk01.hk.bb.gin.ntt.net [129.250.2.110]
11 292 ms 275 ms 278 ms po-1.a04.newthk01.hk.ra.gin.ntt.net [203.131.240.122]
12 295 ms 278 ms 293 ms 203.131.241.198
13 302 ms 285 ms 299 ms 202.177.216.33
14 281 ms 304 ms 294 ms 202.167.234.161

coldwind · Post by **coldwind** » Mon Dec 24, 2007 6:01 pm

please look at the time you did the test and mine

it happens every night, thre must be some problem at off-peak time

i post the tracert at 6pm now:

1 13 ms 19 ms 9 ms 220.233.1.196

2 * * * Request timed out.

3 9 ms 9 ms 9 ms 10.0.1.1

4 14 ms 9 ms 19 ms 220.233.2.38

5 18 ms 9 ms 19 ms 203.166.92.57

6 17 ms 19 ms 19 ms 210.80.33.189

7 15 ms 9 ms 19 ms 210.80.33.218

8 9 ms 19 ms 9 ms 203.103.244.210

9 128 ms 129 ms 129 ms 129.250.4.193

10 128 ms 129 ms 129 ms 129.250.3.181

11 178 ms 179 ms 179 ms 129.250.4.54

12 188 ms 189 ms 189 ms 203.131.240.122

13 203 ms 199 ms 199 ms 203.131.241.198

14 187 ms 189 ms 189 ms 202.177.216.33

15 182 ms 179 ms 179 ms 202.167.234.161

Trace complete.

it is normal now, but at night there always appear a *
like "189 ms * 189 ms 203.131.240.122"
this is not the problme about a bit slow, but the problem
with singal loss or request time out

coldwind · Post by **coldwind** » Mon Dec 24, 2007 6:04 pm

can any exetel staff really look at the prolblem and answer me?

coldwind · Post by **coldwind** » Tue Dec 25, 2007 1:20 am

tracert at 1:21am

Tracing route to s16.s5proxy.com [202.167.234.161]

over a maximum of 30 hops:

1 * 17 ms 19 ms 220.233.1.196

2 * * * Request timed out.

3 25 ms 19 ms 19 ms 10.0.1.1

4 19 ms 19 ms 19 ms 220.233.2.38

5 * * * Request timed out.

6 24 ms 19 ms 19 ms 210.80.33.189

7 15 ms 19 ms 19 ms 210.80.33.218

8 16 ms 19 ms 29 ms 203.103.244.210

9 139 ms 139 ms 159 ms 129.250.4.193

10 138 ms 139 ms 139 ms 129.250.3.181

11 197 ms * 184 ms 129.250.4.54

12 191 ms * 193 ms 203.131.240.122

13 203 ms 209 ms 209 ms 203.131.241.198

14 * 192 ms 189 ms 202.177.216.33

15 185 ms 189 ms 189 ms 202.167.234.161

Trace complete.

lots of request time out (*).....so bad

coldwind · Post by **coldwind** » Tue Dec 25, 2007 2:17 am

Tracing route to s16.s5proxy.com [202.167.234.161]

over a maximum of 30 hops:

1 16 ms 19 ms 19 ms 220.233.1.196

2 * * * Request timed out.

3 20 ms 19 ms 20 ms 10.0.1.1

4 18 ms 19 ms 19 ms 220.233.2.38

5 18 ms 19 ms 19 ms 203.166.92.57

6 18 ms 19 ms * 210.80.33.189

7 * * 19 ms 210.80.33.218

8 18 ms 19 ms 19 ms 203.103.244.210

9 177 ms 139 ms 140 ms 129.250.4.193

10 159 ms * 139 ms 129.250.3.181

11 * 248 ms 189 ms 129.250.4.54

12 198 ms 189 ms 189 ms 203.131.240.122

13 207 ms 199 ms 209 ms 203.131.241.198

14 189 ms 199 ms 190 ms 202.177.216.33

15 188 ms 189 ms 199 ms 202.167.234.161

Trace complete.

tracert at 2am

Post by **ForumAdmin** » Wed Dec 26, 2007 8:44 am

coldwind wrote:tracert at 1:21am

Tracing route to s16.s5proxy.com [202.167.234.161]

over a maximum of 30 hops:

1 * 17 ms 19 ms 220.233.1.196

2 * * * Request timed out.

3 25 ms 19 ms 19 ms 10.0.1.1

4 19 ms 19 ms 19 ms 220.233.2.38

5 * * * Request timed out.

6 24 ms 19 ms 19 ms 210.80.33.189

7 15 ms 19 ms 19 ms 210.80.33.218

8 16 ms 19 ms 29 ms 203.103.244.210

9 139 ms 139 ms 159 ms 129.250.4.193

10 138 ms 139 ms 139 ms 129.250.3.181

11 197 ms * 184 ms 129.250.4.54

12 191 ms * 193 ms 203.131.240.122

13 203 ms 209 ms 209 ms 203.131.241.198

14 * 192 ms 189 ms 202.177.216.33

15 185 ms 189 ms 189 ms 202.167.234.161

Trace complete.

lots of request time out (*).....so bad

Request tie outs on a trace are meaningless and don't affect anything.

They simply mean that roter is set not to respond to pings or traces.

There is nothing wrong with those times to US sites.

coldwind · Post by **coldwind** » Thu Dec 27, 2007 2:59 am

ForumAdmin wrote:
coldwind wrote:tracert at 1:21am

Tracing route to s16.s5proxy.com [202.167.234.161]

over a maximum of 30 hops:

1 * 17 ms 19 ms 220.233.1.196

2 * * * Request timed out.

3 25 ms 19 ms 19 ms 10.0.1.1

4 19 ms 19 ms 19 ms 220.233.2.38

5 * * * Request timed out.

6 24 ms 19 ms 19 ms 210.80.33.189

7 15 ms 19 ms 19 ms 210.80.33.218

8 16 ms 19 ms 29 ms 203.103.244.210

9 139 ms 139 ms 159 ms 129.250.4.193

10 138 ms 139 ms 139 ms 129.250.3.181

11 197 ms * 184 ms 129.250.4.54

12 191 ms * 193 ms 203.131.240.122

13 203 ms 209 ms 209 ms 203.131.241.198

14 * 192 ms 189 ms 202.177.216.33

15 185 ms 189 ms 189 ms 202.167.234.161

Trace complete.

lots of request time out (*).....so bad
Request tie outs on a trace are meaningless and don't affect anything.

They simply mean that roter is set not to respond to pings or traces.

There is nothing wrong with those times to US sites.

please compare the time i did the tracert at 1am and 6pm
the one at 1am has lots of * while there is no time out at 6pm
the fact is the ping is so high and unplayable from 1am to 3am
when i play the wow on China's game server.
please look carefully at the problme instead simply stats "meaningless or do not affect anything", if there is no problem, the game's ping is as normal as peak time, why did i post here?
can you expalin why there is none * at 6pm while 6 of * at 1am when
tracert the same server?

David_h · Post by **David_h** » Thu Dec 27, 2007 9:09 am

As an answer to the * you're seeing.

ICMP packets are not a priority for routers and as such they do time out under load since the router has 'better things to do'

This is normal operation and as such the results do not indicate anything out of the ordinary.

You should also be aware that our off peak period coincides with the peak period for traffic in the US which may account for the high pings you're seeing as the results show that the pings go up only outside our network.

dogwomble · Post by **dogwomble** » Thu Dec 27, 2007 2:27 pm

Yeah, wrt ICMP packets I'd agree with David on this one, particularly as the ping times are extremely good up to point 8-9, which are becoming well and truly outside the Exetel network. Up until then I would have expected ping times of roughly double that - in some cases, I remember seeing around 50ms pings in this region, and I'd consider ping times of around that mark to be relatively normal. I don't think these traceroutes do anything at all to assist with troubleshooting - they're showing so ridiculously little (in fact showing a near perfect Internet connection each time) that there's nothing that can be done based on those alone.

You'd need to expand out on the information provided to be able to ascertain what exactly is going on - for example, are any other applications behaving in a similar manner during off peak, have you got any P2P etc. scheduled to start then, etc.?

coldwind · Post by **coldwind** » Thu Dec 27, 2007 3:05 pm

ok thanks for you explanation.

I will try to find another proxy to connect the game server tonight

the ping was 2000 form 1am to 3am for the last 2 weeks.

dogwomble · Post by **dogwomble** » Fri Dec 28, 2007 7:34 am

Lansalot,

Firstly, if you have left Exetel, why are posting in these forums? Can an admin please ban his user account and block his IP address from accessing Exetel services I've seen him do this a few times before

Secondly, why are you being so unhelpful and providing what is obviously misinformation to discredit Exetel? Exetel can be suited to gaming - I do a bit of gaming on the Exetel network (albeit not much of it) and have not once had a problem. While the customer have been a bit slow off the mark to provide information initially, we have a customer here who seems to have a genuine problem and is making a genuine attempt to fix the problem, and trying to provide us with the information required to help them fix the problem, which is more than what I could ever say for you. Can you leave this to the people that are willing to help, rather than lying to cover your own inability to resolve your own problems?