Packet Loss

I switched my WA account over to Verizon last night and everything was normal again (well 700ms compared to 7k) Didn't bother switching back but will check to night if SAIX is still doing it
 
Is SAOL Verizon too? Some of our guildies are using SAOL and they don't seem to be having any problems. It seems like its a SAIX thing? What I found most bizarre was when idling latency is hovering around 400ms, as soon as you run around shatt, fight some mobs or go to BG's it jumps to 1-7k ms at times.
 
Last edited:
I seem to be having this problem again. Here's yet ANOTHER ping-transcript:

Ping statistics for 64.233.167.99:
Packets: Sent = 157, Received = 105, Lost = 52 (33% loss),
Approximate round trip times in milli-seconds:
Minimum = 345ms, Maximum = 818ms, Average = 373ms

... poor Google's going to ban me for ICMP-spamming.

Kalvaer - did you buy Verizon bandwidth from Web Africa? Perhaps I should investigate that...
 
I use a Webafrica unshaped account and it allows you to use SAIX or Verizon. You basically change your log in name by adding a .s at the end for SAIX, and a .v for verizon.

I'll be home in about and hour and I'll check all my accounts and see whats up (ie: IS, SAIX, and Verizon)
 
i have this error as well getting 1-5% packet loss and its REALLY REALLY annoying and this is local. Tested with my unshaped account and i get 1-5% packet loss ad well, only difference is that ive been getting this since 13 February.


.
 
I logged a call with Telkom and got a reference number. I suggest everyone does that so that Telkom will acknowledge that there is a fault.
 
Typical, for now everything is ok again. Weekends also do seem better most times for me than weekdays. Its still not the same as the 300 ms pings from a few months ago, but 700ms is much more playable than 7k ms. I will try test tonight again. At this time of day most people aren't online but in traffic going home or sitting in a pub so expected better results than peak, but not this :confused:

Eye of the Storm BG on thunderlord US:
fighting groups at the flag

WA unshaped - Verizon: 670 ms ping
WA unshaped - SAIX: 530ms ping
OWeb shaped - IS fibre: 640 ms ping

Whats really pathetic though is that the shaped account is pretty damn close to the unshaped that I'm paying double for. The pings are the same, Shaped OW currently has a quicker response time than SAIX or Verizon

Now for the pings

Openweb shaped - IS fiber:
Pinging www.l.google.com [72.14.205.103] with 32 bytes of data:

Reply from 72.14.205.103: bytes=32 time=286ms TTL=238
Reply from 72.14.205.103: bytes=32 time=285ms TTL=238
Reply from 72.14.205.103: bytes=32 time=283ms TTL=238
Reply from 72.14.205.103: bytes=32 time=280ms TTL=238

Ping statistics for 72.14.205.103:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 280ms, Maximum = 286ms, Average = 283ms
Click to expand...
WA unshaped - SAIX:
Pinging www.l.google.com [72.14.205.103] with 32 bytes of data:

Reply from 72.14.205.103: bytes=32 time=289ms TTL=242
Reply from 72.14.205.103: bytes=32 time=294ms TTL=242
Reply from 72.14.205.103: bytes=32 time=291ms TTL=242
Reply from 72.14.205.103: bytes=32 time=292ms TTL=242

Ping statistics for 72.14.205.103:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 289ms, Maximum = 294ms, Average = 291ms
Click to expand...
WA unshaped - Verizon
Pinging www.l.google.com [72.14.205.99] with 32 bytes of data:

Reply from 72.14.205.99: bytes=32 time=307ms TTL=236
Reply from 72.14.205.99: bytes=32 time=277ms TTL=236
Reply from 72.14.205.99: bytes=32 time=308ms TTL=236
Reply from 72.14.205.99: bytes=32 time=306ms TTL=236

Ping statistics for 72.14.205.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 277ms, Maximum = 308ms, Average = 299ms
Click to expand...
 
Tracerts are also ok as of today.. Will also test later tonight:

Openweb:
Tracing route to 206.16.23.6 over a maximum of 30 hops
1 * * * Request timed out.
2 12 ms 11 ms X.X.X.X
3 12 ms 13 ms 13 ms cdsl1-rba-vl2257.ip.isnet.net [196.38.73.237]
4 12 ms 13 ms 12 ms css2-rba-gi0-1.ip.isnet.net [196.26.0.14]
5 44 ms 13 ms 11 ms core2b-rba-7600-gi1-0-5.ip.isnet.net [196.26.0.182]
6 262 ms 261 ms 262 ms 168.209.161.232
7 276 ms 276 ms 270 ms 168.209.160.213
8 267 ms 269 ms 264 ms core2a-ny-gi1-0-19-20.ip.isnet.net [168.209.163.41]
9 262 ms 261 ms 262 ms core1b-ny-gi0-0-2.ip.isnet.net [168.209.244.3]
10 262 ms 260 ms 260 ms 12.86.139.193
11 305 ms 306 ms 302 ms tbr2.n54ny.ip.att.net [12.122.105.82]
12 299 ms 301 ms 300 ms cr2.n54ny.ip.att.net [12.122.16.205]
13 303 ms 306 ms 302 ms cr2.wswdc.ip.att.net [12.122.3.38]
14 303 ms 312 ms 310 ms tbr1.wswdc.ip.att.net [12.122.16.30]
15 308 ms * 309 ms tbr1.sl9mo.ip.att.net [12.122.10.30]
16 303 ms 302 ms 300 ms tbr2.dlstx.ip.att.net [12.122.10.90]
17 312 ms 311 ms 311 ms br2.dlstx.ip.att.net [12.123.16.213]
18 302 ms 304 ms 306 ms mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255.78]
19 304 ms 303 ms 309 ms mdf002fbi8ks0001-eth-1-2.dal1.attens.net [63.241.192.62]


WA SAIX
Tracing route to 206.16.23.6 over a maximum of 30 hops
1 12 ms 11 ms 11 ms X.X.X.X
2 * * * Request timed out.
3 * * * Request timed out.
4 15 ms 14 ms 13 ms 196.43.33.2
5 12 ms 14 ms 13 ms 196.43.33.5
6 261 ms 261 ms 260 ms ash-ip-dir-equinix-pos-4-1.telkom-ipnet.co.za [196.43.18.34]
7 275 ms 276 ms 275 ms 12.117.208.5
8 304 ms 306 ms 305 ms tbr1.wswdc.ip.att.net [12.122.80.194]
9 306 ms 305 ms 304 ms tbr1.sl9mo.ip.att.net [12.122.10.30]
10 306 ms 303 ms 304 ms tbr2.dlstx.ip.att.net [12.122.10.90]
11 304 ms 301 ms 302 ms br2.dlstx.ip.att.net [12.123.16.213]
12 303 ms 303 ms 304 ms mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255.78]
13 479 ms 304 ms 301 ms mdf002fbi8ks0001-eth-1-4.dal1.attens.net [63.241.192.126]

WA Verizon
Tracing route to 206.16.23.6 over a maximum of 30 hops
1 11 ms 12 ms 11 ms X.X.X.X
2 13 ms 14 ms 13 ms atm4-0-0sub106.gw11.jnb6.alter.net [196.7.196.21]
3 15 ms 14 ms 15 ms pos8-1-0.gw11.jnb6.alter.net [196.30.121.157]
4 15 ms 13 ms 16 ms fe4-1-0.cr2.jnb6.alter.net [196.30.156.34]
5 198 ms 198 ms 198 ms other-side.s0-1-0.cr2.jnb6.alter.net [196.30.229.245]
6 200 ms 230 ms 200 ms so0-0-0.ir1.par6.alter.net [196.30.229.109]
7 270 ms 267 ms 270 ms 0.so-3-1-0.IH1.NYC1.ALTER.NET [152.63.16.109]
8 291 ms 294 ms 297 ms 500.at-6-3-0.XR1.NYC1.ALTER.NET [152.63.19.90]
9 297 ms 296 ms 295 ms 0.so-1-1-0.XL1.NYC1.ALTER.NET [152.63.19.86]
10 295 ms 386 ms 297 ms 0.so-6-1-1.XL3.NYC4.ALTER.NET [152.63.21.22]
11 270 ms 269 ms 268 ms 0.ge-6-1-0.BR3.NYC4.ALTER.NET [152.63.3.166]
12 268 ms 268 ms 268 ms 192.205.34.49
13 331 ms 332 ms 333 ms tbr2.n54ny.ip.att.net [12.122.105.74]
14 309 ms 305 ms 308 ms cr2.n54ny.ip.att.net [12.122.16.221]
15 336 ms 337 ms 334 ms cr2.wswdc.ip.att.net [12.122.3.38]
16 311 ms 314 ms 311 ms tbr1.wswdc.ip.att.net [12.122.16.54]
17 337 ms 341 ms 340 ms tbr1.sl9mo.ip.att.net [12.122.10.30]
18 313 ms 312 ms 315 ms tbr2.dlstx.ip.att.net [12.122.10.90]
19 341 ms 337 ms 336 ms br2.dlstx.ip.att.net [12.123.16.213]
20 339 ms 337 ms 344 ms mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255.78]
21 338 ms 338 ms 337 ms mdf002fbi8ks0002-eth-2-2.dal1.attens.net [63.241.192.118]
 
Thanks for the info. For me I was still experiencing packet loss this weekend, but not as bad as it was before.

Also, AFAIK, ICMP don't get shaped which is why your ping for shaped & unshaped are the same.
 
Playing was also great though. Ended up having a hectic weekend and only got to play for an hour yesterday. I forgot to switch accounts to the unshaped, and only realised after 3 BG's that I was sitting on 430 ms with no lag....
 
Any 1 still getting bad ping in wow and packet loss......cause mine is screwed :(
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X