MWEB Uncapped ADSL Feedback - Part 2

Status
Not open for further replies.
gus said:
Strange latency issues: When i reset modem and change from @dslmweb.co.za to @mweb.co.za to force new IP the tracert looks fine and the latency is low:

Tracing route to 195.12.238.193 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 10 ms 9 ms 9 ms 41-133-134-1.dsl.mweb.co.za [41.133.134.1]
3 10 ms 10 ms 10 ms te1-1-0.505.cpt-ipc-1.mweb.co.za [196.28.178.178]
4 10 ms 10 ms 10 ms 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 158 ms 156 ms 159 ms 197-84-5-242.cpt.mweb.co.za [197.84.5.242]
6 159 ms 158 ms 159 ms 197-84-4-197.cpt.mweb.co.za [197.84.4.197]
7 185 ms 186 ms 188 ms 176.67.177.148
8 154 ms 154 ms 153 ms ldn-b5-link.telia.net [62.115.13.17]
9 232 ms 154 ms 153 ms ldn-bb2-link.telia.net [80.91.246.146]
10 161 ms 162 ms 161 ms prs-bb2-link.telia.net [80.91.246.177]
11 163 ms 179 ms 163 ms prs-b8-link.telia.net [213.155.131.15]


But after about 10-20min the latency deteriorates and this is what the tracert looks like:

1 1 ms <1 ms <1 ms 192.168.1.1
2 293 ms 324 ms 322 ms 41-133-134-1.dsl.mweb.co.za [41.133.134.1]
3 210 ms 322 ms 322 ms te1-1-0.505.cpt-ipc-1.mweb.co.za [196.28.178.178]
4 215 ms 324 ms 55 ms 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 453 ms 608 ms 607 ms 197-84-5-242.cpt.mweb.co.za [197.84.5.242]
6 358 ms 602 ms 606 ms 197-84-4-197.cpt.mweb.co.za [197.84.4.197]
7 359 ms 509 ms 605 ms 176.67.177.148
8 563 ms 607 ms 321 ms ldn-b5-link.telia.net [62.115.13.17]
9 558 ms 284 ms 661 ms ldn-bb2-link.telia.net [80.91.246.146]
10 214 ms 163 ms 598 ms prs-bb2-link.telia.net [80.91.246.177]
11 518 ms 607 ms 611 ms prs-b8-link.telia.net [213.155.131.15]
12


Can anyone shed some light on this?
Click to expand...

hadroncollider said:
I've been having the same damn problem for 2-3 days now. It's not my exchange, other ISPs are fine, it's just mweb doing this. It's completely random for me, and out of nowhere I'll start getting high pings to everything from 500m-2k ms for a while, then it'll disappear and come back again. Resetting my router fixes it for a while too, and then it just starts again. There have been the same complaints on their FB group by others with the EXACT same issue.
Click to expand...

Hi guys

Please can you PM me the results from the other tests you did with the other ISP accounts so that we can look further into this from our side.

Also, include your Mweb email address or username.
 
Hi MWEB Guy, my net seems to have sorted itself out for now. Thanks again for help
 
MWEB Guy said:
Hi guys

Please can you PM me the results from the other tests you did with the other ISP accounts so that we can look further into this from our side.

Also, include your Mweb email address or username.
Click to expand...

I am also experiencing this, even after changing my login realm to what you suggested yesterday. I'm also sure you had my line reset a few weeks ago to try help, but unfortunately it hasn't :(
 
Solja. said:
I am also experiencing this, even after changing my login realm to what you suggested yesterday. I'm also sure you had my line reset a few weeks ago to try help, but unfortunately it hasn't :(
Click to expand...

Afternoon Solja. please provide me trace routes to mweb.co.za and bbc.co.uk
 
Hi MWEB Guy, as discussed I ran some more tests. I used the following ISP's: MWEB Uncapped, Afrihost, Webafrica, Telkom (guest Account).

The results where all similar. After logging in with the different accounts the initial latency is low (as what I'm accustomed to), however after about 10-20min the latency increases. The only account that never displays this latency decay seems to be the Telkom guest account.

I also ran some speed test, using the saix.net speed test. The Telkom guest account has the lowest latency to the Cape Town server, and also the highest down and upload speeds. (I'll PM you some screenshots, along with the other info).

I also conducted these test at various times over the weekend to rule out any possible congestion issues. The results where the same, regardless of time of day.

TLDR: All accounts except the Telkom guest account display latency deterioration. The telkom Guest account has the highest download speed. I'm in Stellenbosch (Dalsig). This started to happen around Wednesday.

Any input, suggestions, help welcome.

Gus

Here are the tracert's: (The destination is the server I log into play Warcraft)

Afrihost, right after resetting the router...happy days:

Tracing route to 195.12.238.193 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 9 ms 9 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]
3 10 ms 11 ms 10 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 10 ms 10 ms 11 ms 41.181.184.28
5 11 ms 11 ms 11 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 175 ms 192 ms 183 ms ls-cr-2--tb-cr-1.uk-b.mtnns.net [196.44.31.113]
7 164 ms 164 ms 167 ms am-cr-1.nl--ls-cr-2.uk-a.mtnns.net [196.44.31.183]
8 163 ms 162 ms 163 ms am-tpr-1.nl--am-cr-1.nl-a.mtn.net [209.212.111.141]

Afrihost, Things going pear shaped:

Tracing route to 195.12.238.193 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 338 ms 327 ms 292 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]
3 459 ms 14 ms 10 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 250 ms 322 ms 322 ms 41.181.184.28
5 445 ms 322 ms 282 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 379 ms 604 ms 610 ms jp-nt-1--pe-ad-1-a.mtnns.net [196.44.31.113]
7 517 ms 549 ms 602 ms am-cr-1.nl--ls-cr-2.uk-a.mtnns.net [196.44.31.183]
8 600 ms 602 ms 603 ms am-tpr-1.nl--am-cr-1.nl-a.mtn.net [209.212.111.141]
9 427 ms 525 ms 603 ms xe-4-1-0.edge5.Amsterdam1.Level3.net [212.72.41.89]
10 526 ms 603 ms 496 ms


MWEB, happy days, right after router reset:

Tracing route to 195.12.238.193 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 10 ms 9 ms 9 ms 41-133-134-1.dsl.mweb.co.za [41.133.134.1]
3 10 ms 10 ms 10 ms te1-1-0.505.cpt-ipc-1.mweb.co.za [196.28.178.178]
4 10 ms 10 ms 10 ms 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 158 ms 156 ms 159 ms 197-84-5-242.cpt.mweb.co.za [197.84.5.242]
6 159 ms 158 ms 159 ms 197-84-4-197.cpt.mweb.co.za [197.84.4.197]
7 185 ms 186 ms 188 ms 176.67.177.148
8 154 ms 154 ms 153 ms ldn-b5-link.telia.net [62.115.13.17]
9 232 ms 154 ms 153 ms ldn-bb2-link.telia.net [80.91.246.146]
10 161 ms 162 ms 161 ms prs-bb2-link.telia.net [80.91.246.177]
11 163 ms 179 ms 163 ms prs-b8-link.telia.net [213.155.131.15]
12 * * * Request timed out.
13 * * * Request timed out.
14 *

MWEB Going pear shaped:

Tracing route to 195.12.238.193 over a maximum of 30 hops

1 <1 ms <1 ms 1 ms 192.168.1.1
2 290 ms 322 ms 9 ms 41-133-134-1.dsl.mweb.co.za [41.133.134.1]
3 197 ms 322 ms 324 ms te1-1-0.505.cpt-ipc-1.mweb.co.za [196.28.178.178]
4 10 ms 10 ms 10 ms 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 409 ms 158 ms 538 ms 197-84-5-242.cpt.mweb.co.za [197.84.5.242]
6 502 ms 484 ms 608 ms 197-84-4-197.cpt.mweb.co.za [197.84.4.197]
7 543 ms 654 ms 581 ms 176.67.177.148
8 560 ms 364 ms 647 ms ldn-b5-link.telia.net [62.115.13.17]
9 554 ms 609 ms 154 ms ldn-bb2-link.telia.net [80.91.246.146]
10 630 ms 612 ms 606 ms prs-bb2-link.telia.net [80.91.246.177]
11 540 ms 615 ms 614 ms prs-b8-link.telia.net [213.155.131.15]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 *


Particularly bad tracert, MWEB:

racing route to 195.12.238.193 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 1545 ms 755 ms 135 ms 41-133-134-1.dsl.mweb.co.za [41.133.134.1]
3 227 ms 322 ms 482 ms te1-1-0.505.cpt-ipc-1.mweb.co.za [196.28.178.178]
4 446 ms 482 ms 512 ms 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 709 ms 506 ms 159 ms 197-84-5-242.cpt.mweb.co.za [197.84.5.242]
6 738 ms 830 ms 558 ms 197-84-4-197.cpt.mweb.co.za [197.84.4.197]
7 159 ms 159 ms 159 ms


And then the tracert's using the Telkom guest account, rock solid to the first hop (where the latency issues manifest for the other ISP's)

Tracing route to 195.12.238.193 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 10 ms 9 ms 8 ms dsl-165-145-70-01.telkomadsl.co.za [165.145.70.1]
3 *

All the Telkom tracert's look like this, not going to duplicate them.

Here are the speedtest using saix.net. Top two screenshots are Afrihost and MWEB, last one is Telkom Guest Account.

View attachment SpeedTests.docx
 
gus said:
Hi MWEB Guy, as discussed I ran some more tests. I used the following ISP's: MWEB Uncapped, Afrihost, Webafrica, Telkom (guest Account).

The results where all similar. After logging in with the different accounts the initial latency is low (as what I'm accustomed to), however after about 10-20min the latency increases. The only account that never displays this latency decay seems to be the Telkom guest account.

I also ran some speed test, using the saix.net speed test. The Telkom guest account has the lowest latency to the Cape Town server, and also the highest down and upload speeds. (I'll PM you some screenshots, along with the other info).

I also conducted these test at various times over the weekend to rule out any possible congestion issues. The results where the same, regardless of time of day.

TLDR: All accounts except the Telkom guest account display latency deterioration. The telkom Guest account has the highest download speed. I'm in Stellenbosch (Dalsig). This started to happen around Wednesday.

Any input, suggestions, help welcome.

Gus

Here are the tracert's: (The destination is the server I log into play Warcraft)

Afrihost, right after resetting the router...happy days:

Tracing route to 195.12.238.193 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 9 ms 9 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]
3 10 ms 11 ms 10 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 10 ms 10 ms 11 ms 41.181.184.28
5 11 ms 11 ms 11 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 175 ms 192 ms 183 ms ls-cr-2--tb-cr-1.uk-b.mtnns.net [196.44.31.113]
7 164 ms 164 ms 167 ms am-cr-1.nl--ls-cr-2.uk-a.mtnns.net [196.44.31.183]
8 163 ms 162 ms 163 ms am-tpr-1.nl--am-cr-1.nl-a.mtn.net [209.212.111.141]

Afrihost, Things going pear shaped:

Tracing route to 195.12.238.193 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 338 ms 327 ms 292 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]
3 459 ms 14 ms 10 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 250 ms 322 ms 322 ms 41.181.184.28
5 445 ms 322 ms 282 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 379 ms 604 ms 610 ms jp-nt-1--pe-ad-1-a.mtnns.net [196.44.31.113]
7 517 ms 549 ms 602 ms am-cr-1.nl--ls-cr-2.uk-a.mtnns.net [196.44.31.183]
8 600 ms 602 ms 603 ms am-tpr-1.nl--am-cr-1.nl-a.mtn.net [209.212.111.141]
9 427 ms 525 ms 603 ms xe-4-1-0.edge5.Amsterdam1.Level3.net [212.72.41.89]
10 526 ms 603 ms 496 ms


MWEB, happy days, right after router reset:

Tracing route to 195.12.238.193 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 10 ms 9 ms 9 ms 41-133-134-1.dsl.mweb.co.za [41.133.134.1]
3 10 ms 10 ms 10 ms te1-1-0.505.cpt-ipc-1.mweb.co.za [196.28.178.178]
4 10 ms 10 ms 10 ms 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 158 ms 156 ms 159 ms 197-84-5-242.cpt.mweb.co.za [197.84.5.242]
6 159 ms 158 ms 159 ms 197-84-4-197.cpt.mweb.co.za [197.84.4.197]
7 185 ms 186 ms 188 ms 176.67.177.148
8 154 ms 154 ms 153 ms ldn-b5-link.telia.net [62.115.13.17]
9 232 ms 154 ms 153 ms ldn-bb2-link.telia.net [80.91.246.146]
10 161 ms 162 ms 161 ms prs-bb2-link.telia.net [80.91.246.177]
11 163 ms 179 ms 163 ms prs-b8-link.telia.net [213.155.131.15]
12 * * * Request timed out.
13 * * * Request timed out.
14 *

MWEB Going pear shaped:

Tracing route to 195.12.238.193 over a maximum of 30 hops

1 <1 ms <1 ms 1 ms 192.168.1.1
2 290 ms 322 ms 9 ms 41-133-134-1.dsl.mweb.co.za [41.133.134.1]
3 197 ms 322 ms 324 ms te1-1-0.505.cpt-ipc-1.mweb.co.za [196.28.178.178]
4 10 ms 10 ms 10 ms 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 409 ms 158 ms 538 ms 197-84-5-242.cpt.mweb.co.za [197.84.5.242]
6 502 ms 484 ms 608 ms 197-84-4-197.cpt.mweb.co.za [197.84.4.197]
7 543 ms 654 ms 581 ms 176.67.177.148
8 560 ms 364 ms 647 ms ldn-b5-link.telia.net [62.115.13.17]
9 554 ms 609 ms 154 ms ldn-bb2-link.telia.net [80.91.246.146]
10 630 ms 612 ms 606 ms prs-bb2-link.telia.net [80.91.246.177]
11 540 ms 615 ms 614 ms prs-b8-link.telia.net [213.155.131.15]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 *


Particularly bad tracert, MWEB:

racing route to 195.12.238.193 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 1545 ms 755 ms 135 ms 41-133-134-1.dsl.mweb.co.za [41.133.134.1]
3 227 ms 322 ms 482 ms te1-1-0.505.cpt-ipc-1.mweb.co.za [196.28.178.178]
4 446 ms 482 ms 512 ms 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 709 ms 506 ms 159 ms 197-84-5-242.cpt.mweb.co.za [197.84.5.242]
6 738 ms 830 ms 558 ms 197-84-4-197.cpt.mweb.co.za [197.84.4.197]
7 159 ms 159 ms 159 ms


And then the tracert's using the Telkom guest account, rock solid to the first hop (where the latency issues manifest for the other ISP's)

Tracing route to 195.12.238.193 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 10 ms 9 ms 8 ms dsl-165-145-70-01.telkomadsl.co.za [165.145.70.1]
3 *

All the Telkom tracert's look like this, not going to duplicate them.

Here are the speedtest using saix.net. Top two screenshots are Afrihost and MWEB, last one is Telkom Guest Account.

View attachment 62339
Click to expand...

Good Day Gus, some of your trace routes show a jump in latency on the second hop. This indicates that the problem may be closer to the remote end. It does show signs of possible congestion at your exchange, it could also be the remote end hardware (that normally show's on the first hop).

The guest account does not allow you to access any websites accept the saix one. Therefore your trace routes there wont really reveal anything.

Please advise which speed test result pertains to which account i.e. MWEB or Telkom guest account

Please also provide me trace routes to mweb.co.za and bbc.co.uk

I also require your MWEB account details via private message.
 
Just got home now and my line is completely dead, Kenilworth, CPT, line is syncing, but no connection at all, anyone else having problems?
 
Chiller89 said:
Just got home now and my line is completely dead, Kenilworth, CPT, line is syncing, but no connection at all, anyone else having problems?
Click to expand...

Hi Chiller89

I replied to your twitter message ;)
 
Hi Mwebguy,
My netflix stopped working a day or so ago. Works fine using Cell C. Thoughts?
 
unskinnybob said:
Hi Mwebguy,
My netflix stopped working a day or so ago. Works fine using Cell C. Thoughts?
Click to expand...

Hi

I'm not aware of anything that would cause netflix to stop working.
Have you changed anything on your side, any updates recently?
 
MwebGuy help. Im getting 4mb line speed the last couple of weeks and im on 10mb premium. Im not expecting 1mb/sec but im use to atleast 700kb/sec.
 
Hi

Could you please PM me a speed test result.
Also please include a trace route to a local site and a international site.
 
I don't think this is the right thread to post the question in, but I can't easily find the right thread.

A while back MWEB was offering Throttled uncapped @ lower rates. I just checked the MWEB website and don't see the word throttled mentioned. Have they done away with this now or is it basically "premium uncapped" = normal and "uncapped" = throttled?

Thanks.
 
Ejeckt said:
I don't think this is the right thread to post the question in, but I can't easily find the right thread.

A while back MWEB was offering Throttled uncapped @ lower rates. I just checked the MWEB website and don't see the word throttled mentioned. Have they done away with this now or is it basically "premium uncapped" = normal and "uncapped" = throttled?

Thanks.
Click to expand...

Hi

You are correct with your summary:

Standard uncapped is throttled.
Premium uncapped is not throttled.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X