South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Tracing route to aviation.weathersa.co.za [196.15.254.131]
1 1 ms <10 ms <10 ms home.gateway [192.168.1.254]
2 6 ms 6 ms 7 ms 41-132-48-1.dsl.mweb.co.za [41.132.48.1]
3 9 ms 8 ms 9 ms Te1-1-0.502.cpt-ipc-1.mweb.co.za [196.28.178.166]
4 9 ms 9 ms 8 ms Vlan92.cpt-hscore-1.mweb.co.za [196.28.179.11]
5 10 ms 11 ms 10 ms TenGigE0-2-0-0.11.cpt-up-1.mweb.co.za [196.28.178.97]
6 160 ms 160 ms 161 ms pos0-0-3-0.lon-up-1.mweb.co.za [196.22.164.2]
7 160 ms 161 ms 161 ms 149.6.98.5
8 161 ms 161 ms 161 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
9 160 ms 161 ms 161 ms te1-2.mpd01.lon01.atlas.cogentco.com [130.117.3.225]
10 161 ms 161 ms 161 ms 149.6.2.194
11 357 ms 350 ms 351 ms 196.43.39.146
12 355 ms 356 ms 356 ms 196.43.11.234
13 391 ms 388 ms 411 ms 196.43.39.146
14 380 ms 379 ms 378 ms 196.43.11.234
I am in Jhb and get the same result for aviation.weathersa.co.za.
Edit: I get the same result from my IS fibre connection at work, so the problem is not limited to MWEB.
Are any MWeb users (particulary in CT) having problems connecting to the website aviation.weathersa.co.za? The routing goes via London, then ends in an infinite loop. Been like this since 8am this morning.
Code:Tracing route to aviation.weathersa.co.za [196.15.254.131] 1 1 ms <10 ms <10 ms home.gateway [192.168.1.254] 2 6 ms 6 ms 7 ms 41-132-48-1.dsl.mweb.co.za [41.132.48.1] 3 9 ms 8 ms 9 ms Te1-1-0.502.cpt-ipc-1.mweb.co.za [196.28.178.166] 4 9 ms 9 ms 8 ms Vlan92.cpt-hscore-1.mweb.co.za [196.28.179.11] 5 10 ms 11 ms 10 ms TenGigE0-2-0-0.11.cpt-up-1.mweb.co.za [196.28.178.97] 6 160 ms 160 ms 161 ms pos0-0-3-0.lon-up-1.mweb.co.za [196.22.164.2] 7 160 ms 161 ms 161 ms 149.6.98.5 8 161 ms 161 ms 161 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165] 9 160 ms 161 ms 161 ms te1-2.mpd01.lon01.atlas.cogentco.com [130.117.3.225] 10 161 ms 161 ms 161 ms 149.6.2.194 11 357 ms 350 ms 351 ms 196.43.39.146 12 355 ms 356 ms 356 ms 196.43.11.234 13 391 ms 388 ms 411 ms 196.43.39.146 14 380 ms 379 ms 378 ms 196.43.11.234
I am in Durbs, and got the same loped result. Something not good there.
Tracing route to south-african-weather-services-gw.telkom-ipnet.co.za [196.25.5.222]
over a maximum of 30 hops:
1 <10 ms <10 ms <10 ms home.gateway [192.168.1.254]
2 6 ms 7 ms 7 ms 41-132-48-1.dsl.mweb.co.za [41.132.48.1]
3 9 ms 8 ms 9 ms Te1-1-0.511.cpt-ipc-1.mweb.co.za [196.28.178.202]
4 8 ms 9 ms 9 ms Vlan92.cpt-hscore-1.mweb.co.za [196.28.179.11]
5 12 ms 9 ms 10 ms TenGigE0-2-0-0.11.cpt-up-1.mweb.co.za [196.28.178.97]
6 160 ms 160 ms 160 ms pos0-0-3-0.lon-up-1.mweb.co.za [196.22.164.2]
7 294 ms 216 ms 224 ms 149.6.98.5
8 161 ms 289 ms 252 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
9 161 ms 161 ms 161 ms te1-2.mpd01.lon01.atlas.cogentco.com [130.117.3.225]
10 160 ms 161 ms 161 ms 149.6.2.194
11 249 ms 250 ms 250 ms 196.43.18.201
12 250 ms 250 ms 250 ms ash-ip-dir-equinix-ge-1-0-2.telkom-ipnet.co.za [196.43.9.166]
13 251 ms 250 ms 249 ms ash-ip-dir-equinix.telkom-ipnet.co.za [196.43.9.245]
14 408 ms 407 ms 410 ms 196.43.18.133
15 424 ms 424 ms 423 ms 196.43.39.150
16 686 ms 693 ms 640 ms south-african-weather-services-gw.telkom-ipnet.co.za [196.25.5.222]
Trace complete.
port recreate helped![]()
jitter is back to normal.
I'm done with MWEB! After a month of dealing with mweb ops nothing has changed... Constant blank page loads, constant timeouts, pathetic speeds. I've had telkom recreate my port nearly 10 times by now, i've tried 3 routers. I've had it. I'm cancelling monday morning. All I got told by mweb ops is that my attenuation is really high, its always been high and I've never had any problems before the start of this year. You know what I just think my account is just shaped to hell and back, which is weird since I'm not a super heavy downloader, my usage is around 70GB a month.
I'm on a capped afrihost account now and I havent had a single damn issue the whole time i've been on it, I'm torrenting and browsing at the same time and its faster than jsut browsing alone with the mweb account. My torrent speeds are 300+ whereas i couldnt even get 100 with mweb. Streaming youtube vids actually works and wow I can actually log into steam and download at full speed...
When I first signed up MWEB was great, its was perfect for what I needed too bad like everything else in SA, its gone to ****. I'm done...
Hi Coldon
I can assure you that MWEB do not shaped individual customers, shaping changes at different times of the day and is dynamic based on the demand on the network.
Please allow me to arrange for our specialist to contact and assist you, it might be possible that we have overlooked something. We care about our customers and would not want to loose you.
Pleas confirm if I can go ahead and schedule the call for tomorrow.
Kind regards
MWEB Operations
Morning 7th day adventist church, are you only encoutnering speed problems when streaming video? Also please PM me your MWEB account details.
How do you do that? *edit* I mean the port recreate.
For the past couple days I've been getting packet loss. My initial suspicion was that it was Telkom, so I phoned them up and got them to check everything out. I was guessing line damage or congestion/damage at the exchange. They replaced a few things, but my line and exchange is in excellent condition (a rare situation indeed). I'm also only one of two 4mb users at my exchange, so its not a congestion problem.
Its an on and off problem, some nights its fine, some nights it rears it's ugly head, but it always starts 8pm+ and stops at about 5am-9am. When it does rear its head, anything latency sensitive craps out, huge 10-15 second spikes, then continues normally, then spikes out of control agian.
Eg.
ping www.mweb.co.za -t
Pinging www.mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=13ms TTL=121
Reply from 196.2.63.110: bytes=32 time=12ms TTL=121
Reply from 196.2.63.110: bytes=32 time=12ms TTL=121
Reply from 196.2.63.110: bytes=32 time=12ms TTL=121
Reply from 196.2.63.110: bytes=32 time=11ms TTL=121
Reply from 196.2.63.110: bytes=32 time=13ms TTL=121
Reply from 196.2.63.110: bytes=32 time=12ms TTL=121
Reply from 196.2.63.110: bytes=32 time=12ms TTL=121
Reply from 196.2.63.110: bytes=32 time=12ms TTL=121
Request timed out.
Reply from 196.2.63.110: bytes=32 time=12ms TTL=121
Reply from 196.2.63.110: bytes=32 time=12ms TTL=121
Reply from 196.2.63.110: bytes=32 time=12ms TTL=121
Reply from 196.2.63.110: bytes=32 time=16ms TTL=121
Reply from 196.2.63.110: bytes=32 time=12ms TTL=121
Request timed out.
Reply from 196.2.63.110: bytes=32 time=12ms TTL=121
Ping statistics for 196.2.63.110:
Packets: Sent = 17, Received = 15, Lost = 2 (11% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 16ms, Average = 12ms
I'm trying to activate an Afrihost 1GB prepaid account to test on there to see if I can replicate the problem, they taking a while though with their whole ID verification process. Irritating how they only start this process after you've paid, anyway.
Obviously, this could still very well be on Telkom's end, but I'm starting to suspect it might, just might be something going on with Mweb. I'm in Cape Town, Bellville, Ridgeworth.
Edit: My line attenuation and noise margin is also good. 30db and 21db.
Edit2: Just got an Axxess account activated, stopped my router from dialing out and dialed the connection out from my machine. Still packet loss. In otherwords, *uck you Telkom. Guess I need to start harrassing the hell out of them again, this time with more rage.