MWEB Uncapped ADSL Feedback - Part 2

Status
Not open for further replies.
Billion 400G router

Microsoft Windows [Version 6.3.9431]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\Home>ping vodafone.co.uk

Pinging vodafone.co.uk [85.205.252.161] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 85.205.252.161:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\Home>ping cbs.com

Pinging cbs.com [64.30.230.36] with 32 bytes of data:
Reply from 64.30.230.36: bytes=32 time=334ms TTL=235
Reply from 64.30.230.36: bytes=32 time=333ms TTL=235
Reply from 64.30.230.36: bytes=32 time=334ms TTL=235
Reply from 64.30.230.36: bytes=32 time=334ms TTL=235

Ping statistics for 64.30.230.36:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 333ms, Maximum = 334ms, Average = 333ms

C:\Users\Home>ping hetzner.de

Pinging hetzner.de [213.133.107.227] with 32 bytes of data:
Reply from 213.133.107.227: bytes=32 time=205ms TTL=49
Reply from 213.133.107.227: bytes=32 time=205ms TTL=49
Reply from 213.133.107.227: bytes=32 time=205ms TTL=49
Reply from 213.133.107.227: bytes=32 time=205ms TTL=49

Ping statistics for 213.133.107.227:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 205ms, Maximum = 205ms, Average = 205ms

C:\Users\Home>ping 1and1.co.uk

Pinging 1and1.co.uk [212.227.126.68] with 32 bytes of data:
Reply from 212.227.126.68: bytes=32 time=211ms TTL=52
Request timed out.
Reply from 212.227.126.68: bytes=32 time=211ms TTL=52
Request timed out.

Ping statistics for 212.227.126.68:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 211ms, Maximum = 211ms, Average = 211ms

C:\Users\Home>ping fbi.gov

Pinging fbi.gov [72.21.81.85] with 32 bytes of data:
Reply from 72.21.81.85: bytes=32 time=269ms TTL=51
Reply from 72.21.81.85: bytes=32 time=269ms TTL=51
Request timed out.
Reply from 72.21.81.85: bytes=32 time=269ms TTL=51

Ping statistics for 72.21.81.85:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 269ms, Maximum = 269ms, Average = 269ms

C:\Users\Home>ping teleservices.mu
Ping request could not find host teleservices.mu. Please check the name and try
again.

C:\Users\Home>ping vogue.it

Pinging vogue.it [194.244.45.210] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 194.244.45.210:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\Home>ping einstein.br

Pinging einstein.br [200.157.195.15] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 200.157.195.15:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\Home>
 
Seriously said:
WHY? I use a old DSL 2500U.
Click to expand...

Hey Seriously, we picking up a trend with clients having problems using the DLink routers. Cannot confirm that this is the problem as yet.

Our Engineers are looking into this, as I have already provided them the information received via My BB. Will continue to provide them the information as I receive it.
 
ASUS DSL-N10

Sorry to ruin your day, but it doesn't look like you're going to be able to blame this on client hardware.
 
With Telkom guest account, speed test at SAIX

ast Result:
Download Speed: 1761 kbps (220.1 KB/sec transfer rate)
Upload Speed: 423 kbps (52.9 KB/sec transfer rate)
Latency: 17 ms
11/7/2013 11:07:04
 
Seriously said:
WHY? I use a old DSL 2500U.
Click to expand...

Hey Seriously, we picking up a trend with clients having problems using the DLink routers. Cannot confirm that this is the problem as yet. (likely not the cause)...

Our Engineers are looking into this, as I have already provided them the information received via My BB. Will continue to provide them the information as I receive it.
 
Microsoft Windows [Version 6.3.9431]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\Home>ping bbc.co.uk

Pinging bbc.co.uk [212.58.253.67] with 32 bytes of data:
Reply from 212.58.253.67: bytes=32 time=191ms TTL=113
Reply from 212.58.253.67: bytes=32 time=191ms TTL=113
Reply from 212.58.253.67: bytes=32 time=192ms TTL=113
Reply from 212.58.253.67: bytes=32 time=191ms TTL=113

Ping statistics for 212.58.253.67:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 191ms, Maximum = 192ms, Average = 191ms

C:\Users\Home>
 
Netgear router This side.

Definately not a D/Link issue just because most people have the same make router doesn't mean they will get the same problems
 
Hi all, I picked up on a number of speed related posts. I have gathered all your information provided and our engineers are currently investigating.
 
Using a Telkom Mega 200VWR Router

Code: 
$ traceroute bbc.co.uk
traceroute: Warning: bbc.co.uk has multiple addresses; using 212.58.253.67
traceroute to bbc.co.uk (212.58.253.67), 64 hops max, 52 byte packets
 1  home.gateway (10.0.0.2)  27.177 ms  0.839 ms  0.812 ms
 2  41-133-102-1.dsl.mweb.co.za (41.133.102.1)  7.791 ms  9.210 ms  9.618 ms
 3  te1-1-0.505.cpt-ipc-1.mweb.co.za (196.28.178.178)  10.016 ms  8.709 ms  8.696 ms
 4  197-84-3-2.cpt.mweb.co.za (197.84.3.2)  10.619 ms  8.899 ms
    197-84-2-2.cpt.mweb.co.za (197.84.2.2)  7.822 ms
 5  tengige0-7-0-3.12.cpt-p-1.mweb.co.za (196.28.178.113)  156.972 ms
    tengige0-0-0-2.11.cpt-p-2.mweb.co.za (196.28.178.98)  159.212 ms
    tengige0-0-0-2.11.cpt-p-1.mweb.co.za (196.28.178.97)  193.544 ms
 6  197-84-4-195.cpt.mweb.co.za (197.84.4.195)  158.377 ms
    197-84-4-32.cpt.mweb.co.za (197.84.4.32)  190.534 ms  191.335 ms
 7  176.67.177.131 (176.67.177.131)  156.182 ms
    197-84-4-195.cpt.mweb.co.za (197.84.4.195)  156.918 ms
    176.67.177.131 (176.67.177.131)  166.653 ms
 8  176.67.177.131 (176.67.177.131)  156.921 ms *  155.939 ms
 9  atos-ic-151907-ldn-b5.c.telia.net (80.239.132.142)  157.290 ms  208.367 ms *
10  * * *
11  * * *
12  * * *
13  132.185.255.156 (132.185.255.156)  191.043 ms
    ae0.er01.cwwtf.bbc.co.uk (132.185.254.93)  194.979 ms *
14  132.185.255.156 (132.185.255.156)  641.893 ms * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  *^C

Code: 
$ ping bbc.co.uk
PING bbc.co.uk (212.58.253.67): 56 data bytes
--- bbc.co.uk ping statistics ---
113 packets transmitted, 68 packets received, 39.8% packet loss
round-trip min/avg/max/stddev = 189.974/192.124/208.445/2.353 ms

Traceroute to an Amazon ec2 server in Singapore:
Code: 
$ traceroute 54.251.189.149
traceroute to 54.251.189.149 (54.251.189.149), 64 hops max, 52 byte packets
 1  home.gateway (10.0.0.2)  2.293 ms  0.831 ms  0.802 ms
 2  41-133-102-1.dsl.mweb.co.za (41.133.102.1)  7.444 ms  7.657 ms  7.822 ms
 3  197-84-8-58.cpt.mweb.co.za (197.84.8.58)  8.936 ms  10.169 ms  8.920 ms
 4  197-84-3-2.cpt.mweb.co.za (197.84.3.2)  10.321 ms
    197-84-2-2.cpt.mweb.co.za (197.84.2.2)  9.253 ms  10.090 ms
 5  tengige0-7-0-2.12.cpt-p-2.mweb.co.za (196.28.178.114)  154.438 ms
    tengige0-0-0-2.11.cpt-p-1.mweb.co.za (196.28.178.97)  193.032 ms
    tengige0-7-0-2.12.cpt-p-2.mweb.co.za (196.28.178.114)  153.747 ms
 6  197-84-4-193.cpt.mweb.co.za (197.84.4.193)  156.513 ms
    197-84-4-33.cpt.mweb.co.za (197.84.4.33)  156.179 ms  155.146 ms
 7  176.67.177.227 (176.67.177.227)  157.276 ms
    197-84-4-193.cpt.mweb.co.za (197.84.4.193)  159.286 ms
    176.67.177.227 (176.67.177.227)  156.620 ms
 8  176.67.177.227 (176.67.177.227)  160.133 ms *  701.976 ms
 9  vl-3602-ve-226.csw2.london1.level3.net (4.69.166.149)  748.251 ms
    vl-3504-ve-118.csw1.london1.level3.net (4.69.166.141)  211.335 ms *
10  * vl-3504-ve-118.csw1.london1.level3.net (4.69.166.141)  192.518 ms *
11  * * *
12  * xe-6-0-3.r23.londen03.uk.bb.gin.ntt.net (129.250.6.54)  157.008 ms *
13  ae-3.r22.amstnl02.nl.bb.gin.ntt.net (129.250.5.198)  170.071 ms
    xe-6-0-3.r23.londen03.uk.bb.gin.ntt.net (129.250.6.54)  154.980 ms
    ae-3.r22.amstnl02.nl.bb.gin.ntt.net (129.250.5.198)  168.583 ms
14  ae-3.r22.amstnl02.nl.bb.gin.ntt.net (129.250.5.198)  167.746 ms
    as-2.r22.tokyjp01.jp.bb.gin.ntt.net (129.250.4.64)  560.170 ms  511.696 ms
15  as-2.r22.tokyjp01.jp.bb.gin.ntt.net (129.250.4.64)  411.740 ms
    as-6.r21.sngpsi02.sg.bb.gin.ntt.net (129.250.5.157)  612.942 ms
    as-2.r22.tokyjp01.jp.bb.gin.ntt.net (129.250.4.64)  512.180 ms
16  ae-4.r20.sngpsi02.sg.bb.gin.ntt.net (129.250.6.100)  716.464 ms
    as-6.r21.sngpsi02.sg.bb.gin.ntt.net (129.250.5.157)  615.118 ms *
17  ae-4.r20.sngpsi02.sg.bb.gin.ntt.net (129.250.6.100)  488.187 ms *
    ae-0.amazon-sg-3.sngpsi02.sg.bb.gin.ntt.net (116.51.17.130)  572.043 ms
18  * 203.83.223.8 (203.83.223.8)  633.370 ms
    ae-0.amazon-sg-3.sngpsi02.sg.bb.gin.ntt.net (116.51.17.130)  627.353 ms
19  203.83.223.31 (203.83.223.31)  614.468 ms *  645.902 ms
20  * 203.83.223.31 (203.83.223.31)  449.397 ms *
21  * * *
22  * * *
23  *^C

Code: 
$ traceroute linode.com
traceroute: Warning: linode.com has multiple addresses; using 72.14.180.202
traceroute to linode.com (72.14.180.202), 64 hops max, 52 byte packets
 1  home.gateway (10.0.0.2)  1.301 ms  0.843 ms  0.793 ms
 2  41-133-102-1.dsl.mweb.co.za (41.133.102.1)  8.672 ms  8.489 ms  8.315 ms
 3  197-84-8-10.cpt.mweb.co.za (197.84.8.10)  8.941 ms  9.831 ms  10.749 ms
 4  197-84-3-2.cpt.mweb.co.za (197.84.3.2)  9.839 ms
    197-84-2-2.cpt.mweb.co.za (197.84.2.2)  9.212 ms
    197-84-3-2.cpt.mweb.co.za (197.84.3.2)  10.615 ms
 5  tengige0-0-0-2.11.cpt-p-2.mweb.co.za (196.28.178.98)  156.538 ms
    tengige0-0-0-2.11.cpt-p-1.mweb.co.za (196.28.178.97)  192.753 ms
    tengige0-7-0-2.12.cpt-p-2.mweb.co.za (196.28.178.114)  154.443 ms
 6  197-84-4-193.cpt.mweb.co.za (197.84.4.193)  158.170 ms
    197-84-4-195.cpt.mweb.co.za (197.84.4.195)  158.832 ms  157.552 ms
 7  176.67.177.131 (176.67.177.131)  157.609 ms  154.064 ms  155.757 ms
 8  176.67.177.133 (176.67.177.133)  308.797 ms
    176.67.177.228 (176.67.177.228)  155.417 ms
    176.67.177.133 (176.67.177.133)  230.555 ms
 9  bbr02.lon01.networklayer.com (195.66.237.183)  157.081 ms
    bbr01.lon01.networklayer.com (195.66.225.183)  154.521 ms
    bbr02.lon01.networklayer.com (195.66.237.183)  164.878 ms
10  * * *
11  * * ae1.bbr01.eq01.chi01.networklayer.com (173.192.18.132)  441.776 ms
12  ae20.bbr01.eq01.dal03.networklayer.com (173.192.18.136)  300.160 ms  489.987 ms  300.666 ms
13  po31.dsr02.dllstx3.networklayer.com (173.192.18.227)  314.282 ms
    po31.dsr01.dllstx3.networklayer.com (173.192.18.225)  457.758 ms  444.067 ms
14  po31.dsr01.dllstx2.networklayer.com (70.87.255.66)  263.971 ms  268.770 ms
    po32.dsr02.dllstx2.networklayer.com (70.87.255.70)  418.134 ms
15  po1.car01.dllstx2.networklayer.com (70.87.254.74)  270.994 ms
    po2.car01.dllstx2.networklayer.com (70.87.254.78)  425.340 ms
    po1.car01.dllstx2.networklayer.com (70.87.254.74)  451.368 ms
16  router1-dal.linode.com (67.18.7.90)  272.455 ms  273.121 ms  270.987 ms
17  www-loadbal1.linode.com (72.14.180.202)  371.502 ms  266.362 ms  380.664 ms

Code: 
$ ping linode.com
PING linode.com (72.14.180.202): 56 data bytes
--- linode.com ping statistics ---
132 packets transmitted, 132 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 270.802/326.508/477.115/75.684 ms
 
@MWEBGuy. Interesting you mentioned D-Link routers. I changed to a Netgear router in my office from a D-Link DSL-2640U. I used to get intermittent problems with it. It would show that I was connected but there was no traffic going through, when this happened the router would not have an Gateway IP Address (would just be blank). I would have to reboot the router and it would run fine till it happened again.
 
MWEB Guy said:
Hey Seriously, we picking up a trend with clients having problems using the DLink routers. Cannot confirm that this is the problem as yet. (likely not the cause)...

Our Engineers are looking into this, as I have already provided them the information received via My BB. Will continue to provide them the information as I receive it.
Click to expand...

Thanks. I have no speed problems with the same Dlink on other networks like Afrihots. ;)

BTW, just ask your Engineers to fix their cycling shaping system and you will have a good network of sorts.
 
Seriously said:
Thanks. I have no speed problems with the same Dlink on other networks like Afrihots. ;)

BTW, just ask your Engineers to fix their cycling shaping system and you will have a good network of sorts.
Click to expand...

I am with Afrihost and have been having speed related issues since yesterday.
My modem is syncing at 2MB to my exchange but download speeds are no highter than 20 or 30k sec, web browsing is super slow.
I am using a Netgear modem.

No one seems to know of any issues, this must be larger than an ISP issue, Telkom must have a problem.
 
Been having issues since last night. Using a dlink -_-. I know my exchange hop is high, but that doesn't explain why local stuff still works slow but international is basically dead


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

1 2 ms 1 ms 1 ms 10.0.0.2
2 284 ms 248 ms 218 ms 41-133-72-1.dsl.mweb.co.za [41.133.72.1]
3 214 ms 259 ms 269 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
4 277 ms 332 ms 293 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
5 310 ms 299 ms 333 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
6 284 ms 318 ms 288 ms 196.28.178.66
7 202 ms 201 ms 197 ms cte-core-sw2.vwol.net [196.41.144.35]
8 1175 ms 320 ms 315 ms www.mweb.co.za [196.2.63.110]

Trace complete.


Tracing route to www.bbc.net.uk [212.58.244.70]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.0.0.2
2 261 ms 307 ms 331 ms 41-133-72-1.dsl.mweb.co.za [41.133.72.1]
3 281 ms 269 ms 292 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
4 313 ms 285 ms 310 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
5 488 ms 489 ms 508 ms 176.67.177.227
6 465 ms 528 ms * ldn-b5-link.telia.net [62.115.13.13]
7 408 ms 410 ms 438 ms atos-ic-151907-ldn-b5.c.telia.net [80.239.132.14
2]
8 * * * Request timed out.
9 346 ms 376 ms 430 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
10 487 ms * 468 ms 132.185.255.149
11 525 ms 490 ms 499 ms www.bbc.co.uk [212.58.244.70]

Trace complete.



 
MWEB Guy said:
Hi all, I picked up on a number of speed related posts. I have gathered all your information provided and our engineers are currently investigating.
Click to expand...

F1ve_Claw said:
Been having issues since last night. Using a dlink -_-. I know my exchange hop is high, but that doesn't explain why local stuff still works slow but international is basically dead


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

1 2 ms 1 ms 1 ms 10.0.0.2
2 284 ms 248 ms 218 ms 41-133-72-1.dsl.mweb.co.za [41.133.72.1]
3 214 ms 259 ms 269 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
4 277 ms 332 ms 293 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
5 310 ms 299 ms 333 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
6 284 ms 318 ms 288 ms 196.28.178.66
7 202 ms 201 ms 197 ms cte-core-sw2.vwol.net [196.41.144.35]
8 1175 ms 320 ms 315 ms www.mweb.co.za [196.2.63.110]

Trace complete.


Tracing route to www.bbc.net.uk [212.58.244.70]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.0.0.2
2 261 ms 307 ms 331 ms 41-133-72-1.dsl.mweb.co.za [41.133.72.1]
3 281 ms 269 ms 292 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
4 313 ms 285 ms 310 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
5 488 ms 489 ms 508 ms 176.67.177.227
6 465 ms 528 ms * ldn-b5-link.telia.net [62.115.13.13]
7 408 ms 410 ms 438 ms atos-ic-151907-ldn-b5.c.telia.net [80.239.132.14
2]
8 * * * Request timed out.
9 346 ms 376 ms 430 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
10 487 ms * 468 ms 132.185.255.149
11 525 ms 490 ms 499 ms www.bbc.co.uk [212.58.244.70]

Trace complete.



Click to expand...

Hi F1ve_Claw

We are investigating the speed related posts.
 
Have found that swopping from username@mweb to username@dslmweb has made a small improvement. What is the primary / secondary DNS meant to be?
 
F1ve_Claw said:
Have found that swopping from username@mweb to username@dslmweb has made a small improvement. What is the primary / secondary DNS meant to be?
Click to expand...


Hi

It should be on "obtain automatically" as we provide the DNS's
 
MWEB Guy said:
Hey Seriously, we picking up a trend with clients having problems using the DLink routers. Cannot confirm that this is the problem as yet.

Our Engineers are looking into this, as I have already provided them the information received via My BB. Will continue to provide them the information as I receive it.
Click to expand...

Using a Billion Router here.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X