WA upgrade

BigAl-sa

Executive Member
Joined
Dec 26, 2006
Messages
6,757
Reaction score
317
Location
Pretoria
Got an email from WA that they were migrating to the new network today. I dunno if it did happen, but I'm getting really nice throughput at the mo.
 
I'm running off my netbook on wireless to the adsl router, and the throughput is stunning.
 
Well changing packages require a lot of work. We need a full month of data on the new network first to analyse patterns. That takes us to Jan, on top of that everything shuts down now, and we on a skeleton staff. (Product managers, engineers, developers, analysts etc) So that gives us a month to figure out how to offer better products. Then another month to communicate and implement (Feb) to go live 1st March. It's the soonest operationally that we can afford to do without risking a mess.
 
Well changing packages require a lot of work. We need a full month of data on the new network first to analyse patterns. That takes us to Jan, on top of that everything shuts down now, and we on a skeleton staff. (Product managers, engineers, developers, analysts etc) So that gives us a month to figure out how to offer better products. Then another month to communicate and implement (Feb) to go live 1st March. It's the soonest operationally that we can afford to do without risking a mess.
Ok Fair Fair :) There will be great anticipation
 
Yes, seemed to happen on the time they said.

Is it however expected that international connections will have 50% less latency well local servers 5 times more?

Here are some graphs where my international has gone done from about 400ms to 200ms well my local server (hosted at RSAWEB, IS network I think) has gone up from 10ms to 50ms.

Google.com http://img20.imageshack.us/img20/401/googlecomafterwebafrica.png
co.za server: http://img20.imageshack.us/img20/674/saserverafterwebafricac.png

Local is still fast though and not a problem. Nice to see international seemingly faster
 
Well changing packages require a lot of work. We need a full month of data on the new network first to analyse patterns. That takes us to Jan, on top of that everything shuts down now, and we on a skeleton staff. (Product managers, engineers, developers, analysts etc) So that gives us a month to figure out how to offer better products. Then another month to communicate and implement (Feb) to go live 1st March. It's the soonest operationally that we can afford to do without risking a mess.

I hope some of the other entrants/players in the market will learn from the part in bold.
 
Matt - without releasing any pricing details, can we expect a substantial decrease in bandwidth costs. And will there be a more affordable uncapped ADSL solution ?
 
Matt - without releasing any pricing details, can we expect a substantial decrease in bandwidth costs. And will there be a more affordable uncapped ADSL solution ?

Yes on both counts, the uncapped will take a bit longer because it really is a wild beast. So many have been burned before on it, so we will need to do a free "beta" type test on that. Won't be ready for March though I'm hoping 1st half 2010.
 
Yes on both counts, the uncapped will take a bit longer because it really is a wild beast. So many have been burned before on it, so we will need to do a free "beta" type test on that. Won't be ready for March though I'm hoping 1st half 2010.

Ok well sign me up now for that free "beta" test please. ;)

Thanks for the feedback. Seems like there is good news on it's way.
 
Ever since the migration, my ping to the Johannesburg test server at www.speedtest.net has increased from about 30ms to 110ms.

International pings have vastly improved though, sometimes by as much as a few hundred ms, and so has international download speeds, now hovering at around 3mbp for Europe and the US. I just wonder what's happened to the local pings?
 
Ever since the migration, my ping to the Johannesburg test server at www.speedtest.net has increased from about 30ms to 110ms.

International pings have vastly improved though, sometimes by as much as a few hundred ms, and so has international download speeds, now hovering at around 3mbp for Europe and the US. I just wonder what's happened to the local pings?

See my post above as well
 
Depends where things are hosted and what "Local" means

If Local means WA and SAIX etc you going to have bleeding fast speeds. Over the next few months as we get our peering agreements Local to everyone is going to be super fast from a latency perspective. That is another reason we launched our own gaming to ensure bleeding fast latency.

Many guys on DSL (CPT) have been reporting 13ms to our servers (gaming, mail, web etc)

Our guys just pulled this from the test 4MB Adsl line.



Pinging www.webafrica.co.za [196.220.58.8] with 32 bytes of data:

Reply from 196.220.58.8: bytes=32 time=13ms TTL=120
Reply from 196.220.58.8: bytes=32 time=11ms TTL=120
Reply from 196.220.58.8: bytes=32 time=12ms TTL=120
Reply from 196.220.58.8: bytes=32 time=12ms TTL=120

Ping statistics for 196.220.58.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 13ms, Average = 12ms

C:\Documents and Settings\user>ping www.hetzner.co.za

Pinging hetzner.co.za [41.203.23.117] with 32 bytes of data:

Reply from 41.203.23.117: bytes=32 time=34ms TTL=51
Reply from 41.203.23.117: bytes=32 time=39ms TTL=51
Reply from 41.203.23.117: bytes=32 time=35ms TTL=51
Reply from 41.203.23.117: bytes=32 time=35ms TTL=51

Ping statistics for 41.203.23.117:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 34ms, Maximum = 39ms, Average = 35ms

C:\Documents and Settings\user>ping www.iafrica.com

Pinging www.iafrica.com [196.31.4.2] with 32 bytes of data:

Reply from 196.31.4.2: bytes=32 time=128ms TTL=243
Reply from 196.31.4.2: bytes=32 time=43ms TTL=243
Reply from 196.31.4.2: bytes=32 time=44ms TTL=243
Reply from 196.31.4.2: bytes=32 time=37ms TTL=243

Ping statistics for 196.31.4.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 37ms, Maximum = 128ms, Average = 63ms

C:\Documents and Settings\user>ping www.telkom.co.za

Pinging www.telkom.co.za [196.43.22.222] with 32 bytes of data:

Reply from 196.43.22.222: bytes=32 time=36ms TTL=246
Reply from 196.43.22.222: bytes=32 time=40ms TTL=246
Reply from 196.43.22.222: bytes=32 time=34ms TTL=246
Reply from 196.43.22.222: bytes=32 time=35ms TTL=246

Ping statistics for 196.43.22.222:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 34ms, Maximum = 40ms, Average = 36ms


C:\Documents and Settings\user>ping www.google.com

Pinging www.google.com [209.85.229.103] with 32 bytes of data:

Reply from 209.85.229.103: bytes=32 time=179ms TTL=52
Reply from 209.85.229.103: bytes=32 time=179ms TTL=52
Reply from 209.85.229.103: bytes=32 time=182ms TTL=52
Reply from 209.85.229.103: bytes=32 time=178ms TTL=52

Ping statistics for 209.85.229.103:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 178ms, Maximum = 182ms, Average = 179ms
 
Get more Ping more -- Live Longer

Depends where things are hosted and what "Local" means

Please could we also have some pings to

196.220.59.188

&

196.220.59.189

I assume the DNS servers that you are going to use :confused:

or

better yet a router log-file :whistle:


MW
 
Top
Sign up to the MyBroadband newsletter
X