Screamer WiMax

had a small issue last night. today seems a lot better.
but will see when it gets into wow prime time later this evening.
 
What I heard from others and seen is that when it happens hops to international stop 196.15.204.81 TELKOM SA LTD.SOEKOR BUILDING151 FRANS CONRADIE AVEPAROWWESTERN CAPE or something similar, but definitely stops to Telkom Saix, so this looks like an upstream problem or Screamer having problems to them.
 
cda said:
upstream dropping every 2 minutes..
Click to expand...

SAIX issue perhaps? or Screamer's connection to SAIX?

1 <1 ms <1 ms <1 ms 192.168.2.1
2 39 ms 42 ms 39 ms 10.0.64.253
3 53 ms 49 ms 49 ms 172.11.11.1
4 49 ms 49 ms 54 ms 10.254.253.254
5 58 ms 49 ms 49 ms 172.17.0.1
6 51 ms 44 ms 44 ms 172.17.0.3
7 58 ms 49 ms 56 ms 196.15.204.81
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.


Hop 7/8 is the link to SAIX.

Think I will just watch some TV instead - this is ridiculous.
 
Last edited:
and they don't answer their phones.

For that extra professional service, go to Screamer.. lolz

Has "howzit" come out of hiding yet?
 
And it was close to 0% at 11pm.

There is definitely a correlation between time of use and packet loss.

The only reasons that come to mind are:
  • Less contention; or
  • Less interference.
 
My current statistics when pining Google -

Ping statistics for 209.85.227.106:
Packets: Sent = 1140, Received = 1014, Lost = 126 (11% loss),
Approximate round trip times in milli-seconds:
Minimum = 212ms, Maximum = 258ms, Average = 222ms

Neotel issues have not been resolved!
 
Had a chat to some of the technical staff awhile ago - they have confirmed that Neotel are still working on the problem as we speak ... err write.
 
coffee ~ # traceroute google.fr
traceroute to google.fr (209.85.229.104), 30 hops max, 40 byte packets
1 10.0.64.253 (10.0.64.253) 37.112 ms 46.625 ms 51.725 ms
2 172.11.11.1 (172.11.11.1) 56.668 ms 56.714 ms 56.752 ms
3 10.254.253.254 (10.254.253.254) 61.449 ms 61.493 ms 61.525 ms
4 172.17.0.1 (172.17.0.1) 61.636 ms 61.676 ms 61.710 ms
5 172.17.0.3 (172.17.0.3) 66.314 ms 66.357 ms 66.394 ms
6 196.15.204.81 (196.15.204.81) 66.511 ms 44.426 ms 38.583 ms
7 tpr-ip-esr-3-wan.telkom-ipnet.co.za (196.25.54.13) 68.535 ms 74.043 ms 74.099 ms
8 lon-ip-dir-telecity-pos-7-0-1.telkom-ipnet.co.za (196.43.18.6) 298.513 ms 298.576 ms 303.786 ms
9 83.245.76.221 (83.245.76.221) 318.588 ms 318.713 ms 318.766 ms
10 209.85.255.175 (209.85.255.175) 303.841 ms 209.85.252.76 (209.85.252.76) 303.743 ms 328.299 ms
11 66.249.95.170 (66.249.95.170) 318.282 ms 318.341 ms 318.656 ms
12 216.239.49.45 (216.239.49.45) 289.941 ms 72.14.236.191 (72.14.236.191) 304.023 ms 209.85.251.231 (209.85.251.231) 309.207 ms
13 209.85.243.81 (209.85.243.81) 324.142 ms 209.85.243.73 (209.85.243.73) 329.111 ms 209.85.243.85 (209.85.243.85) 344.046 ms
14 ww-in-f104.google.com (209.85.229.104) 358.567 ms 363.281 ms 363.337 ms
 
Odd, maybe they are balancing the two connections per tower or something odd
 
Yup,

My WoW gaming lately has been really terrible. I even decided to signup to Gamemax in the hopes that it would solve the problem but Packet loss really seems to be the culprit here.

I received an sms from Screamer last week Thursday saying that they would be working on my area and honestly it seems that since then I am getting up to 18 000ms in WoW.

At least by using Gamemax I am able to stay connected for extended periods but still not really good for a raid and the like.
 
Last edited:
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X