MWEB Uncapped ADSL Feedback - Part 2

Status
Not open for further replies.
Received a list of things to check from MWEGUY after I complained about my browsing experience . .
Provide me with a trace route to a local and international site.

Then also setup your router with Telkom guest details

Username: guest@telkomadsl

Password: guest

then do a trace route to www.telkom .co.za and post the results and also do a speed test with these details on www.saix.net
Come 7 PM no problem at all . Everything stayed the same including Attenuation .It looks like it is MWEB shaping policy . Thank you MWEBGUY for helping me make a decision .
 
Received a list of things to check from MWEGUY after I complained about my browsing experience . .
Come 7 PM no problem at all . Everything stayed the same including Attenuation .It looks like it is MWEB shaping policy . Thank you MWEBGUY for helping me make a decision .

Good evening arni1954

High attenuation can cause your experience to fluctuate. In your case the attenuation is extremely high, 61.5dB.

The attenuation problem needs to be resolved first in order for us to troubleshoot anything else.
 
Anyone else in the Southern Suburbs experiencing intermittent speeds? Could this be congestion at the exchange? If so, how would something like that be resolved?
 
Anyone else in the Southern Suburbs experiencing intermittent speeds? Could this be congestion at the exchange? If so, how would something like that be resolved?

Good evening,

Your ADSL line is with MWEB, so we can log a fault for congestion with Telkom.

However Telkom will require proof.

We will need speed test readings, tracers to mweb.co.za and bbc.co.uk
 
Good evening arni1954

High attenuation can cause your experience to fluctuate. In your case the attenuation is extremely high, 61.5dB.

The attenuation problem needs to be resolved first in order for us to troubleshoot anything else.

Attenuation now is also 61.5 . Why my experience is totally different .?
 
Attenuation now is also 61.5 . Why my experience is totally different .?

Attenuation can cause your experience to fluctuate.

Have you found out why your attenuation is that high?
 
Thanks MWEB Guy for all the help so far. After testing with an Afrihost, FNB, MWEB and Axxess account, it would appear that it is a Telkough problem.... The tech from MWEB that called me was most helpful and a fault has been logged.

My experience with MWEB was fantastic, and in light of this still is. Thanks for the assistance and helping to log the tech support issue and determine it is a line fault.

Much appreciated and fantastic service so far from yourself and MWEB. I will let you know if that changes... :)
 
Thanks MWEB Guy for all the help so far. After testing with an Afrihost, FNB, MWEB and Axxess account, it would appear that it is a Telkough problem.... The tech from MWEB that called me was most helpful and a fault has been logged.

My experience with MWEB was fantastic, and in light of this still is. Thanks for the assistance and helping to log the tech support issue and determine it is a line fault.

Much appreciated and fantastic service so far from yourself and MWEB. I will let you know if that changes... :)

Good day

Thanks for the feedback, please do continue to keep me informed ;)
 
Yes I am far from the exchange .

If that's the reason, then you will suffer from a deteriorated experience no matter who your ISP is.

This is completely out of our control and our products are dependent on the Telkom infrastructure.
 
Good evening,

Your ADSL line is with MWEB, so we can log a fault for congestion with Telkom.

However Telkom will require proof.

We will need speed test readings, tracers to mweb.co.za and bbc.co.uk

Hi MWEB Guy

Here are the tracerts:

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

1 <1 ms <1 ms <1 ms login.router [10.0.0.2]
2 11 ms 10 ms 11 ms 41-132-48-1.dsl.mweb.co.za [41.132.48.1]
3 11 ms 10 ms 10 ms te1-1-0.511.cpt-ipc-1.mweb.co.za [196.28.178.202
]
4 12 ms 11 ms 9 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 16 ms 17 ms 16 ms 196.28.178.66
6 16 ms 17 ms 16 ms cte-core-sw2.vwol.net [196.41.144.35]
7 13 ms 12 ms 13 ms mweb.co.za [196.2.63.110]

Trace complete.


Tracing route to bbc.co.uk [212.58.253.67]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms login.router [10.0.0.2]
2 11 ms 13 ms 15 ms 41 [41.132.48.1]
3 15 ms * 15 ms te1 [196.28.178.202]
4 11 ms 13 ms 14 ms 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 157 ms 161 ms 161 ms TenGigE0-7-0-3.12.cpt-p-1.mweb.co.za [196.28.178
.113]
6 159 ms 159 ms * 197-84-4-193.cpt.mweb.co.za [197.84.4.193]
7 160 ms 162 ms 158 ms 176.67.177.131
8 161 ms 161 ms 192 ms xe-8-1-0.edge3.London1.Level3.net [195.50.124.13
3]
9 186 ms 191 ms 185 ms vl-3602-ve-226.csw2.London1.Level3.net [4.69.166
.149]
10 * * * Request timed out.
11 160 ms 162 ms 154 ms BBC-TECHNOL.edge4.London1.Level3.net [212.113.14
.222]
12 * * * Request timed out.
13 * * * Request timed out.
14 163 ms 158 ms 161 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
15 184 ms 185 ms 189 ms 132.185.255.156
16 163 ms 157 ms 160 ms bbc.co.uk [212.58.253.67]

Trace complete.

Could my attenuation be high? Could you perhaps recreate my port? (if that would help)
 
Last edited:
Hi Mweb Guy

Been wondering this for a while now but during the last Seacom outage we were routed through SAT3(i think) and was wondering why its latency to international was about 20-30ms faster than Seacom. Can you please explain why the back up system has better latency than the primary line?

Thanks


PS: NNTP has been running fine now
 
Hi Mweb Guy

Been wondering this for a while now but during the last Seacom outage we were routed through SAT3(i think) and was wondering why its latency to international was about 20-30ms faster than Seacom. Can you please explain why the back up system has better latency than the primary line?

Thanks


PS: NNTP has been running fine now

Hi Bar_Rat

I honestly can't answer that 1 for you.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X