Screamer WiMax

Hi Wowforlife

We have identified the problem to them and they have promised to sort out the problem this weekend.

We are even more frustrated than you are.

Sorry about the inconvenience.:(
 
Dear Howzit.

I have phoned your sales office yesterday and he informed me that if i want a 1024mbit connection i have to pay 25% extra ? is this true ?
 
howzit said:
Hi Wowforlife

We have identified the problem to them and they have promised to sort out the problem this weekend.

We are even more frustrated than you are.

Sorry about the inconvenience.:(
Click to expand...

Thanks for the update - posts like these make for happier customers :D
 
howzit said:
Hi Wowforlife

We have identified the problem to them and they have promised to sort out the problem this weekend.

We are even more frustrated than you are.

Sorry about the inconvenience.:(
Click to expand...

"howzit" you are a plain out liar ! i have just spoken to your technical department who are clueless about this. According to your technical department, Neotel is the issue and they have NO ETA on when this issue will be resolved. I am in damn good mind to take a legal route on the basis of fraud and theft with Screamer.

Once again how can Screamer be willing to take a debit order in advance when your service is not blady well working !

I am not content with one excuse after the next. ALL I WANT IS TO GET WHAT I PAY FOR. now get your backsides in gear !

FYI: Your director is joke who avoids complaint calls. Lack of leadership filters to lack of Service ! Hmmm i think i spot a link here !
 
Last edited:
Code: 
                                            Packets               Pings
 Host                                     Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 10.0.64.253                           94.7%    20   37.8  37.8  37.8  37.8   0.0
 2. 172.11.11.1                           94.7%    20   53.9  53.9  53.9  53.9   0.0
 3. 10.254.253.254                        94.7%    20   54.9  54.9  54.9  54.9   0.0
 4. 172.17.0.1                            94.7%    20   55.9  55.9  55.9  55.9   0.0
 5. 172.17.0.159                          94.7%    20   56.9  56.9  56.9  56.9   0.0
 6. 41.154.7.32                           94.7%    20   48.2  48.2  48.2  48.2   0.0
 7. firewall1.vlan15.jnb1.gp-online.net   94.7%    20   38.8  38.8  38.8  38.8   0.0
 8. 41.161.56.1                           94.7%    20   59.9  59.9  59.9  59.9   0.0
 9. 41.160.0.244                          94.7%    20   50.9  50.9  50.9  50.9   0.0
10. 198.32.142.10                         94.7%    20   66.9  66.9  66.9  66.9   0.0
11. 168.209.1.164                         94.7%    20   54.7  54.7  54.7  54.7   0.0
12. core1a-bry-gi0-0-1-215.ip.isnet.net   94.7%    20   47.8  47.8  47.8  47.8   0.0
13. 168.209.217.21                        94.7%    20   64.0  64.0  64.0  64.0   0.0
14. ???

I might as well go back to Vodacom 3G... Obviously interference.

I guess Screamers avoidance is more "Oh ***, our illegally used spectrum isn't working and we can't do anything about it".
 
howzit said:
Hi Wowforlife

We have identified the problem to them and they have promised to sort out the problem this weekend.

We are even more frustrated than you are.

Sorry about the inconvenience.:(
Click to expand...

I am now writing this msg (via 3G with my cell phone as a modem) at 22:54 06 September 2009 (sunday) and guess what, Screamer still has the same issues. So whats your next move ? "Oh Neotel will attend to it". How can your infrastructure be based solely on Neotel ? If it isnt you cant keep passing the blame to them. Once again if Neotel are able single handedly bring your service levels to "non existant" why was i not informed about this when i signed up ?

According to your sales department we should all never experience any of the problems we are, because your sales department says they use multiple providers.

So again i ask when will this "identified but not yet rectified fault" get some attending to ! ?

FYI: I was promised a phone call about this on friday evening via your technical department, suprise surprise i am still waiting ! Screamer is utterly pathetic.
 
My experience atm isn't great ... far from it actually - for example:

Reply from 209.85.227.106: bytes=32 time=619ms TTL=48
Reply from 209.85.227.106: bytes=32 time=262ms TTL=48
Request timed out.
Reply from 209.85.227.106: bytes=32 time=1147ms TTL=48
Request timed out.
Reply from 209.85.227.106: bytes=32 time=237ms TTL=48
Reply from 209.85.227.106: bytes=32 time=415ms TTL=48
Reply from 209.85.227.106: bytes=32 time=308ms TTL=48
Reply from 209.85.227.106: bytes=32 time=613ms TTL=48
Reply from 209.85.227.106: bytes=32 time=421ms TTL=48
Reply from 209.85.227.106: bytes=32 time=675ms TTL=48
Request timed out.
Reply from 209.85.227.106: bytes=32 time=1216ms TTL=48
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 209.85.227.106: bytes=32 time=387ms TTL=48
Reply from 209.85.227.106: bytes=32 time=275ms TTL=48
Reply from 209.85.227.106: bytes=32 time=243ms TTL=48
Reply from 209.85.227.106: bytes=32 time=237ms TTL=48
Reply from 209.85.227.106: bytes=32 time=256ms TTL=48
Reply from 209.85.227.106: bytes=32 time=374ms TTL=48
Reply from 209.85.227.106: bytes=32 time=237ms TTL=48
Reply from 209.85.227.106: bytes=32 time=235ms TTL=48
Reply from 209.85.227.106: bytes=32 time=229ms TTL=48
Reply from 209.85.227.106: bytes=32 time=232ms TTL=48
Reply from 209.85.227.106: bytes=32 time=235ms TTL=48
Reply from 209.85.227.106: bytes=32 time=234ms TTL=48
Reply from 209.85.227.106: bytes=32 time=237ms TTL=48
Reply from 209.85.227.106: bytes=32 time=256ms TTL=48
Request timed out.
Reply from 209.85.227.106: bytes=32 time=291ms TTL=48
Reply from 209.85.227.106: bytes=32 time=244ms TTL=48
Reply from 209.85.227.106: bytes=32 time=237ms TTL=48
Reply from 209.85.227.106: bytes=32 time=1112ms TTL=48
Reply from 209.85.227.106: bytes=32 time=633ms TTL=48
Reply from 209.85.227.106: bytes=32 time=1078ms TTL=48
Reply from 209.85.227.106: bytes=32 time=834ms TTL=48
Reply from 209.85.227.106: bytes=32 time=749ms TTL=48
Reply from 209.85.227.106: bytes=32 time=1142ms TTL=48

Seems like the problem wasn't corrected this weekend.
 
Last edited:
bulwer_last_10800.png
 
Had a chat to Screamer earlier today - seems as if Neotel are still working on the problem - hoping for a resolution this week still.
 
wow4life said:
Had a chat to Screamer earlier today - seems as if Neotel are still working on the problem - hoping for a resolution this week still.
Click to expand...

Yeah i chatted to them today as well and i got the same excuse as you did. I would really like to see a response from Mr "howzit". This all seems like "cloak and daggers" to me.
 
tower_last_10800.png


It's even better at night... :rolleyes: and that's to the network edge, NOT Neotel... :mad:
 
Last edited:
Must be all those big arse IPWireless basestations from Sentech interfering with Screamers' "wimax spectrum"
 
My connection to Screamer's network is pretty damn solid - the problems occur outside of their network. This isn't ideal by any stretch of the imagination but at least the problem is known and a resolution seems to be around the corner.

fyi: Getting about 7% packet loss atm
 
Last edited:
They seem to have finally given up on Neocrap

Code: 
 2  10.0.64.253 (10.0.64.253)  61.380 ms  61.261 ms  67.430 ms
 3  172.11.11.1 (172.11.11.1)  79.706 ms  85.964 ms  85.963 ms
 4  10.254.253.254 (10.254.253.254)  91.734 ms  97.812 ms  103.956 ms
 5  172.17.0.1 (172.17.0.1)  103.940 ms  109.582 ms  115.566 ms
 6  172.17.0.3 (172.17.0.3)  140.414 ms  139.494 ms  139.479 ms
 7  196.15.204.81 (196.15.204.81)  139.663 ms  68.000 ms  74.043 ms
 8  tpr-ip-esr-3-wan.telkom-ipnet.co.za (196.25.54.13)  143.007 ms  142.933 ms  149.310 ms
 9  196.43.18.134 (196.43.18.134)  472.839 ms  491.757 ms  491.654 ms
 
cda said:
They seem to have finally given up on Neocrap

Code: 
 2  10.0.64.253 (10.0.64.253)  61.380 ms  61.261 ms  67.430 ms
 3  172.11.11.1 (172.11.11.1)  79.706 ms  85.964 ms  85.963 ms
 4  10.254.253.254 (10.254.253.254)  91.734 ms  97.812 ms  103.956 ms
 5  172.17.0.1 (172.17.0.1)  103.940 ms  109.582 ms  115.566 ms
 6  172.17.0.3 (172.17.0.3)  140.414 ms  139.494 ms  139.479 ms
 7  196.15.204.81 (196.15.204.81)  139.663 ms  68.000 ms  74.043 ms
 8  tpr-ip-esr-3-wan.telkom-ipnet.co.za (196.25.54.13)  143.007 ms  142.933 ms  149.310 ms
 9  196.43.18.134 (196.43.18.134)  472.839 ms  491.757 ms  491.654 ms
Click to expand...

I think this is a temporary measure until the Neotel issue is resolved.
 
this is to the gamemax server :

Code: 
Tracing route to denise.gamemax.org [94.229.66.54]
over a maximum of 30 hops:

  1    60 ms    49 ms    49 ms  10.0.64.253
  2    58 ms    54 ms    55 ms  172.11.11.1
  3    55 ms    53 ms    55 ms  10.254.253.254
  4    49 ms    59 ms    40 ms  172.17.0.1
  5    58 ms    55 ms    54 ms  172.17.0.159
  6    58 ms    59 ms    54 ms  41.154.7.32
  7    56 ms    64 ms    59 ms  firewall1.vlan15.jnb1.gp-online.net [41.154.0.26
]
  8    63 ms     *       64 ms  41.161.56.1
  9    63 ms    78 ms    60 ms  41.160.0.244
 10    64 ms    60 ms    59 ms  if-1-8.bb1.JSO-Johannesburg.as6453.net [216.6.55
.41]
 11   233 ms   244 ms     *     if-3-4.core2.LDN-London.as6453.net [216.6.55.34]

 12   234 ms   230 ms   234 ms  if-9-1.mcore3.LDN-London.as6453.net [195.219.195
.5]
 13   238 ms   234 ms   229 ms  sl-gw29-lon-0-0-2.sprintlink.net [82.195.189.129
]
 14   233 ms   234 ms   230 ms  sl-bb23-lon-2-0-0.sprintlink.net [213.206.128.18
6]
 15   232 ms   230 ms   224 ms  sl-gw23-lon-15-0.sprintlink.net [213.206.128.63]

 16   232 ms   390 ms   230 ms  89.191.196.130
 17   233 ms   230 ms   240 ms  195.72.129.125
 18   239 ms   239 ms   230 ms  no.rdns-yet.ukservers.com [77.74.193.230]
 19   240 ms   234 ms   230 ms  bsd1.ukservers.com [78.110.166.122]
 20   233 ms   230 ms   234 ms  earth.vpsville.co.uk [94.229.66.5]
 21   234 ms   229 ms   229 ms  94.229.66.54

Trace complete.

No idea why im getting 7K MS .. has it got to do with the actual packet loss?
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X