Screamer sucks

maybe i am one of the lucky few.
then as i have mayb had 2 disconnects the whole of last week.
wow i have avg ping of about 350ms to 500ms

web browsing is not to bad. and avg dl speed is about 110kb/s depending on what i download but the large stuff i have been downloading over the last week that was the speed i was getting.

i connect to the Kylami Tower and stay in the fourways area if that helps somewhat..
 
Darksun said:
maybe i am one of the lucky few.
then as i have mayb had 2 disconnects the whole of last week.
wow i have avg ping of about 350ms to 500ms

web browsing is not to bad. and avg dl speed is about 110kb/s depending on what i download but the large stuff i have been downloading over the last week that was the speed i was getting.

i connect to the Kylami Tower and stay in the fourways area if that helps somewhat..
Click to expand...

My connection is normally good - this weekend and atm is an exception and I believe it is due to network maintenance by their backhaul provider.
 
Well, I have perfectly good (even perhaps excellent) signal but my TX modulation is bouncing around from BPSK to QAM16.

This either means interference, some seriously broken tower config, or push back from overloaded spectrum... At least that's what various sources on the subject inform me.

Of course, apparently no one cares.
 
cda said:
Well, I have perfectly good (even perhaps excellent) signal but my TX modulation is bouncing around from BPSK to QAM16.

This either means interference, some seriously broken tower config, or push back from overloaded spectrum... At least that's what various sources on the subject inform me.

Of course, apparently no one cares.
Click to expand...

How do you check that? I assume it is directly on the IDU. Plug directly in and then set my browser to what ip?
 
Ya screw this actually... I'm off to order a DSL line.
 
Hi ppl... i made the change more than a year ago..... they do suck and if i can give advise CHANGE.

In my area basically 95% of the screamer clients canceled their service they even lost their reseller in the area due to the poor service.
 
Fairly clear trend of where the problem is

Code: 
                                                   Packets               Pings
 Host                                            Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 10.0.64.253                                   0.0%    33   51.7  51.2  33.9 122.1  13.2
 2. 172.11.11.1                                   0.0%    33   55.2  54.0  40.3  60.6   3.6
 3. 10.254.253.254                                3.0%    33   37.8  53.7  37.8  66.2   4.5
 4. 172.17.0.1                                    0.0%    33   62.0  54.6  49.5  62.0   2.8
 5. 172.17.0.159                                  0.0%    33   55.9  54.2  47.6  58.2   2.7
 6. 41.154.7.32                                   0.0%    33   54.6  53.3  39.0  61.9   3.8
 7. firewall1.vlan15.jnb1.gp-online.net           3.0%    33   53.8  55.6  47.7  63.2   3.4
 8. 41.161.56.1                                   9.1%    33   63.1  59.7  50.7  66.9   3.4
 9. 41.160.0.244                                 15.2%    33   61.0  67.7  52.2 167.7  22.8
10. 41.160.2.65                                  18.2%    33  129.1  65.6  54.6 129.1  14.8
11. vlan9.hr3.jnb6.za.mtnbusiness.net            21.2%    33   61.9  61.7  46.1  83.0   6.3
12. 196.30.213.108                               18.2%    33   71.1  62.0  45.0  72.1   6.0
13. firewall1.jnb2.host-h.net                     3.1%    32   60.7  61.5  45.3  75.3   5.8
14. mybroadband.co.za                            25.0%    32   63.6  63.1  53.2  70.9   4.5

Code: 
                                                   Packets               Pings
 Host                                            Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 10.0.64.253                                   0.0%    21   50.3  48.6  27.9  52.4   5.1
 2. 172.11.11.1                                   0.0%    21   41.2  54.8  41.2  57.9   3.5
 3. 10.254.253.254                                0.0%    21   49.8  54.1  34.9  58.8   5.2
 4. 172.17.0.1                                    0.0%    21   52.6  54.3  37.4  58.5   4.7
 5. 172.17.0.159                                  4.8%    21   48.7  55.1  48.7  58.2   2.2
 6. 41.154.7.32                                   0.0%    21   49.7  52.7  41.3  59.3   5.0
 7. firewall1.vlan15.jnb1.gp-online.net           4.8%    21   50.7  54.9  44.0  67.6   5.3
 8. 41.161.56.1                                  14.3%    21   56.6  59.1  41.8  63.0   4.8
 9. 41.160.0.244                                 23.8%    21   52.6  67.1  52.6 148.4  22.5
10. if-1-8.bb1.JSO-Johannesburg.as6453.net       15.0%    21   62.4  62.0  55.2  73.6   4.6
11. if-3-7.core2.LDN-London.as6453.net           23.8%    21  228.6 255.1 228.6 391.3  45.0
12. if-3-2.mcore3.LDN-London.as6453.net          14.3%    21  218.6 232.8 218.6 243.9   5.8
13. Vlan62.icore1.LDN-London.as6453.net          14.3%    21  228.5 236.2 228.5 245.8   4.9
14. xe-10-2-0-edge3.london1.level3.net            9.5%    21  219.3 236.4 219.3 270.2   9.6
15. ae-34-52.ebr2.London1.Level3.net             23.8%    21  229.9 235.1 223.5 240.3   4.0
16. ae-41-41.ebr1.NewYork1.Level3.net            25.0%    21  373.7 375.9 356.8 385.3   6.4
17. ae-3-3.ebr4.Washington1.Level3.net           20.0%    21  379.0 379.8 373.0 388.0   4.0
18. ae-64-64.csw1.Washington1.Level3.net         15.0%    21  385.4 378.7 368.7 390.6   5.9
19. ae-1-69.edge1.Washington1.Level3.net         30.0%    21  376.7 379.4 366.8 434.2  18.1
20. GOOGLE-INC.edge1.Washington1.Level3.net      25.0%    21  318.1 317.2 308.6 334.7   7.0
21. 209.85.240.136                               15.0%    21  312.4 311.4 304.2 317.1   2.9
22. 66.249.95.149                                20.0%    21  326.9 326.6 319.0 330.8   3.1
    72.14.238.136
23. 72.14.239.127                                20.0%    20  323.1 327.3 321.8 337.7   4.3
    209.85.254.247
    72.14.239.131
    209.85.254.249
24. 209.85.255.194                               30.0%    20  333.0 333.7 324.0 341.0   5.4
    209.85.255.198
    209.85.255.190
25. gw-in-f100.google.com                        31.6%    20  326.2 327.5 319.7 345.9   6.8
 
diebaas said:
Hi ppl... i made the change more than a year ago..... they do suck and if i can give advise CHANGE.
Click to expand...

I don't agree.

To be fair to them they have been very supportive and helpful to me and I know that they are addressing the issues in their WiMax network.

Personally I will wait awhile longer to see how it goes.
 
wow4life said:
I don't agree.

To be fair to them they have been very supportive and helpful to me and I know that they are addressing the issues in their WiMax network.

Personally I will wait awhile longer to see how it goes.
Click to expand...

I was with Webintact then the partners parted ways and we went with Global Webintact then it changed to Screamer then there was promises made of changes waited over a year nothing improved, all the phone calls made to them regarding problems and it was always the same answer " Our technician's are aware of the problem and is working on it".

I did walk a very long road with them, and a person can only take so much.
 
diebaas said:
I was with Webintact then the partners parted ways and we went with Global Webintact then it changed to Screamer then there was promises made of changes waited over a year nothing improved, all the phone calls made to them regarding problems and it was always the same answer " Our technician's are aware of the problem and is working on it".

I did walk a very long road with them, and a person can only take so much.
Click to expand...

I personally have had a great experience with Screamer and find it hard to believe that there are clients of theirs that still have a problem with their service.

That is untill I checked your posts, "diebaas", and discovered that even though you left their service years ago you still seem to have an axe to grind.

Maybe try their service again and then your commentary will be more relevant to the rest of us.
 
Playoff said:
I personally have had a great experience with Screamer and find it hard to believe that there are clients of theirs that still have a problem with their service.

That is untill I checked your posts, "diebaas", and discovered that even though you left their service years ago you still seem to have an axe to grind.

Maybe try their service again and then your commentary will be more relevant to the rest of us.
Click to expand...

You see most of threads regarding GWI aka screamer now i used to post on and about three buddies of mine is still on their network, so i still hear about the complains.
 
I signed up with the Screamer guys last Wednesday. We moved and Telkom wait on DSL is pointless as i wont be here long enough. Connecting to Kyalami from Sunninghill.

Screamer guys all ridiculously helpfull from helpdesk to techies.

I was plagued by problems DCs not connecting again horible packet loss.
They sent out Team next day replaced hardware realigned the arial outside. Worked for a few hours but not great then permanent DC again.

The next day they sent another crew with a Level 2 Tech and they raised the arial 2.5 meters did some more testing and the service is now working really nicely.

I play WoW and through proxy sat on 260ms even in VoA 10 man did not go higher than 300ms.
Should have tried without proxy to get latency but didnt bother.

SSH to our local servers is decent latency on about 90ms for that. Not quite the 40ms DSL but its decent enough from a wireless link.

There is still the odd packet loss but i was told that they are aware of it and are working hard to rectify it.

If their team internally are as dedicated as their Techies, Installers and Helpdesk then it wont take long. Its been a long time since any company i have dealt with has tried so hard to make an experience easy and painless.

So if you are having problems rather let them try fix it i get 50 to 60K on this link now latencys decent so i am very happy i decided to let them sort it out rather than move providers. And they are damned quick at doing so.

here is ping to local server

Pinging ***.co.za [196.22.132.174] with 32 bytes of data:
Reply from 196.22.*.174: bytes=32 time=89ms TTL=49
Reply from 196.22.*.174: bytes=32 time=84ms TTL=49
Reply from 196.22.*.174: bytes=32 time=73ms TTL=49
Reply from 196.22.*.174: bytes=32 time=77ms TTL=49
Reply from 196.22.*.174: bytes=32 time=77ms TTL=49
Reply from 196.22.*.174: bytes=32 time=78ms TTL=49
Reply from 196.22.*.174: bytes=32 time=70ms TTL=49
Reply from 196.22.*.174: bytes=32 time=67ms TTL=49
Reply from 196.22.*.174: bytes=32 time=71ms TTL=49
Reply from 196.22.*.174: bytes=32 time=90ms TTL=49
Reply from 196.22.*.174: bytes=32 time=82ms TTL=49
Reply from 196.22.*.174: bytes=32 time=91ms TTL=49
Reply from 196.22.*.174: bytes=32 time=73ms TTL=49
Reply from 196.22.*.174: bytes=32 time=93ms TTL=49
Reply from 196.22.*.174: bytes=32 time=77ms TTL=49
Reply from 196.22.*.174: bytes=32 time=78ms TTL=49
Reply from 196.22.*.174: bytes=32 time=77ms TTL=49
Reply from 196.22.*.174: bytes=32 time=75ms TTL=49
Reply from 196.22.*.174: bytes=32 time=72ms TTL=49
Reply from 196.22.*.174: bytes=32 time=80ms TTL=49
Reply from 196.22.*.174: bytes=32 time=77ms TTL=49
Reply from 196.22.*.174: bytes=32 time=77ms TTL=49
Reply from 196.22.*.174: bytes=32 time=77ms TTL=49

Ping statistics for 196.22.*.174:
Packets: Sent = 23, Received = 23, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 67ms, Maximum = 93ms, Average = 78ms

This is to our UK Server
ping wdev.co.za -t

Pinging ***.co.za [77.68.44.70] with 32 bytes of data:
Reply from 77.68.*.70: bytes=32 time=245ms TTL=45
Reply from 77.68.*.70: bytes=32 time=249ms TTL=45
Reply from 77.68.*.70: bytes=32 time=265ms TTL=45
Reply from 77.68.*.70: bytes=32 time=246ms TTL=45
Reply from 77.68.*.70: bytes=32 time=249ms TTL=45
Reply from 77.68.*.70: bytes=32 time=241ms TTL=45
Reply from 77.68.*.70: bytes=32 time=249ms TTL=45
Reply from 77.68.*.70: bytes=32 time=241ms TTL=45
Reply from 77.68.*.70: bytes=32 time=248ms TTL=45
Reply from 77.68.*.70: bytes=32 time=250ms TTL=45
Reply from 77.68.*.70: bytes=32 time=249ms TTL=45
Reply from 77.68.*.70: bytes=32 time=249ms TTL=45
Reply from 77.68.*.70: bytes=32 time=248ms TTL=45
Reply from 77.68.*.70: bytes=32 time=249ms TTL=45
Reply from 77.68.*.70: bytes=32 time=252ms TTL=45
Reply from 77.68.*.70: bytes=32 time=251ms TTL=45

Ping statistics for 77.68.*.70:
Packets: Sent = 16, Received = 16, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 241ms, Maximum = 265ms, Average = 248ms

And to mybroadband.co.za
Pinging mybroadband.co.za [41.203.21.136] with 32 bytes of data:
Reply from 41.203.21.136: bytes=32 time=89ms TTL=49
Reply from 41.203.21.136: bytes=32 time=77ms TTL=49
Reply from 41.203.21.136: bytes=32 time=92ms TTL=49
Reply from 41.203.21.136: bytes=32 time=69ms TTL=49
Reply from 41.203.21.136: bytes=32 time=71ms TTL=49
Reply from 41.203.21.136: bytes=32 time=93ms TTL=49
Reply from 41.203.21.136: bytes=32 time=92ms TTL=49
Reply from 41.203.21.136: bytes=32 time=78ms TTL=49
Reply from 41.203.21.136: bytes=32 time=76ms TTL=49
Reply from 41.203.21.136: bytes=32 time=77ms TTL=49
Reply from 41.203.21.136: bytes=32 time=77ms TTL=49
Reply from 41.203.21.136: bytes=32 time=69ms TTL=49
Reply from 41.203.21.136: bytes=32 time=62ms TTL=49
Reply from 41.203.21.136: bytes=32 time=77ms TTL=49
Reply from 41.203.21.136: bytes=32 time=67ms TTL=49

Ping statistics for 41.203.21.136:
Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 62ms, Maximum = 93ms, Average = 77ms

As you can see from plagued problems and non usable service. Allowing them to sort it out has given me an excellent service and i get my 512K speeds.

Hope this helps
 
Last edited:
Marklo

Well give them the benefit of the doubt, but there is better solutions out there,

I am still with a wireless provider, just it was time for me to move.

Just a quicky, i pinged the same servers and my results is.

ping ooo.co.za -t

Pinging ooo.co.za [196.22.132.174] with 32 bytes of data:

Reply from 196.22.132.174: bytes=32 time=24ms TTL=58
Reply from 196.22.132.174: bytes=32 time=37ms TTL=58
Reply from 196.22.132.174: bytes=32 time=12ms TTL=58
Reply from 196.22.132.174: bytes=32 time=23ms TTL=58
Reply from 196.22.132.174: bytes=32 time=11ms TTL=58
Reply from 196.22.132.174: bytes=32 time=12ms TTL=58
Reply from 196.22.132.174: bytes=32 time=34ms TTL=58
Reply from 196.22.132.174: bytes=32 time=18ms TTL=58
Reply from 196.22.132.174: bytes=32 time=19ms TTL=58
Reply from 196.22.132.174: bytes=32 time=10ms TTL=58
Reply from 196.22.132.174: bytes=32 time=11ms TTL=58
Reply from 196.22.132.174: bytes=32 time=14ms TTL=58
Reply from 196.22.132.174: bytes=32 time=18ms TTL=58
Reply from 196.22.132.174: bytes=32 time=10ms TTL=58
Reply from 196.22.132.174: bytes=32 time=84ms TTL=58

Ping statistics for 196.22.132.174:
Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 84ms, Average = 22ms

ping wdev.co.za -t

Pinging wdev.co.za [77.68.44.70] with 32 bytes of data:

Reply from 77.68.44.70: bytes=32 time=14ms TTL=58
Reply from 77.68.44.70: bytes=32 time=27ms TTL=58
Reply from 77.68.44.70: bytes=32 time=42ms TTL=58
Reply from 77.68.44.70: bytes=32 time=22ms TTL=58
Reply from 77.68.44.70: bytes=32 time=12ms TTL=58
Reply from 77.68.44.70: bytes=32 time=18ms TTL=58
Reply from 77.68.44.70: bytes=32 time=10ms TTL=58
Reply from 77.68.44.70: bytes=32 time=12ms TTL=58
Reply from 77.68.44.70: bytes=32 time=13ms TTL=58
Reply from 77.68.44.70: bytes=32 time=18ms TTL=58
Reply from 77.68.44.70: bytes=32 time=15ms TTL=58
Reply from 77.68.44.70: bytes=32 time=17ms TTL=58
Reply from 77.68.44.70: bytes=32 time=55ms TTL=58
Reply from 77.68.44.70: bytes=32 time=105ms TTL=58
Reply from 77.68.44.70: bytes=32 time=96ms TTL=58

Ping statistics for 77.68.44.70:
Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 105ms, Average = 31ms

ping mybroadband.co.za -t

Pinging mybroadband.co.za [41.203.21.136] with 32 bytes of data:

Reply from 41.203.21.136: bytes=32 time=37ms TTL=58
Reply from 41.203.21.136: bytes=32 time=18ms TTL=58
Reply from 41.203.21.136: bytes=32 time=7ms TTL=58
Reply from 41.203.21.136: bytes=32 time=16ms TTL=58
Reply from 41.203.21.136: bytes=32 time=11ms TTL=58
Reply from 41.203.21.136: bytes=32 time=8ms TTL=58
Reply from 41.203.21.136: bytes=32 time=8ms TTL=58
Reply from 41.203.21.136: bytes=32 time=8ms TTL=58
Reply from 41.203.21.136: bytes=32 time=19ms TTL=58
Reply from 41.203.21.136: bytes=32 time=21ms TTL=58
Reply from 41.203.21.136: bytes=32 time=12ms TTL=58
Reply from 41.203.21.136: bytes=32 time=13ms TTL=58
Reply from 41.203.21.136: bytes=32 time=15ms TTL=58

Ping statistics for 41.203.21.136:
Packets: Sent = 13, Received = 13, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 37ms, Average = 14ms

Can you see the difference..

Well i wish everybody on screamer the best of luck......... me unsubscribing from the thread.
 
Last edited:
Playoff said:
I personally have had a great experience with Screamer and find it hard to believe that there are clients of theirs that still have a problem with their service.
Click to expand...

Why is it hard to believe?

IP is a difficult and competetive industry, Screamer are not working hard enough.

Every time I phone their technical support, I get the feeling I'm talking to a concrete block. I've had more enlightening conversations with the Multichoice IVR. I get the feeling the Screamer tech support are more interested in hanging up the phone or picking a random excuse to get you to do so, than investigating an issue. Nevermind service with a smile, how about service with a clue. To solve my latency issues, he recommended I change my DNS server address. Hello? What the ****? This was after he said "It could be a number of problems". Yes? How about starting with one and fixing it? Must I the customer just be content that "Oh well, **** happens with WiMax it could be anything, sit back and enjoy the ride"

Whilst the Screamer rep person here (who just goes "PM me!" and then vanishes for a week, and then asks you to PM him again when you complain again - is he a gold fish? Is he even a screamer employee?), is claiming that they are doing emergency maintenance on their crummy Neotel link, their technical support people seem to be blisfully unaware and claim everything is fine.

If anything, you should choose which clients you piss off...
 
I agree that their first line support is poor and I have never received a helpful response from them. However, I haven't used 1st line support for a long time now.

The 2nd line support guys are pretty good and are very quick to either resolve my problems or provide insight into the issue. Ideally there wouldn't be any problems but I know they are working on building and stabilising their network.

I used to live in the UK and know how good it can be but then they had copper and fibre everywhere ....
 
diebass

who is your provider.

Pinging wdev.co.za [77.68.44.70] with 32 bytes of data:

Reply from 77.68.44.70: bytes=32 time=14ms TTL=58
Reply from 77.68.44.70: bytes=32 time=27ms TTL=58
Reply from 77.68.44.70: bytes=32 time=42ms TTL=58
Reply from 77.68.44.70: bytes=32 time=22ms TTL=58
Reply from 77.68.44.70: bytes=32 time=12ms TTL=58

That server is in the UK and that server hits the WoW servers at 32ms.
So theoretically you could have the sub 100ms WoW latencys in your hands.

Please could u send me info on who you are using those latencys are insane.
 
would be interested as well :)
anything to get those wow latencies down even more :D
 
Okay on this matter i live with "cda". This is my perspective on screamer.

1) Service was wonderfull when i placed the order with them
2) Their technicians came out and said "sorry we can't help you and the signal is not good enough"
3) a few days later i noticed their technicians installing with no problems at an adjacent unit.
4) Now with my complaining their technicians actually came back and did a wonder full job installing (i.e actually bothering to mount their equipment on the roof) and worked quite late afterhours (7:30 pm) to get the installation working and done correctly.
5) after one week we get cut off. The excuse was "sorry you ordered a 1GB account". So we fax the paperwork through confirming that we did indeed order a 5GB account.
6) So now we are at the end of the month and debit order comes. "CDA" got debited for over R2000 when our bill should have been around R1000 or just over. No hassels we contact accounts. The usual "sorry sir we will sort it out" comment. No problems by myself and "CDA" we live with it. Now another month down the line we still havn't got our money back from them. Yes it does put our account into credit which is a good thing. However WE DID ASK for the money to be returned, which screamer agreed to.
7) Now with actual relation to what this thread is about, WHEN CAN WE EXPECT THIS PROBLEM with your net connections to be sorted out ! ??

I am a gaming addict! Further more i informed your sales staff about this when i placed the order. Now you (screamer) say "we are attending to it". Utter BS. I can not even begin to think about playing any game online due absolutely crap latencies. My average WOW latency is 2000ms - 5500ms, which has been going on longer than 2 weeks (almost half a blady month !) . I ask you, would anyone here put up with this. Not even telscum (telkom) can be this bad at service delivery and customer realtions.

ONCE AGAIN when will this BS get sorted out!! ??

Dont dare ask me to PM you. Get off your lazy ass and phone me. You have my details. If you don't, ask your techincal department for my customer number. I phoned them @ 17:00 (yesterday 02 September 2009) and again at 20:35 to try get some answers, but as "CDA" says "it is like talking to a brick wall".

EDIT: removed some of my more fruitier language.
 
Last edited:
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X