I'm doing some tests.
For those of you getting more than 1000s ping and spikes:

1) 512/1MB
2) What IP?
3) Tracert to us.logon.worldofwarcraft.com

getting bad now , latency bouncing around 900 to 4000ms.
gonna back to dial-up.

1mb
218/60, cant seem to get to 219
damansara utama area
ip bouncing up and down between 1000-1500 with LOTS of spikes, tracert 312 ms with a few packet losses. this fuKing sux, how is it that im still lagging and a friend who lives a few rows from my house gets a 600 ping ingame with no spikes =( someone please help me =(

can a WoW JWBB user join here?

hehe yeah i always wanted to know what kinda latency you get playing wow using JWBB.. pls provide some info
lag and such

ip 60, nice ping. around 300-600. back to normal

for real ?
Current IP Address: 60.48.84.90

which area you in ?
im still getting 1300-2k

219.95.x.x. Average latency is about 800ms-1100ms. Lag spikes about once every 3-8 iminutes. Response feels like a 400-600ms except during sporadic spikes.

Very playable if you're a warlock, good if you're a hunter or shaman, decent for warriors/rogues, horrible if your class requires clicks to attack (i.e. mages).

Tracing route to us.logon.worldofwarcraft.com [12.129.232.112]
over a maximum of 30 hops:

1 * * * Request timed out.
2 21 ms 20 ms 21 ms 219.93.218.177
3 38 ms 20 ms 20 ms 219.93.216.109
4 19 ms 19 ms 20 ms 219.93.155.33
5 19 ms 19 ms 19 ms 210.187.133.83
6 20 ms 19 ms 20 ms 219.93.174.83
7 312 ms 312 ms 313 ms 219.93.153.158
8 383 ms 382 ms * 12.118.44.5
9 382 ms * 387 ms 12.123.8.50
10 386 ms 381 ms 385 ms tbr1-cl4.sl9mo.ip.att.net [12.122.10.30]
11 376 ms 375 ms 379 ms tbr1-cl2.sffca.ip.att.net [12.122.10.42]
12 376 ms 379 ms 371 ms gbr6-p100.sffca.ip.att.net [12.122.11.78]
13 378 ms 375 ms 375 ms gar3-p370.sffca.ip.att.net [12.123.13.161]
14 396 ms 394 ms 396 ms mdf1-gsr12-2-pos-7-0.lax1.attens.net [12.122.255
.254]
15 387 ms 390 ms * mdf1-bi8k-2-eth-1-3.lax1.attens.net [12.129.192.
110]
16 * * * Request timed out.

The ping for me is very bumpy. It can go as low as 500 and 3 minutes later it can shoot up to 1.3k, and repeat that sequence around every 3 minutes. Add in a few lag spikes every now and then too. The funny thing is, my friend thats staying oposite of my house, was having 219.95 since ancient times till now, and he never has any connection problem, having a ping at 400-800 all the time. With the exception of few days ago ofcourse.

60.48.xxx.xxx

Johor, Skudai

yes... the ping is really good for me

219.93.xx.xx, 512 package

Kota Bharu, Kelantan

Ping is around 500-600, makes me happy enough so no complains here

Using 219.95.xxx

There are some packet losses to WoW. But it's fine for EQ2. The old problem we faced before with the 1k ping is reduced to 400s. So, we're back to our original problem (of this thread) but there are slight improvements.

The best connection I "feel" is the 218.111.xxx only. The ping is slightly the same, but it's stable with no packet loss. If you can't get 218.111.xxx, log in during the day between lunch time up to 10PM. Past midnight, you'll be served with 219 only. I couldn't test 60 because the leasing is geographically influenced.

Tracing route to us.logon.worldofwarcraft.com [12.129.232.111]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 23 ms 23 ms 24 ms 219.93.218.177
3 19 ms 19 ms 20 ms 219.93.216.117
4 21 ms 20 ms 21 ms 219.93.155.37
5 20 ms 20 ms 21 ms 210.187.133.83
6 21 ms 20 ms 21 ms 219.93.174.83
7 315 ms 313 ms 312 ms 219.93.153.158
8 * 392 ms 390 ms 12.118.44.5
9 383 ms 384 ms 383 ms 12.123.8.50
10 382 ms 379 ms 383 ms tbr1-cl4.sl9mo.ip.att.net [12.122.10.30]
11 375 ms 373 ms 375 ms tbr1-cl2.sffca.ip.att.net [12.122.10.42]
12 382 ms 379 ms 383 ms gbr6-p100.sffca.ip.att.net [12.122.11.78]
13 366 ms 369 ms 372 ms gar3-p370.sffca.ip.att.net [12.123.13.161]
14 382 ms 379 ms 380 ms mdf1-gsr12-2-pos-7-0.lax1.attens.net [12.122.255
.254]
15 394 ms 388 ms 392 ms mdf1-bi8k-2-eth-1-3.lax1.attens.net [12.129.192.
110]
16 ^C

Tracing route to ableq2-08-01.everquest2.com [199.108.203.33]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 22 ms 23 ms 23 ms 219.93.218.177
3 19 ms 20 ms 20 ms 219.93.216.117
4 20 ms 21 ms 22 ms 219.93.155.29
5 20 ms 21 ms 21 ms brf-odsy02-srp1-0.tm.net.my [210.187.135.2]
6 21 ms 21 ms 21 ms 210.187.142.1
7 21 ms 21 ms 21 ms vlan150-brf-sw04.tm.net.my [219.93.175.115]
8 22 ms 22 ms 21 ms 210.187.129.171
9 251 ms 251 ms 252 ms 219.93.168.234
10 252 ms 253 ms 252 ms exch1.laeqnx-1.sonyonline.net [206.223.123.90]
11 315 ms 314 ms 315 ms vl892.asheqnx-1.sonyonline.net [64.37.128.82]
12 316 ms 315 ms 315 ms vl46.ashaens-1.sonyonline.net [64.37.144.177]
13 314 ms 315 ms 314 ms ableq2-08-01.everquest2.com [199.108.203.33]

Trace complete.


Using 218.111.xxx

Tracing route to us.logon.worldofwarcraft.com [12.129.232.110]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 23 ms 27 ms 25 ms 219.93.218.177
3 22 ms 20 ms 20 ms 219.93.216.125
4 21 ms 20 ms 21 ms 219.93.155.41
5 21 ms 21 ms 20 ms 210.187.133.83
6 20 ms 21 ms 20 ms 219.93.174.83
7 314 ms 313 ms 312 ms 219.93.153.158
8 361 ms 352 ms 350 ms 12.118.44.5
9 356 ms 358 ms 352 ms 12.123.8.50
10 355 ms 355 ms 351 ms tbr1-cl4.sl9mo.ip.att.net [12.122.10.30]
11 347 ms 347 ms 354 ms tbr1-cl2.sffca.ip.att.net [12.122.10.42]
12 354 ms 351 ms 345 ms gbr6-p100.sffca.ip.att.net [12.122.11.78]
13 344 ms 344 ms 348 ms gar3-p370.sffca.ip.att.net [12.123.13.161]
14 353 ms 347 ms 343 ms mdf1-gsr12-2-pos-7-0.lax1.attens.net [12.122.255
.254]
15 351 ms 346 ms 348 ms mdf1-bi8k-2-eth-1-2.lax1.attens.net [12.129.192.
46]
16 ^C

This post has been edited by Owen: Apr 11 2005, 06:56 AM

Edit: double post

This post has been edited by Owen: Apr 11 2005, 06:41 AM

bash-2.05b$ traceroute us.logon.worldofwarcraft.com
traceroute to us.logon.worldofwarcraft.com (12.129.232.112), 64 hops max, 44 byte packets
1 219.93.218.177 (219.93.218.177) 20.118 ms 22.346 ms 27.619 ms
2 219.93.216.101 (219.93.216.101) 19.624 ms 19.449 ms 18.719 ms
3 219.93.155.29 (219.93.155.29) 19.569 ms 19.296 ms 19.390 ms
4 210.187.133.83 (210.187.133.83) 20.003 ms 19.258 ms 19.518 ms
5 219.93.174.83 (219.93.174.83) 20.512 ms 20.121 ms 20.261 ms
6 219.93.153.158 (219.93.153.158) 212.531 ms 212.195 ms 212.207 ms
7 12.118.44.5 (12.118.44.5) 292.419 ms 288.090 ms 282.462 ms
8 * 12.123.8.50 (12.123.8.50) 280.367 ms 282.751 ms
9 tbr1-cl4.sl9mo.ip.att.net (12.122.10.30) 283.458 ms 285.456 ms 280.641 ms
10 tbr1-cl2.sffca.ip.att.net (12.122.10.42) 275.570 ms 275.612 ms 270.997 ms
11 gbr6-p100.sffca.ip.att.net (12.122.11.78) 267.238 ms 271.666 ms 271.836 ms
12 gar3-p370.sffca.ip.att.net (12.123.13.161) 271.257 ms 270.746 ms 269.383 ms
13 mdf1-gsr12-2-pos-7-0.lax1.attens.net (12.122.255.254) 276.198 ms 274.153 ms 278.285 ms
14 mdf1-bi8k-1-eth-2-3.lax1.attens.net (12.129.192.126) 268.740 ms 267.576 ms 271.674 ms
15 * * *
16 * *^C


Best of all

[myr0n@eleanor myr0n]$ traceroute us.logon.worldofwarcraft.com
traceroute to us.logon.worldofwarcraft.com (12.129.232.114), 64 hops max, 44 byte packets
1 Fe0-0-1.gw03.glsfb.time.net.my (203.121.16.29) 0.946 ms 0.485 ms 0.410 ms
2 Fe0-0-1.gw03.glsfb.time.net.my (203.121.16.29) 0.533 ms 0.582 ms 0.523 ms
3 203.121.16.53 (203.121.16.53) 36.042 ms 35.832 ms 35.834 ms
4 203.222.180.73 (203.222.180.73) 40.155 ms 40.712 ms 40.107 ms
5 sl-bb21-hk-15-3.sprintlink.net (203.222.38.55) 40.045 ms 40.822 ms 39.677 ms
6 sl-bb21-tok-15-1.sprintlink.net (203.222.33.7) 91.266 ms 91.171 ms 91.987 ms
7 sl-bb21-sea-8-2.sprintlink.net (144.232.20.50) 188.796 ms 188.755 ms 187.927 ms
8 * * *
9 12.123.44.178 (12.123.44.178) 195.547 ms 195.139 ms 197.042 ms
10 tbr2-cl1.sffca.ip.att.net (12.122.12.113) 195.346 ms 195.072 ms 195.069 ms
11 gbr5-p20.sffca.ip.att.net (12.122.11.90) 195.166 ms 194.673 ms 194.582 ms
12 gar3-p360.sffca.ip.att.net (12.123.13.157) 194.665 ms 194.449 ms 195.009 ms
13 mdf1-gsr12-2-pos-7-0.lax1.attens.net (12.122.255.254) 203.410 ms 203.646 ms 203.387 ms
14 mdf1-bi8k-1-eth-2-3.lax1.attens.net (12.129.192.126) 202.904 ms 202.142 ms 202.103 ms

This post has been edited by Utada: Apr 11 2005, 07:28 AM

Just want to know hows the 1mb line doing. Considering of upgrading, but not sure whether it will make any difference. I can only get 219 ip for my 512 line. Will i get other ips if I subscribe for a 1mb?

Ping is from 400-1.5k last night with occasional lag spikes.

not sure upgrade can improve connection to wow, i doubt there is a difference unless u play wow while dowloading torrent file (use netlimiter please).

218.111 got lots spike + better connection,
219.95 bad bad conection 1K~infinite
60.* godd connection, sometime only spike, average 700~800

can 512kb users get 218 and 60 ip? because i can never get them. Or issit depending on loc?

i think no difference in ip assign between 512k and 1Mb. Anyway, place maybe a factor, since I have 1 guild member can't get 219 at all. Weird huh... we all crying for 218 and 60, and this guy never get anything other than 218 and 60.

edit: and I usually can get 219.94, and 218 if only before 7-8 pm. never see 60

This post has been edited by keylink: Apr 11 2005, 12:44 PM

i'm on 219.95 atm and its ok with ocasional lag spikes every few minutes. its much more playable than last week thats for sure, but still irritating.

hmm... our friends from Broadband reports seems to imply that everything is back to normal....
Broadband Reports

This post has been edited by LoStBoYz: Apr 11 2005, 02:40 PM