That definitely not good. Can you also run the full trace when this happens so we can see where the latency occurs?
Yep, Lag spikes is still sporadic tried some Diablo III last night between 6:30 and 9 pm, with latencey running between ~200 and ~700 ..... definitely not ideal when one gets ganked by mobs on a glass canon Witch Doctor
5:30 am this morning - the latency spikes still present :wtf:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Igor III>ping bras.afrihost.com -t
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=603ms TTL=63
Reply from 155.239.255.250: bytes=32 time=573ms TTL=63
Reply from 155.239.255.250: bytes=32 time=716ms TTL=63
Reply from 155.239.255.250: bytes=32 time=639ms TTL=63
Reply from 155.239.255.250: bytes=32 time=649ms TTL=63
Reply from 155.239.255.250: bytes=32 time=583ms TTL=63
Reply from 155.239.255.250: bytes=32 time=515ms TTL=63
Reply from 155.239.255.250: bytes=32 time=722ms TTL=63
Reply from 155.239.255.250: bytes=32 time=660ms TTL=63
Reply from 155.239.255.250: bytes=32 time=614ms TTL=63
Reply from 155.239.255.250: bytes=32 time=669ms TTL=63
Reply from 155.239.255.250: bytes=32 time=566ms TTL=63
Reply from 155.239.255.250: bytes=32 time=648ms TTL=63
Reply from 155.239.255.250: bytes=32 time=690ms TTL=63
Reply from 155.239.255.250: bytes=32 time=643ms TTL=63
Reply from 155.239.255.250: bytes=32 time=672ms TTL=63
Reply from 155.239.255.250: bytes=32 time=636ms TTL=63
Reply from 155.239.255.250: bytes=32 time=684ms TTL=63
Reply from 155.239.255.250: bytes=32 time=621ms TTL=63
Reply from 155.239.255.250: bytes=32 time=571ms TTL=63
Reply from 155.239.255.250: bytes=32 time=640ms TTL=63
Reply from 155.239.255.250: bytes=32 time=617ms TTL=63
Reply from 155.239.255.250: bytes=32 time=682ms TTL=63
Reply from 155.239.255.250: bytes=32 time=121ms TTL=63
Reply from 155.239.255.250: bytes=32 time=149ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=15ms TTL=63
Reply from 155.239.255.250: bytes=32 time=20ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=62ms TTL=63
Reply from 155.239.255.250: bytes=32 time=28ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=27ms TTL=63
Reply from 155.239.255.250: bytes=32 time=19ms TTL=63
Reply from 155.239.255.250: bytes=32 time=15ms TTL=63
Reply from 155.239.255.250: bytes=32 time=45ms TTL=63
Reply from 155.239.255.250: bytes=32 time=18ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=54ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=28ms TTL=63
Reply from 155.239.255.250: bytes=32 time=15ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=19ms TTL=63
Reply from 155.239.255.250: bytes=32 time=27ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=78ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=35ms TTL=63
Reply from 155.239.255.250: bytes=32 time=36ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=15ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=48ms TTL=63
Reply from 155.239.255.250: bytes=32 time=38ms TTL=63
Reply from 155.239.255.250: bytes=32 time=29ms TTL=63
Reply from 155.239.255.250: bytes=32 time=37ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=19ms TTL=63
Reply from 155.239.255.250: bytes=32 time=19ms TTL=63
Reply from 155.239.255.250: bytes=32 time=30ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Ping statistics for 155.239.255.250:
Packets: Sent = 70, Received = 70, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 722ms, Average = 227ms
Control-C
^C
C:\Users\Igor III>tracert bras.afrihost.com
Tracing route to bras.afrihost.com [155.239.255.250]
over a maximum of 30 hops:
1 <1 ms <1 ms 10 ms 192.168.1.1
2 15 ms 26 ms 19 ms 155.239.255.250
Trace complete.
C:\Users\Igor III>tracert telkom.co.za
Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:
1 <1 ms 19 ms 5 ms 192.168.1.1
2 * * * Request timed out.
3 17 ms 13 ms 16 ms jhb-up3.net.afrihost.co.za [169.1.5.29]
4 59 ms 17 ms 13 ms jhb-in1.net.afrihost.co.za [169.1.5.42]
5 59 ms 33 ms 12 ms jhb-net1.net.afrihost.co.za [169.1.5.52]
6 88 ms 13 ms 24 ms 41.169.57.216
7 20 ms 19 ms 36 ms 41.160.2.69
8 16 ms 14 ms 25 ms rrba-ip-lir-1-gig-0-0-0-102.telkom-ipnet.co.za [
196.43.25.137]
9 25 ms 39 ms 24 ms 196.43.39.166
10 65 ms 41 ms 19 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
11 80 ms 40 ms 17 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.30]
12 72 ms 22 ms 20 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43
.22.222]
Trace complete.
C:\Users\Igor III>tracert bras.afrihost.com
Tracing route to bras.afrihost.com [155.239.255.250]
over a maximum of 30 hops:
1 3 ms 5 ms <1 ms 192.168.1.1
2 13 ms 23 ms 11 ms 155.239.255.250
Trace complete.
C:\Users\Igor III>tracert telkom.co.za
Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:
1 <1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 39 ms 15 ms 15 ms jhb-up3.net.afrihost.co.za [169.1.5.29]
4 19 ms 22 ms 22 ms jhb-in1.net.afrihost.co.za [169.1.5.42]
5 19 ms 13 ms 12 ms jhb-net1.net.afrihost.co.za [169.1.5.52]
6 13 ms 37 ms 39 ms 41.169.57.216
7 55 ms 38 ms 25 ms 41.160.2.69
8 15 ms 14 ms 13 ms rrba-ip-lir-1-gig-0-0-0-102.telkom-ipnet.co.za [
196.43.25.137]
9 40 ms 18 ms 13 ms 196.43.39.166
10 27 ms 25 ms 16 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
11 36 ms 27 ms 18 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.30]
12 28 ms 22 ms 33 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43
.22.222]
Trace complete.
Don't want to sound full of cr@p, but ............. with the 23rd getting closer and with the "miracle" network still being in "test phase" I am not sure if my disappointment with the "latency" experienced on my Afrihost account is premature and if I should stick it out for another month (reminds me of the classic song from The Clash - Should I stay or should I go

)