New IP range for MyWireless 256

JayT

Senior Member
Joined
Aug 26, 2004
Messages
505
Reaction score
0
Location
Cape Town
Anyone else notice the ip changes?

Im now connected to: 196.31.33.xx. I disconnected and reconnected to a similar range
 
Yes I noticed it, right now I'm connected to 196.31.33.185 , damn its extremely slow!
 
Might be due to
Sentech Bulletin Board said:
MyWireless - Failure on 256kbps Usergroup: 17 August 2006

A failure is currently being experienced on the MyWireless network resulting in the 256kbps usergroup experiencing degraded throughput. Our technicians are working on the problem with the highest priority.
I'm also on 196.31.33.*
 
My connection was fine yesterday and earlier today. Why couldnt they just bump us up to the 512 usergroup instead of dropping us to below the 128 group
 
196.31.34.* here :D
Some packet loss though
Crucial.co.uk said:
Pinging www.crucial.co.uk [194.154.164.82] with 32 bytes of data:

Reply from 194.154.164.82: bytes=32 time=526ms TTL=43
Reply from 194.154.164.82: bytes=32 time=420ms TTL=43
Reply from 194.154.164.82: bytes=32 time=509ms TTL=43
Reply from 194.154.164.82: bytes=32 time=452ms TTL=43
Reply from 194.154.164.82: bytes=32 time=631ms TTL=43
Reply from 194.154.164.82: bytes=32 time=533ms TTL=43
Request timed out.
Request timed out.
Request timed out.
Reply from 194.154.164.82: bytes=32 time=477ms TTL=43

Ping statistics for 194.154.164.82:
Packets: Sent = 10, Received = 7, Lost = 3 (30% loss),
Approximate round trip times in milli-seconds:
Minimum = 420ms, Maximum = 631ms, Average = 506ms
Packets: Sent = 10, Received = 7, Lost = 3 (30% loss),
Approximate round trip times in milli-seconds:
Minimum = 430ms, Maximum = 692ms, Average = 535ms
Crucial.com said:
Pinging www.crucial.com [137.201.245.23] with 32 bytes of data:

Request timed out.
Reply from 137.201.245.23: bytes=32 time=430ms TTL=47
Reply from 137.201.245.23: bytes=32 time=508ms TTL=47
Reply from 137.201.245.23: bytes=32 time=447ms TTL=47
Reply from 137.201.245.23: bytes=32 time=567ms TTL=47
Reply from 137.201.245.23: bytes=32 time=494ms TTL=47
Request timed out.
Reply from 137.201.245.23: bytes=32 time=608ms TTL=47
Request timed out.
Reply from 137.201.245.23: bytes=32 time=692ms TTL=47

Ping statistics for 137.201.245.23:
Packets: Sent = 10, Received = 7, Lost = 3 (30% loss),
Approximate round trip times in milli-seconds:
Minimum = 430ms, Maximum = 692ms, Average = 535ms
Sentech.co.za said:
Pinging www.sentech.co.za [66.18.65.124] with 32 bytes of data:

Request timed out.
Reply from 66.18.65.124: bytes=32 time=310ms TTL=250
Request timed out.
Reply from 66.18.65.124: bytes=32 time=210ms TTL=250
Reply from 66.18.65.124: bytes=32 time=75ms TTL=250
Reply from 66.18.65.124: bytes=32 time=169ms TTL=250
Reply from 66.18.65.124: bytes=32 time=87ms TTL=250
Reply from 66.18.65.124: bytes=32 time=159ms TTL=250
Reply from 66.18.65.124: bytes=32 time=136ms TTL=250
Reply from 66.18.65.124: bytes=32 time=60ms TTL=250

Ping statistics for 66.18.65.124:
Packets: Sent = 10, Received = 8, Lost = 2 (20% loss),
Approximate round trip times in milli-seconds:
Minimum = 60ms, Maximum = 310ms, Average = 150ms
 
Last edited:
If it takes this long for the technicians to solve the problem then I'm speechless.
 
I can't even ****ing connect :(

"The remote computer is not responding"
 
Anyone with real feedback from Sentech?They told me they can't respond to my queries since I'm a nowire client.How long are we gonna wait until the "engineers" fix this?
 
I've being pulling my hair out for most of the week with the speeds I'm getting, a 56k dialup seems to be faster at the moment than my Sentech connection.

Quite frankly, I'm waiting untill the new SNO becomes operational and seeing what emergers from other isp's in terms of connections. Sentech seems to have completely lost the plot.

Yes I do empithise with them with the fact that they dont have the resources to expand there network, but they're not even trying to retain their current customers base and work on promoting the areas that covered.

However it's what i have begun to expect from a "goverment" organisation.

To quote Douglas Adams, "So long, and thanks for all the fish".
 
Last edited:
Quite frankly, I'm waiting untill the new SNO becomes operational and seeing what emergers from other isp's in terms of connections. Sentech seems to have completely lost the plot.

.

Well since for the first 3 to 7 years they will just be hiring Telkom lines I wouldnt hold my breath

And the major cost is anyway theundersea connection out of the country, and the SNO will never install a competing line there
 
I don't think anyone is actually working on this problem.How complex can it be that it takes this long to sort out?
 
Well they said they were giving the problem their highest attention so I'm positive it will be resolved.... imminently.
 
Top
Sign up to the MyBroadband newsletter
X