MWEB Uncapped ADSL Feedback - Part 2

Status
Not open for further replies.
oh dear. I just DCed from D3 on my mweb. Did AH infect it :eek:
 
Underlying issues (aka telkom) starting to creep out of the wood? Or some other issues starting to manifest themselves now that we're saturating lines more and more?

Sigh... True or maybe some demon slipped through from the forth I've been trying to save with all these DCs :mad:
 
Hi Code-Red

As I've mentioned in my previous post, it seems as a congestion issue if you look at the 2nd hop.

Please configure your router with the following username & password: guest@telkomadsl / password: guest then provide me with test results.

Have you perhaps tried with a different ISP account already?

Same issues with a different ISP account. What can be done?

These feels: http://www.pingtest.net/result/72166492.png
 
Last edited:
Anyone know what the new 'off peak' time is these days? Heading to 10pm and still only getting half line speed on the news servers :/
 
For hotfile.com I use a web proxy on one of my own servers in the states. I hate doing it but Mweb left me with no option. Suck on my 300kb/s download from hotfile.com :p
 
My uncapped speed test results. This is the 1MB uncapped package on a 2MB line.

2303471467.png


2303496260.png


Here you can see my best attempt at streaming a video.

This was at around 10PM. Both accounts are Mweb accounts, and this was probably the most stable stream today, hovering at around the 70kB mark. It has been like this for the last 3-4 weeks, and you can see that even the capped account is unreliable and just drops down to around 70kB.

Image_3.png
 
2 Minutes past 11pm and suddenly full line speed ....... that's not cool Mweb, not cool at all.
 
Here's a tracert of when I was experiencing packet loss and high ping.

Tracing route to www.google.com [74.125.233.84]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Billion.800VGT [10.0.0.2]
2 302 ms 352 ms 327 ms 41-132-48-1.dsl.mweb.co.za [41.132.48.1]
3 385 ms 392 ms 375 ms 197-84-8-82.cpt.mweb.co.za [197.84.8.82]
4 310 ms 310 ms 325 ms 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 326 ms 365 ms 378 ms TenGigE0-7-0-3.12.cpt-p-1.mweb.co.za [196.28.178
.113]
6 324 ms 352 ms 311 ms tengig0-0-0-0.vic-p-2.mweb.co.za [197.84.4.35]
7 257 ms 256 ms 281 ms tengig0-7-0-0.vic-p-1.mweb.co.za [197.84.4.37]
8 347 ms 368 ms 328 ms tengig0-0-0.vic-pr-1.mweb.co.za [197.80.4.141]
9 375 ms 356 ms 357 ms 197-80-96-6.jhb.mweb.co.za [197.80.96.6]
10 321 ms 314 ms 341 ms 64.233.174.57
11 341 ms 293 ms 323 ms jnb01s02-in-f20.1e100.net [74.125.233.84]

Trace complete.
 
2 Minutes past 11pm and suddenly full line speed ....... that's not cool Mweb, not cool at all.

Getting the same here. Just loaded up a video, and immediate response with full line capacity.

The height of the shapping seems to come in around 8PM. Pretty blatant that it is happening on a schedule and not on actual usage.
 
I normally get full speed after 9 at night. Between 5 and 9, don't get me started. Don't give me this crap story of P2P is best effort yada yada.
On Friday last week I had full speed on torrents up to about midday.

Seems that M-Web's "Off peak" times are screwed up.
 
Here's a tracert of when I was experiencing packet loss and high ping.

Tracing route to www.google.com [74.125.233.84]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Billion.800VGT [10.0.0.2]
2 302 ms 352 ms 327 ms 41-132-48-1.dsl.mweb.co.za [41.132.48.1]
3 385 ms 392 ms 375 ms 197-84-8-82.cpt.mweb.co.za [197.84.8.82]
4 310 ms 310 ms 325 ms 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 326 ms 365 ms 378 ms TenGigE0-7-0-3.12.cpt-p-1.mweb.co.za [196.28.178
.113]
6 324 ms 352 ms 311 ms tengig0-0-0-0.vic-p-2.mweb.co.za [197.84.4.35]
7 257 ms 256 ms 281 ms tengig0-7-0-0.vic-p-1.mweb.co.za [197.84.4.37]
8 347 ms 368 ms 328 ms tengig0-0-0.vic-pr-1.mweb.co.za [197.80.4.141]
9 375 ms 356 ms 357 ms 197-80-96-6.jhb.mweb.co.za [197.80.96.6]
10 321 ms 314 ms 341 ms 64.233.174.57
11 341 ms 293 ms 323 ms jnb01s02-in-f20.1e100.net [74.125.233.84]

Trace complete.

Hi Fancy-Pants

Based on your trace results it seems as though you maybe on a congested exchange.
Hence the spike in the second hop.
 
Hi mweb guy. Can't get more then 200kbps download on the news.mweb.co.za . 4mb uncapped line here. Items are cached and i know they should be coming down fast. Please advise

C:\Users\>tracert www.google.co.za

Tracing route to www.google.co.za [74.125.233.55]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 16 ms 12 ms * 41-135-93-1.dsl.mweb.co.za [41.135.93.1]
3 12 ms 11 ms 14 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
4 15 ms 44 ms 24 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
5 25 ms 30 ms 25 ms tengig0-0-0.vic-pr-1.mweb.co.za [197.80.4.141]
6 27 ms 36 ms 27 ms 197-80-96-6.jhb.mweb.co.za [197.80.96.6]
7 30 ms 36 ms 27 ms 64.233.174.21
8 32 ms 23 ms 38 ms jnb01s01-in-f23.1e100.net [74.125.233.55]

Trace complete.

C:\Users\Jared>
 
Hi mweb guy. Can't get more then 200kbps download on the news.mweb.co.za . 4mb uncapped line here. Items are cached and i know they should be coming down fast. Please advise

C:\Users\>tracert www.google.co.za

Tracing route to www.google.co.za [74.125.233.55]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 16 ms 12 ms * 41-135-93-1.dsl.mweb.co.za [41.135.93.1]
3 12 ms 11 ms 14 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
4 15 ms 44 ms 24 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
5 25 ms 30 ms 25 ms tengig0-0-0.vic-pr-1.mweb.co.za [197.80.4.141]
6 27 ms 36 ms 27 ms 197-80-96-6.jhb.mweb.co.za [197.80.96.6]
7 30 ms 36 ms 27 ms 64.233.174.21
8 32 ms 23 ms 38 ms jnb01s01-in-f23.1e100.net [74.125.233.55]

Trace complete.

C:\Users\Jared>

Hi

I have checked your account and I see numerous disconnects on the line for today alone.
Seems as though the connection is not vry stable and that would certainly have an impact on your connection.

I would advise having a fault logged for you line so Telkom could perhaps check if there's any noise on the line.
 
Hi Mweb Guy having issues with SABnzbd, for some reason when I am setting it up it cannot connect to the mweb news server.
(10061, "Failed to connect: (10060, 'timed out') [email protected]:119") this the error that I get.

Tracing route to news.mweb.co.za [196.28.78.229]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Billion.400G [10.0.0.2]
2 9 ms 8 ms 9 ms 41-133-66-1.dsl.mweb.co.za [41.133.66.1]
3 10 ms 10 ms 10 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
4 10 ms 10 ms 10 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
5 21 ms 22 ms 21 ms tengig-3-1.vic-core-sw1.mweb.co.za [196.22.169.6
6]
6 22 ms 21 ms 22 ms tengig-3-1.vic-core-sw1.mweb.co.za [196.22.169.6
6]
7 21 ms 21 ms 23 ms news.mweb.co.za [196.28.78.229]

Trace complete.

Please could you check this out :) thanks

Never Mind, seemed to sort itself out:confused::whistle:
 
Last edited:
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X