PTCL DNS and European Servers.. Whats wrong with them

Ever since the last SEAMWE fiasco,

I've hardly gotten decent pings on wow..

my pings hover around 350 ~ 500ms .. I don't have problem downloading but the pings are really annoying and sometimes even spikes..

When I am using Gamepath to route my data through another server, its fine .. with sub 200ms.. but with PTCL DNS (automatically assign DNS or even 240 / 243 sub digit DNS, the problem persists.

Any solution to this annoyance?

Opendns and Google DNS doesn't solve the problem.. I've tried.. several times..

I used to play wow (Kilrogg server) until a few months ago - but the latency seems fine to me? Make a character on Kilrogg server and notice the latency. If it's better, then either

1. Probably your server is overcrowded

2. OR , the PTCL problem does exist, but unluckily just for the path of YOUR server (remember, this tracert is for kilrogg server)

C:> tracert 213.248.123.92

Tracing route to 213-248-123-92.customer.teliacarrier.com [213.248.123.92]

over a maximum of 30 hops:

1 3 ms <1 ms <1 ms 10.0.2.1

2 30 ms 38 ms 29 ms 119.152.32.1

3 23 ms 28 ms 20 ms 203.99.170.190

4 21 ms 22 ms 21 ms rwp44.pie.net.pk [221.120.252.9]

5 40 ms 41 ms 39 ms static-khi275-P02-pie.net.pk [221.120.254.18]

6 43 ms 43 ms 53 ms static-khi-ni01-swa.pie.net.pk [202.125.128.162]

7 43 ms 42 ms 44 ms rwp44.pie.net.pk [221.120.250.229]

8 175 ms 174 ms 174 ms pal7-pakistan-telecom-11.pal.seabone.net [195.22

.198.57]

9 172 ms 170 ms 171 ms telia-2-fra34.fra.seabone.net [89.221.34.166]

10 171 ms 171 ms 171 ms telia-2-fra34.fra.seabone.net [89.221.34.166]

11 170 ms 195 ms 167 ms ffm-bb1-link.telia.net [80.91.252.169]

12 194 ms 197 ms 200 ms s-bb1-link.telia.net [80.91.251.144]

13 199 ms 194 ms 192 ms s-b1-link.telia.net [80.91.254.57]

14 300 ms 222 ms 225 ms 80.91.247.33

15 * * * Request timed out.

16 * * * Request timed out.

17 * * * Request timed out.

which dns are you using?

203.99.163.240

202.125.132.12

I had a high latency issue when I started playing wow on vista from pakistan - I tried the fix and it worked, but it was more technical. For people who are not technical , you can try this:

http://www.wowinterface.com/downloads/info13581-LeatrixLatencyFix.html

Also, are you sure this problem started occurring after the semewe issue? I once had an issue with the latest patch of wow, and it totally caused my connection to go fubar. I had to use a second wireless network card installed in my motherboard to connect to a wireless network/wifi, and then switch back to my wired network card to my router again. That was the only thing that resolved my issue.

yeah it started right after that..

right now i am on my wireless network..

I tried it from my home PC, Laptop's Lan, Wireless.. still no avail..

i am still getting 350ms +

I am currently on Magtheridon (its now rated as low)..

thanks for the link..

guess you have to use it for each and every adapter ^^

anyway.. my latency is down to 320+ms atleast its not 600ms or so ..

still.. id like to have 220ms or so like i used to have :<

Neo.. can you post your ip?

someone tells me that there's a good ip range.. I'll set up a static ip on one of those..

try 116.71.175.52

ehy thyhammerer i m also playing wow on european KT server having same problem for over a week now, tell me if u find any solution.

yeah its a bit better now..

getting stagnant 270ms ~ 300ms now..

ensure.. dns is on automatically assign in both your network settings and router..

240 and 243 dns are crowded.

Dear All;

If someone has been suffering at the hands of high latency then its me. I have been playing WoW for over 3 years from Pakistan on Eonar EU. I am in Islamabad.

I have been playing WoW on European servers using PTCL since June 2009. Previously I was playing using Wateen. Wateen was a lame service for this but IMO PTCL 2MB really rocked the last 10 months. My Latency was always under 250ms in game and 25 man raids were like a hot knife through butter.

Somewhere around 23rd May 2010 I started getting #$%# lag, apparent reason BLACKLISTED IPs. So I converted to EDSL 2MB with a static IP with PTCL. Unfortunately still no luck. This is my tracert to Eonar EU. Can someone please help me on what to do? Otherwise I will have to close down my account as I cannot even raid 10 mans with it now :S

Tracing route to 213-248-123-128.customer.teliacarrier.com [213.248.123.128]

over a maximum of 30 hops:

1 2 ms 2 ms 1 ms 172.19.12.50

2 3 ms 3 ms 2 ms 192.168.5.1

3 31 ms 30 ms 28 ms 203.135.12.1

4 12 ms 13 ms 12 ms 203.99.170.22

5 14 ms 13 ms 13 ms rwp44.pie.net.pk [221.120.253.1]

6 33 ms 33 ms 34 ms static-khi275-P01-pie.net.pk [221.120.254.14]

7 43 ms 46 ms 49 ms static-khi-ni02-swa.pie.net.pk [202.125.128.180]

8 43 ms 40 ms 43 ms khi77.ptcl.net.pk [221.120.250.237]

9 134 ms 132 ms 133 ms pos3-1-0.palermo7.pal.seabone.net [195.22.198.57]

10 268 ms 269 ms 269 ms telia.franco34.fra.seabone.net [89.221.34.162]

11 305 ms 267 ms 270 ms telia.franco34.fra.seabone.net [89.221.34.162]

12 266 ms 261 ms 266 ms ffm-bb1-link.telia.net [80.91.252.173]

13 294 ms 295 ms 292 ms s-bb1-link.telia.net [80.91.251.144]

14 296 ms 293 ms 293 ms s-b1-link.telia.net [80.91.249.71]

15 294 ms 291 ms 292 ms s-hdn-i3-link.telia.net [80.91.251.245]

16 * * * Request timed out.

17 * * * Request timed out.

18 * * * Request timed out.

19 * * * Request timed out.

20 * * * Request timed out.

Can someone please help me here? I have done Leatrix as well but to no avail. My Latency is constantly at 450ms+.

Please help. Because I cannot understand what you guys discussed about setting the static IP to?

How can I get my latency to 270ms - 300ms please. It will be most appreciated.

BTW: For all interested, my Characters on Eonar EU are

Alliance: Sinhara, Bleedem, Divastate

Horde: Sigorni

Do get in touch via forum or in game if you like. We are looking for more players from my timezone

My Tracert to your server:

Tracing route to 213-248-123-128.customer.teliacarrier.com [213.248.123.128]

over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1

2 33 ms 30 ms 39 ms 119.152.32.1

3 21 ms 21 ms 23 ms 203.99.170.190

4 21 ms 21 ms 20 ms rwp44.pie.net.pk [221.120.252.9]

5 40 ms 40 ms 41 ms static-khi275-P02-pie.net.pk [221.120.254.18]

6 40 ms 41 ms 40 ms static-khi-ni01-swb.pie.net.pk [202.125.128.142]

7 45 ms 44 ms 46 ms rwp44.pie.net.pk [221.120.250.229]

8 182 ms 177 ms 176 ms pos3-1-0.palermo7.pal.seabone.net [195.22.198.57]

9 172 ms 173 ms 175 ms telia.franco34.fra.seabone.net [89.221.34.162]

10 174 ms 173 ms 173 ms telia.franco34.fra.seabone.net [89.221.34.162]

11 167 ms 166 ms 168 ms ffm-bb1-link.telia.net [80.91.252.173]

12 193 ms 199 ms 194 ms s-bb1-link.telia.net [80.91.251.144]

13 192 ms 211 ms 191 ms s-b1-link.telia.net [80.91.249.71]

14 191 ms 191 ms 192 ms s-hdn-i3-link.telia.net [80.91.251.245]

15 * * * Request timed out.

16 * ^C

Try this:

http://dionadar.wordpress.com/2008/06/21/latency-goes-dooowwwnnn/

ALSO: Make characters on other servers e.g. Kilrogg etc - you have to test at least 5-6 different ones. Make sure you are in goldshire or some other place where there are no people, to get the lowest ping recording. Maybe PTCLs latency to YOUR wow server is stuffed. Try other servers and report here.

I am getting the same results to all of them.

BTW what city are you in, because I have tested this on two or three different connections from PTCL and getting the same result. and I am in Islamabad.

Lahore

Tracing route to 213-248-123-128.customer.teliacarrier.com [213.248.123.128]

over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1

2 171 ms 58 ms 45 ms 119.153.136.1

3 15 ms 13 ms 14 ms 203.99.170.22

4 14 ms 14 ms 14 ms rwp44.pie.net.pk [221.120.253.1]

5 35 ms 37 ms 34 ms static-khi275-P01-pie.net.pk [221.120.254.14]

6 35 ms 37 ms 36 ms static-khi-ni01-swb.pie.net.pk [202.125.128.142]

7 35 ms 34 ms 34 ms khi77.ptcl.net.pk [221.120.250.229]

8 135 ms 134 ms 133 ms pos3-1-0.palermo7.pal.seabone.net [195.22.198.57

]

9 164 ms 164 ms 163 ms telia.franco34.fra.seabone.net [89.221.34.166]

10 163 ms 164 ms 165 ms telia.franco34.fra.seabone.net [89.221.34.166]

11 164 ms 163 ms 163 ms ffm-bb2-link.telia.net [80.91.248.101]

12 192 ms 191 ms 192 ms s-bb2-link.telia.net [80.91.248.58]

13 190 ms 189 ms 190 ms s-b1-link.telia.net [80.91.246.151]

14 192 ms 189 ms 192 ms s-hdn-i3-link.telia.net [80.91.251.245]

15 * * ^C

its bit better on ptcl now.

I know its a stupid question.

How can I get my latency down again? I have tried everything else like Leatrix and Diondar etc. etc.

Would re-installing windows make any difference?

It wouldn't really make a difference. The main problem is that whenever you reboot your router you get a different gateway/dns assigned to you. I also began facing this problem during the end of april and found one of the most effective way to resolve this issue is to keep rebooting your router till you get a 203.99.XXX.X gateway/ip assigned to you (in your router configuration page). I understand that this method is pretty tiresome and im not really sure whether or not you can change your setting to always make sure you get this gateway but when pinging grim batol (the server that i play on), the tracert displays a 175ms on the 14th hop which results in about 200-300ms during a 25man raid where as teh 113.xxx.xxx.x gateways result in about 500-600ms.

Like i said earlier, you would have to reboot your router quite a few times but see if it works out for you :). I dont have alot of info to back up this theory as to why this is but i'm a huge wow fanatic and i've been playing it since the original wow began so this was the best solution that i discovered because all i do are 25man raids

Yes I am aware of that, I actually played like that for a month. After getting tired of the router restarting exercise I finally went out and got myself EDSL with Static IP hoping it would solve the problem.

So now I get a Static IP that is not blacklisted anywhere.

1 <1 ms <1 ms <1 ms 192.168.1.1

2 175 ms 48 ms 37 ms 203.99.180.1

3 112 ms 33 ms 29 ms 203.99.170.22

4 154 ms 51 ms 40 ms rwp44.pie.net.pk [221.120.253.1]

5 113 ms 80 ms 93 ms static-khi275-P01-pie.net.pk [221.120.254.14]

6 99 ms 105 ms * static-khidr-ni01-sw.pie.net.pk [202.125.128.161

]

7 53 ms 261 ms 98 ms rwp44.pie.net.pk [221.120.250.246]

8 205 ms 200 ms 151 ms pos12-1.palermo5.pal.seabone.net [195.22.198.101

]

9 268 ms 497 ms 307 ms xe-0-1-0.parigi52.par.seabone.net [213.144.183.7

7]

10 327 ms 617 ms 224 ms te2-3.ar1.cdg1.fr.nlayer.net [69.22.139.49]

11 195 ms 193 ms 197 ms xe-2-2-0.cr1.lhr1.uk.nlayer.net [69.22.142.65]

12 347 ms 331 ms 325 ms xe-7-2-0.cr1.nyc2.us.nlayer.net [69.22.142.62]

13 332 ms 367 ms 337 ms xe-3-2-0.cr2.ord1.us.nlayer.net [69.22.142.85]

14 380 ms 472 ms 334 ms as32748.ae1-133.cr2.ord1.us.nlayer.net [69.31.11

0.30]

15 451 ms 421 ms 547 ms ip31.208-100-1.static.steadfast.net [208.100.1.3

1]

Trace complete.

tracert infdat.com

Tracing route to infdat.com [208.100.1.31]

over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1

2 31 ms 28 ms 41 ms 203.99.180.1

3 30 ms 28 ms 23 ms 203.99.170.22

4 77 ms 80 ms 66 ms rwp44.pie.net.pk [221.120.253.1]

5 106 ms 120 ms 77 ms static-khi275-P01-pie.net.pk [221.120.254.14]

6 133 ms 134 ms 59 ms static-khidr-ni01-sw.pie.net.pk [202.125.128.161

]

7 155 ms 122 ms 56 ms rwp44.pie.net.pk [221.120.250.246]

8 149 ms 149 ms * pos12-1.palermo5.pal.seabone.net [195.22.198.101

]

9 * 215 ms 260 ms xe-0-1-0.parigi52.par.seabone.net [213.144.183.7

7]

10 471 ms 292 ms 592 ms te2-3.ar1.cdg1.fr.nlayer.net [69.22.139.49]

11 217 ms 206 ms 256 ms xe-2-2-0.cr1.lhr1.uk.nlayer.net [69.22.142.65]

12 319 ms 317 ms 434 ms xe-7-2-0.cr1.nyc2.us.nlayer.net [69.22.142.62]

13 328 ms 375 ms 372 ms xe-3-2-0.cr2.ord1.us.nlayer.net [69.22.142.85]

14 407 ms 412 ms 514 ms as32748.ae1-133.cr2.ord1.us.nlayer.net [69.31.11

0.30]

15 332 ms 458 ms 452 ms ip31.208-100-1.static.steadfast.net [208.100.1.3

1]

Trace complete.

tracert infdat.com

Tracing route to infdat.com [208.100.1.31]

over a maximum of 30 hops:

1 1 ms <1 ms 1 ms 192.168.1.1

2 425 ms 162 ms 44 ms 203.99.180.1

3 197 ms 30 ms 24 ms 203.99.170.22

4 167 ms 43 ms 25 ms rwp44.pie.net.pk [221.120.253.1]

5 148 ms 46 ms 47 ms static-khi275-P01-pie.net.pk [221.120.254.14]

6 147 ms 51 ms 51 ms static-khidr-ni01-sw.pie.net.pk [202.125.128.161

]

7 141 ms 56 ms 54 ms rwp44.pie.net.pk [221.120.250.246]

8 142 ms 153 ms 646 ms pos12-1.palermo5.pal.seabone.net [195.22.198.101

]

9 213 ms 623 ms 401 ms xe-0-1-0.parigi52.par.seabone.net [213.144.183.7

7]

10 594 ms 800 ms 401 ms te2-3.ar1.cdg1.fr.nlayer.net [69.22.139.49]

11 594 ms 197 ms 600 ms xe-2-2-0.cr1.lhr1.uk.nlayer.net [69.22.142.65]

12 800 ms 401 ms 788 ms xe-7-2-0.cr1.nyc2.us.nlayer.net [69.22.142.62]

13 326 ms 721 ms 334 ms xe-3-2-0.cr2.ord1.us.nlayer.net [69.22.142.85]

14 * 959 ms 789 ms as32748.ae1-133.cr2.ord1.us.nlayer.net [69.31.11

0.30]

15 326 ms 723 ms 335 ms ip31.208-100-1.static.steadfast.net [208.100.1.3

1]

Trace complete.

@fircruz.. whats wrong with ptcl now :(

Tracing route to 213-248-123-92.customer.teliacarrier.com [213.248.123.92]

over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1

2 50 ms 51 ms 49 ms 203.99.169.17

3 49 ms 49 ms 51 ms 116.71.251.205

4 50 ms 50 ms 50 ms static.lhr63.pie.net.pk [221.120.208.17]

5 49 ms 49 ms 56 ms 221.120.252.25

6 68 ms 69 ms 69 ms 221.120.254.18

7 70 ms 69 ms 70 ms static-khi-ni01-swa.pie.net.pk [202.125.128.162]

8 67 ms 69 ms 69 ms 221.120.250.229

9 210 ms 211 ms 211 ms pos3-1-0.palermo7.pal.seabone.net [195.22.198.57]

10 199 ms 195 ms 193 ms telia.franco34.fra.seabone.net [89.221.34.166]

11 194 ms 195 ms 195 ms telia.franco34.fra.seabone.net [89.221.34.166]

12 195 ms 196 ms 193 ms ffm-bb1-link.telia.net [80.91.247.166]

13 221 ms 221 ms 222 ms s-bb1-link.telia.net [80.239.147.173]

14 221 ms 221 ms 223 ms s-b1-link.telia.net [80.91.249.71]

15 222 ms 219 ms 221 ms s-hdn-i3-link.telia.net [80.91.249.69]

^C

pings are reasonable nw :o