MWEB Uncapped ADSL Feedback - Part 3

TheLaggingShaman said:
It is fine now, but the severe latency occurred twice last night/early morning. A friend also in CPT (and on MWEB) reported the same problem at the same time.
Click to expand...

Thanks for the feedback, let me know if the problem re-occurs
 
Hey MWEB Guy

wrt below, it appears there is something wrong around hop 5 or so. The IP still indicates a cpt.mweb server but for some reason the ping has jumped massively along with a few timeouts. Advice?

Thanks!

traceroute to www.tumblr.com (66.6.42.20), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 4.616 ms 2.069 ms 1.942 ms
2 41-133-108-1.dsl.mweb.co.za (41.133.108.1) 7.606 ms 7.877 ms 7.914 ms
3 197-84-96-210.cpt.mweb.co.za (197.84.96.210) 9.614 ms 9.336 ms 8.852 ms
4 197-84-2-2.cpt.mweb.co.za (197.84.2.2) 9.799 ms
197-84-3-2.cpt.mweb.co.za (197.84.3.2) 9.486 ms
197-84-2-2.cpt.mweb.co.za (197.84.2.2) 8.998 ms
5 * 197-84-5-241.cpt.mweb.co.za (197.84.5.241) 199.197 ms *
6 197-84-4-32.cpt.mweb.co.za (197.84.4.32) 200.000 ms
197-84-4-33.cpt.mweb.co.za (197.84.4.33) 187.009 ms 191.127 ms
7 * 197-84-4-201.cpt.mweb.co.za (197.84.4.201) 203.775 ms
197-84-4-195.cpt.mweb.co.za (197.84.4.195) 244.038 ms
8 be-69-thd-p-1.mweb.co.za (176.67.177.161) 187.599 ms * 213.452 ms
9 176.67.177.131 (176.67.177.131) 181.951 ms
176.67.177.148 (176.67.177.148) 193.058 ms *
10 xe-8-1-0.edge3.london1.level3.net (195.50.124.133) 183.865 ms 194.090 ms 198.750 ms
11 * vl-3608-ve-232.csw2.london1.level3.net (4.69.166.30) 272.374 ms 319.583 ms
12 ae-58-223.ebr2.london1.level3.net (4.69.153.137) 297.355 ms
ae-59-224.ebr2.london1.level3.net (4.69.153.141) 245.523 ms
ae-58-223.ebr2.london1.level3.net (4.69.153.137) 336.185 ms
13 ae-43-43.ebr1.newyork1.level3.net (4.69.137.74) 306.836 ms
ae-42-42.ebr1.newyork1.level3.net (4.69.137.70) 282.186 ms 307.644 ms
14 ae-91-91.csw4.newyork1.level3.net (4.69.134.78) 280.731 ms 258.279 ms
ae-81-81.csw3.newyork1.level3.net (4.69.134.74) 231.491 ms
15 ae-82-82.ebr2.newyork1.level3.net (4.69.148.41) 237.075 ms
ae-72-72.ebr2.newyork1.level3.net (4.69.148.37) 337.591 ms
ae-82-82.ebr2.newyork1.level3.net (4.69.148.41) 252.868 ms
16 ae-2-2.ebr1.newark1.level3.net (4.69.132.98) 235.235 ms 234.097 ms 280.511 ms
17 ae-1-51.edge3.newark1.level3.net (4.69.156.11) 307.298 ms 233.102 ms 231.380 ms
18 tumblr-inc.edge3.newark1.level3.net (4.30.129.254) 268.494 ms 307.015 ms 306.886 ms
19 66.6.42.20 (66.6.42.20) 307.202 ms 249.067 ms 307.050 ms
 
I've been getting quite a bit of international packet loss on MWEB international for the last 30min. I ran a pingplotter graph and it's basically red across the board as soon as it crosses to international - 44 to 60% (sometimes higher) loss.

I've connected to my Afrihost backup account and all is fine with international connectivity there - so I reckon it's localized to MWEB.
 
If you could reply to my PM ASAP Mweb, I need to sort it out as soon as possible before I leave work today.

Edit: NVM sorted the problem.
 
Last edited:
International's crawling

Tracing route to star.c10r.facebook.com [31.13.72.65]
over a maximum of 30 hops:

1 2 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 5 ms 5 ms 5 ms 197-87-135-1.cpt.mweb.co.za [197.87.135.1]
3 7 ms 6 ms 6 ms 197-84-96-162.cpt.mweb.co.za [197.84.96.162]
4 7 ms 7 ms 6 ms 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 177 ms 171 ms 174 ms 197-84-5-241.cpt.mweb.co.za [197.84.5.241]
6 186 ms 185 ms * 197-84-4-32.cpt.mweb.co.za [197.84.4.32]
7 * 183 ms * 197-84-4-197.cpt.mweb.co.za [197.84.4.197]
8 192 ms 185 ms 192 ms be-69-thd-p-2.mweb.co.za [176.67.177.162]
9 * * * Request timed out.
10 171 ms 167 ms 171 ms 176.67.177.228
11 * 173 ms 166 ms linx.br02.lhr1.tfbnw.net [195.66.225.121]
12 167 ms 182 ms * ae2.bb04.lhr2.tfbnw.net [31.13.30.176]
13 188 ms 189 ms 189 ms ae1.pr01.lhr2.tfbnw.net [31.13.30.199]
14 * 172 ms 169 ms po126.msw01.05.lhr2.tfbnw.net [74.119.77.53]
15 * 189 ms 189 ms edge-star-shv-05-lhr2.facebook.com [31.13.72.65]

Trace complete.

Page loads currently very slow/broken to impossible on any intl web sites
 
Experiencing the same packet loss issues as last night - and the same as a few weeks before. Again, not having this problem with my backup Afrihost account.

This has been quite a frequent occurrence for MWEB lately, and I'm wondering if and how they plan to tackle this problem. I'm not really fond of ISP-jumping, but it is getting to the point where it becomes rather disruptive. For reference:

Doing a 8.8.8.8 trace route: Hops 1 to 8 is normal (up to 197.80.96.6) with latency around 37-50ms and no packet loss. From hop 9 (66.249.95.8) onward latency appears normal at around 208-226ms, but packet loss is really bad - between 34% to 66%, making even normal web browsing sluggish and unresponsive (no to mention VOIP or video streaming).
 
FraserBlade said:
Experiencing the same packet loss issues as last night - and the same as a few weeks before. Again, not having this problem with my backup Afrihost account.

This has been quite a frequent occurrence for MWEB lately, and I'm wondering if and how they plan to tackle this problem. I'm not really fond of ISP-jumping, but it is getting to the point where it becomes rather disruptive. For reference:

Doing a 8.8.8.8 trace route: Hops 1 to 8 is normal (up to 197.80.96.6) with latency around 37-50ms and no packet loss. From hop 9 (66.249.95.8) onward latency appears normal at around 208-226ms, but packet loss is really bad - between 34% to 66%, making even normal web browsing sluggish and unresponsive (no to mention VOIP or video streaming).
Click to expand...

For interest sake, could you post a tracert on the forum?
 
Dames said:
Hey MWEB Guy

wrt below, it appears there is something wrong around hop 5 or so. The IP still indicates a cpt.mweb server but for some reason the ping has jumped massively along with a few timeouts. Advice?

Thanks!

traceroute to www.tumblr.com (66.6.42.20), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 4.616 ms 2.069 ms 1.942 ms
2 41-133-108-1.dsl.mweb.co.za (41.133.108.1) 7.606 ms 7.877 ms 7.914 ms
3 197-84-96-210.cpt.mweb.co.za (197.84.96.210) 9.614 ms 9.336 ms 8.852 ms
4 197-84-2-2.cpt.mweb.co.za (197.84.2.2) 9.799 ms
197-84-3-2.cpt.mweb.co.za (197.84.3.2) 9.486 ms
197-84-2-2.cpt.mweb.co.za (197.84.2.2) 8.998 ms
5 * 197-84-5-241.cpt.mweb.co.za (197.84.5.241) 199.197 ms *
6 197-84-4-32.cpt.mweb.co.za (197.84.4.32) 200.000 ms
197-84-4-33.cpt.mweb.co.za (197.84.4.33) 187.009 ms 191.127 ms
7 * 197-84-4-201.cpt.mweb.co.za (197.84.4.201) 203.775 ms
197-84-4-195.cpt.mweb.co.za (197.84.4.195) 244.038 ms
8 be-69-thd-p-1.mweb.co.za (176.67.177.161) 187.599 ms * 213.452 ms
9 176.67.177.131 (176.67.177.131) 181.951 ms
176.67.177.148 (176.67.177.148) 193.058 ms *
10 xe-8-1-0.edge3.london1.level3.net (195.50.124.133) 183.865 ms 194.090 ms 198.750 ms
11 * vl-3608-ve-232.csw2.london1.level3.net (4.69.166.30) 272.374 ms 319.583 ms
12 ae-58-223.ebr2.london1.level3.net (4.69.153.137) 297.355 ms
ae-59-224.ebr2.london1.level3.net (4.69.153.141) 245.523 ms
ae-58-223.ebr2.london1.level3.net (4.69.153.137) 336.185 ms
13 ae-43-43.ebr1.newyork1.level3.net (4.69.137.74) 306.836 ms
ae-42-42.ebr1.newyork1.level3.net (4.69.137.70) 282.186 ms 307.644 ms
14 ae-91-91.csw4.newyork1.level3.net (4.69.134.78) 280.731 ms 258.279 ms
ae-81-81.csw3.newyork1.level3.net (4.69.134.74) 231.491 ms
15 ae-82-82.ebr2.newyork1.level3.net (4.69.148.41) 237.075 ms
ae-72-72.ebr2.newyork1.level3.net (4.69.148.37) 337.591 ms
ae-82-82.ebr2.newyork1.level3.net (4.69.148.41) 252.868 ms
16 ae-2-2.ebr1.newark1.level3.net (4.69.132.98) 235.235 ms 234.097 ms 280.511 ms
17 ae-1-51.edge3.newark1.level3.net (4.69.156.11) 307.298 ms 233.102 ms 231.380 ms
18 tumblr-inc.edge3.newark1.level3.net (4.30.129.254) 268.494 ms 307.015 ms 306.886 ms
19 66.6.42.20 (66.6.42.20) 307.202 ms 249.067 ms 307.050 ms
Click to expand...

I will gladly look into this.

Provide me with a ping and speed test result
 
Hi Mweb Guy,
Spoke to telkom this morning technitian tells me he finds no problem on the line line looks fine by him. Still sti with SNR of up 10 and down 12. perhaps we can test it at 6mb again and see if it works now?
Past week was stable.
 
Vl@d said:
Hi Mweb Guy,
Spoke to telkom this morning technitian tells me he finds no problem on the line line looks fine by him. Still sti with SNR of up 10 and down 12. perhaps we can test it at 6mb again and see if it works now?
Past week was stable.
Click to expand...

I have now set the line to 6Mb, give it a few minutes then restart your router and test
 
Hi Mweb Guy,

Nope problems are back, back to SNR to 6 better to move me back to 4mb.
 
Hi Mweb Guy can I test the 6mb line till Tuesday?
Didn't have dsl dropping as yet. Lag seems bareable when it hits.
I don't want to lose the rolling cap limit of the 6mb line if possible.
 
Vl@d said:
Hi Mweb Guy can I test the 6mb line till Tuesday?
Didn't have dsl dropping as yet. Lag seems bareable when it hits.
I don't want to lose the rolling cap limit of the 6mb line if possible.
Click to expand...


Keep using and let me know if your experience deteriorates
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X