OFFICIAL Web Africa Network Upgrade Thread

Ok, tried again .. using other addresses.


C:\>tracert webafrica.co.za

Tracing route to webafrica.co.za [196.220.58.66]
over a maximum of 30 hops:

1 4 ms 3 ms 3 ms home.gateway.pace.net [10.0.0.2]
2 23 ms 26 ms 22 ms 196-210-138-1.dynamic.isadsl.co.za [196.210.138.
1]
3 22 ms 22 ms 29 ms 196.38.73.85
4 382 ms 377 ms 378 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
5 338 ms 335 ms 339 ms cdsl1-rba-vl2.ip.isnet.net [196.26.77.1]
6 334 ms 342 ms 371 ms cdsl1-ctn-cdsl1-rba.ip.isnet.net [196.38.72.159]

7 261 ms 250 ms 254 ms wa-is.isdsl.net [196.38.72.84]
8 42 ms 43 ms 44 ms wnls-cr2-vl-140.wa.co.za [41.185.1.1]
9 103 ms 82 ms 71 ms wnls-hr1-gi-9-13.wa.co.za [41.185.1.26]
10 44 ms 47 ms 49 ms 196.220.58.66

Trace complete.

C:\>tracert twitter.com

Tracing route to twitter.com [199.59.148.10]
over a maximum of 30 hops:

1 2 ms 3 ms 3 ms home.gateway.pace.net [10.0.0.2]
2 20 ms 22 ms 21 ms 196-210-138-1.dynamic.isadsl.co.za [196.210.138.
1]
3 22 ms 22 ms 22 ms 196.38.73.85
4 22 ms 25 ms 30 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
5 38 ms 28 ms 26 ms core1-pkl-tg0-7-0-0.ip.isnet.net [168.209.1.162]

6 250 ms 248 ms 217 ms 168.209.201.89
7 211 ms 205 ms 212 ms 168.209.246.3
8 204 ms 205 ms 204 ms 195.50.124.33
9 336 ms 256 ms 328 ms vl-3503-ve-117.csw1.London1.Level3.net [4.69.166
.137]
10 205 ms 207 ms 218 ms ae-1-51.edge4.London1.Level3.net [4.69.139.74]
11 204 ms 206 ms 202 ms TWITTER-INC.edge4.London1.Level3.net [212.113.14
.238]
12 284 ms 315 ms 279 ms xe-1-2-1.iad-cr2.twttr.com [199.16.159.125]
13 353 ms 353 ms 352 ms ae60.pao1-cr2.twttr.com [199.16.159.87]
14 353 ms 348 ms 349 ms ae52.smf1-er2.twttr.com [199.16.159.55]
15 357 ms 358 ms 358 ms r-199-59-148-10.twttr.com [199.59.148.10]

Trace complete.


My kids are not here, and no other computers are running ..

I dont have the energy to go thru Telkom/Web Africa ping-pong .. I have been there/done that.

Plse tell me, realistically, is there any hope, or do I just bite the bullet, and cancel ?

While I understand this is annoying, there's no need to cancel.
We've already established that there's an issue around some Western Cape locations.http://forums.webafrica.co.za/showt...dback-and-Issues?p=80296&viewfull=1#post80296

WAJeff said:
Just want to confirm things here quickly, under one post :)

We're currently investigating a 15ms - 20ms latency increase within the Western Cape area. Unfortunately we aren't able to make an exact pin-point location at the moment, however latency is seen as being increased slightly by anywhere between 15ms to 20ms. This will be from hop 2.

Anything increased from the response times mentioned above may indicate an issue with your exchange or there is activity on the line whilst running a tracert.

Will have feedback posted up here as soon as we get further updates.

We should have further feedback or hopefully a resolution by tomorrow.
All in all though, I personally think this network move has gone very smoothly considering this is the only "major" problem we've experienced here. I promise you, this is something that we're busy sorting out.
 
Last edited:
Not happy

10 meg capped account

http://www.speedtest.net/result/2540551466.png

Yesterday was better, so this is not a good start to have problems on day 2

DL is running at about 4 megs

tracert www.cnn.com

Tracing route to cnn-56m.gslb.vgtf.net [157.166.248.10]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 7 ms 4 ms 6 ms 196-210-130-1.dynamic.isadsl.co.za [196.210.130.
1]
3 16 ms 15 ms 16 ms 196.38.72.229
4 19 ms 16 ms 16 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
5 20 ms 19 ms 19 ms core2-pkl-t0-7-0-0.ip.isnet.net [168.209.1.163]

6 199 ms 199 ms 199 ms core2b-dock-tenge-0-3-0-0-126.ip.isnet.net [168.
209.201.81]
7 195 ms 195 ms 195 ms 195.50.124.33
8 286 ms 285 ms 285 ms vl-3601-ve-225.csw2.London1.Level3.net [4.69.166
.145]
9 * * * Request timed out.
10 288 ms 285 ms 315 ms ae-44-44.ebr1.NewYork1.Level3.net [4.69.137.78]

11 284 ms 284 ms 284 ms 4.69.201.62
12 283 ms 282 ms 283 ms ae-1-100.ebr1.Washington12.Level3.net [4.69.143.
213]
13 282 ms 281 ms 282 ms ae-6-6.ebr1.Atlanta2.Level3.net [4.69.148.105]
14 290 ms 290 ms 290 ms ae-1-51.edge2.Atlanta4.Level3.net [4.69.150.17]

15 * * * Request timed out.
16 * * * Request timed out.
17
 
What time are you running these downloads that are running at 4Mbps? Have you tested downloads after hours?
 
So you still have your own IPC, only for Hosting, or will these eventually be moved over to Teraco?

We already host our own servers within Teraco and these servers are completely managed by us.
 
What time are you running these downloads that are running at 4Mbps? Have you tested downloads after hours?

At the very time I made my post and have started right now again and it is running even slower (avg 320 KB/s)

Yesterday after 4 - when I started - it went at full 10 meg
 
At the very time I made my post and have started right now again and it is running even slower (avg 320 KB/s)

Yesterday after 4 - when I started - it went at full 10 meg

Me too down to about 100KB/s so about 1/4 of line speed. I hope Jeff's question regarding time does not imply full speed only after hours.
Noticed you also in durban perhaps ipc issues?

Remember if you don't cancel today you are going to be stuck with this for the next two months.
 
Last edited:
A problem ?

Jeff
Perhaps you need to look at this ?

From Telkom

Code:
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\>ping www.netgear.com

Pinging netgear.com [206.16.44.90] with 32 bytes of data:

Reply from 206.16.44.90: bytes=32 time=371ms TTL=234
Reply from 206.16.44.90: bytes=32 time=370ms TTL=234
Reply from 206.16.44.90: bytes=32 time=372ms TTL=234
Reply from 206.16.44.90: bytes=32 time=370ms TTL=234

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

C:\>ping www.cisco.com

Pinging e144.dscb.akamaiedge.net [84.53.184.170] with 32 bytes of data:

Reply from 84.53.184.170: bytes=32 time=45ms TTL=56
Reply from 84.53.184.170: bytes=32 time=45ms TTL=56
Reply from 84.53.184.170: bytes=32 time=45ms TTL=56
Reply from 84.53.184.170: bytes=32 time=46ms TTL=56

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

C:\>


From WA

Code:
C:\>ping www.netgear.com

Pinging netgear.com [206.16.44.90] with 32 bytes of data:

Reply from 206.16.44.90: bytes=32 time=348ms TTL=230
Reply from 206.16.44.90: bytes=32 time=347ms TTL=230
Reply from 206.16.44.90: bytes=32 time=349ms TTL=230
Reply from 206.16.44.90: bytes=32 time=344ms TTL=230

Ping statistics for 206.16.44.90:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 344ms, Maximum = 349ms, Average = 347ms

C:\>ping www.cisco.com

Pinging e144.dscb.akamaiedge.net [2.18.112.170] with 32 bytes of data:

Reply from 2.18.112.170: bytes=32 time=201ms TTL=54
Reply from 2.18.112.170: bytes=32 time=199ms TTL=54
Reply from 2.18.112.170: bytes=32 time=199ms TTL=54
Reply from 2.18.112.170: bytes=32 time=199ms TTL=54

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

C:\>

As you can see your akamai connection is on a different IP range and is a bit slow ? :)
 
Seems like I am being throttled during the day to 384kb speeds, can't seem to download faster than 40kbps, is this to be expected?

This is on a 1Mbps home uncapped account with a 5 star ratting still.
 
Last edited:
Yup 4Mbps account slowed down to 150KB/s max download speed. Still 5 star rating
 
account is basically dead now....... not even able to connect to chat.wage.co.za their own teamspeak server
 
Same here can't go to any websites, like 1 out of 10 works.

Experiencing loads of problems now, just restarted my router now and I can open mybb again.
 
Last edited:
Anyone have DNS problems? At least thats what I think it is.

I'm definitely not having DNS problems, everything just seems erratic. Speedtests run after one another are giving me very varying results, pings to mybroadband are 700ms, then 40ms the next minute.

I hope this is just a temporary hiccup, everything was fine yesterday.
 
Internet is very erratic.
Some sites not loading at all.
Speeds terrible.
I am on the IS backbone.
 
Top
Sign up to the MyBroadband newsletter
X