WoW latency

Sooo monday morning and still rubbish latency. Thought everything would be restored by sunday?:confused::cry:
 
The following notice has been UPDATED.

TIME: 7 Feb 2010 1:38:15 PM
ADDITIONAL: Please note that power reconfiguration maintenance on SAT3 that was supposed to take place on Saturday 6 February 2010 (0:01 to 04:00
UTC) has been postponed.

Telkom has advised that power reconfiguration was unsuccessful.

Telkom will confirm a new maintenance date tomorrow afternoon after consultation with SAT3 devices product specialists, Alcatel.
 
Oh ffs.... all that info and what probably happened was they had an extended lunch.
 
i love crying ****hes loosing against superior teams HAHAHA -- look we play at 800ms lag sure we suck the big one but we lol at times when we do win with smart positioning -- i see poor lagg as a training xperience tbh - we got a 4 meg line now that shud give us around 400ms on a good day (we share connection) shadow priest+ele sham seem to have other teams guessing on our tacts (lotsa cc) - so we capalitize on the odd setup - i bet we get boned with better teams but we bottomfeed so its all fun atm ^^

play for fun or die while NERDRAGINGEMOQUIT s**t we are in africa players in EU will always kop their better
 
Telkom report that the non-impact work that was scheduled for this
morning (11/2/10) was fortunately a success.

The planned SAT3 traffic normalisation is still scheduled for Friday
morning, 12 February 2010 @ 02h00 - 16h30.

It is hoped that the normalisation will be completed within the first 6
hours of the scheduled change window tomorrow. The normalisation steps
will cause brief patching breaks to restorable traffic, which is deemed
to have little to no affect on customer services.
 
From what I can tell it should be all back to good on both IS and MTN-Business/Verizon/UUnet looking at my tests from Europe.

Internet Solutions:
be ~ # traceroute www.islabs.co.za
traceroute to www.islabs.co.za (196.34.133.186), 30 hops max, 40 byte packets
1 rt-gs01-v53.xl-is.net (79.170.90.2) 0.441 ms 0.409 ms 0.416 ms
2 xl-internetservices.nl.jointtransit.nl (217.170.10.139) 0.988 ms 1.229 ms 0.941 ms
3 r22.amstnl02.nl.bb.gin.ntt.net (195.69.144.36) 3.384 ms 3.365 ms 3.343 ms
4 p64-2-0-0.r23.londen03.uk.bb.gin.ntt.net (129.250.4.104) 10.915 ms 10.895 ms 11.193 ms
5 po-1.r00.londen03.uk.bb.gin.ntt.net (129.250.4.134) 11.499 ms 11.147 ms 11.448 ms
6 dimensiondata-0.r00.londen03.uk.bb.gin.ntt.net (83.231.181.234) 10.430 ms 10.040 ms 10.420 ms
7 core2a-dock-te2-2.ip.isnet.net (168.209.246.68) 10.380 ms 10.375 ms 10.352 ms
8 168.209.164.57 (168.209.164.57) 207.548 ms 207.999 ms 207.079 ms
9 mi-za-rba-p6-po5-1-2.ip.isnet.net (168.209.163.2) 207.355 ms 207.534 ms 207.327 ms
10 168.209.164.12 (168.209.164.12) 205.312 ms 206.173 ms 205.688 ms
11 core5a-rba-gi0-0-0.ip.isnet.net (196.26.0.42) 207.026 ms 206.995 ms 206.977 ms
12 core1a-bry-gi0-0-1-215.ip.isnet.net (168.209.0.98) 207.895 ms 208.216 ms 208.195 ms
13 csw1-b-jup-bry-gi3-1.ip.isnet.net (168.209.217.21) 208.500 ms 208.542 ms 208.575 ms
14 196.34.133.186 (196.34.133.186) 212.213 ms 212.307 ms 212.278 ms


MTN-Business/Verizon
be ~ # traceroute myadsl.co.za
traceroute to myadsl.co.za (41.203.21.136), 30 hops max, 40 byte packets
1 rt-gs01-v53.xl-is.net (79.170.90.2) 0.624 ms 0.582 ms 0.559 ms
2 xl-internetservices.nl.jointtransit.nl (217.170.10.139) 12.154 ms 12.134 ms 8.078 ms
3 am-tpr-1-nl.mtnns.net (195.69.144.31) 1.441 ms 1.389 ms 1.397 ms
4 am-cr-1.nl--am-tpr-1.nl-a.mtn.net (209.212.111.140) 1.726 ms 1.692 ms 1.680 ms
5 jp-cr-1.za--mtnh-cr-1.cm-a.mtnns.net (196.44.31.214) 187.694 ms 187.663 ms 187.628 ms
6 196.44.31.99 (196.44.31.99) 187.247 ms 186.938 ms 186.884 ms
7 ge11-0-0.gw2.jnb6.za.mtnbusiness.net (196.30.1.22) 202.200 ms 196.30.1.21 (196.30.1.21) 185.187 ms 185.181 ms
8 vlan9.hr3.jnb6.za.mtnbusiness.net (196.30.156.136) 186.789 ms 185.146 ms 185.114 ms
9 196.30.213.108 (196.30.213.108) 202.052 ms 201.379 ms 201.700 ms
10 firewall1.jnb2.host-h.net (196.7.216.173) 187.072 ms 185.148 ms 185.383 ms
11 mybroadband.co.za (41.203.21.136) 202.471 ms 202.462 ms 202.908 ms
 
My average ping via Afrihost is 650-800ms ... I remember there was some registry edit I did back on XP long ago to bring it down to about 350, just no idea how to fix it for Win7.
 
Voicy said:
I remember there was some registry edit I did back on XP long ago to bring it down to about 350, just no idea how to fix it for Win7.

http://forums.webafrica.co.za/showthread.php?t=2688-3&highlight=leatrix

Second post has a link to an addon which you can download to do the Leatrix Latency fix for you instead of editing the registry yourself. Be sure to run it while connected to the internet account you will be using to connect to WoW.

I guess PvE'rs know best how to reduce latency :P
 
What's with that fancy name? Isn't it just the normal TcpAck registry fix?
 
Reporting latency of 380ms to Scarshield Legion on Afrihost package last night ... so .. back to normal, but not better.

I also noticed an improvement in pings to SSL via Afrihost last night...
 
I just wish Blizzard would fix whatever is causing the high latency issues lately. I have only experienced it in WG but it's annoying. Getting steamrolled in WG because your entire side is laggin is not fun.
 
Top
Sign up to the MyBroadband newsletter
X