MWEB Uncapped ADSL Feedback - Part 2

Status
Not open for further replies.
ichigo said:
Still very slow

Start Time: 21:48:59
End time: 21:49:13
IP Address: 197.87.122.139
Download Size: 409600 bytes
Time Delta: 14.043021917343 seconds
Download Speed: 28 KBytes/s
Line Speed: 224 kbits/s

Edit: Back to normal now

Start Time: 22:06:20
End time: 22:06:23
IP Address: 197.87.122.139
Download Size: 409600 bytes
Time Delta: 3.1185500621796 seconds
Download Speed: 128 KBytes/s
Line Speed: 1024 kbits/s

http://www.speedtest.net/result/2198146021.png

Downloads back to normal also and browsing and strangely after 10 pm so what was wrong?
Click to expand...

Good Morning, thanks for the feedback ichigo. I'm not sure what caused the problem, please let me know if you encounter the problem again.
 
Well I for one am glad to see you working on a public holiday MWEB Guy. Whether you actually are a singular person or a front for various support staff, I appreciate it. Just thought I'd say that. And no I could not resist the sig :D
 
rambo919 said:
Well I for one am glad to see you working on a public holiday MWEB Guy. Whether you actually are a singular person or a front for various support staff, I appreciate it. Just thought I'd say that. And no I could not resist the sig :D
Click to expand...

MOrning.. LOL :D

Thanks for the laugh and its always a pleasure...
 
Very Very Slow Here with dropped packets.
Second day running that throughput drops to almost 0 during the day. Router restart was done. International response non existent. Pinging mweb.co.za shows frequent dropped packets, with low ping times.

Reply from 196.2.63.110: bytes=32 time=9ms TTL=122
Reply from 196.2.63.110: bytes=32 time=8ms TTL=122
Reply from 196.2.63.110: bytes=32 time=8ms TTL=122
Reply from 196.2.63.110: bytes=32 time=10ms TTL=122
Request timed out.
Request timed out.
Reply from 196.2.63.110: bytes=32 time=8ms TTL=122
Request timed out.
Reply from 196.2.63.110: bytes=32 time=9ms TTL=122
Reply from 196.2.63.110: bytes=32 time=9ms TTL=122
Reply from 196.2.63.110: bytes=32 time=9ms TTL=122
Reply from 196.2.63.110: bytes=32 time=9ms TTL=122
Reply from 196.2.63.110: bytes=32 time=10ms TTL=122
Reply from 196.2.63.110: bytes=32 time=8ms TTL=122
Reply from 196.2.63.110: bytes=32 time=9ms TTL=122
Reply from 196.2.63.110: bytes=32 time=9ms TTL=122
Request timed out.
Reply from 196.2.63.110: bytes=32 time=8ms TTL=122
Reply from 196.2.63.110: bytes=32 time=9ms TTL=122
Reply from 196.2.63.110: bytes=32 time=9ms TTL=122

My line and account was recently upgraded to 2mb. Throughput was perfect early this morning and late last night.
 
mack_again said:
Very Very Slow Here with dropped packets.
Second day running that throughput drops to almost 0 during the day. Router restart was done. International response non existent. Pinging mweb.co.za shows frequent dropped packets, with low ping times.

Reply from 196.2.63.110: bytes=32 time=9ms TTL=122
Reply from 196.2.63.110: bytes=32 time=8ms TTL=122
Reply from 196.2.63.110: bytes=32 time=8ms TTL=122
Reply from 196.2.63.110: bytes=32 time=10ms TTL=122
Request timed out.
Request timed out.
Reply from 196.2.63.110: bytes=32 time=8ms TTL=122
Request timed out.
Reply from 196.2.63.110: bytes=32 time=9ms TTL=122
Reply from 196.2.63.110: bytes=32 time=9ms TTL=122
Reply from 196.2.63.110: bytes=32 time=9ms TTL=122
Reply from 196.2.63.110: bytes=32 time=9ms TTL=122
Reply from 196.2.63.110: bytes=32 time=10ms TTL=122
Reply from 196.2.63.110: bytes=32 time=8ms TTL=122
Reply from 196.2.63.110: bytes=32 time=9ms TTL=122
Reply from 196.2.63.110: bytes=32 time=9ms TTL=122
Request timed out.
Reply from 196.2.63.110: bytes=32 time=8ms TTL=122
Reply from 196.2.63.110: bytes=32 time=9ms TTL=122
Reply from 196.2.63.110: bytes=32 time=9ms TTL=122

My line and account was recently upgraded to 2mb. Throughput was perfect early this morning and late last night.
Click to expand...

Hi, send me your MWEB details so that I can investigate this for you.
 
Hey Mweb Guy. Ive been a mweb subscriber for more than a year nw. I have a 4mbps uncapped account for the last two weeks my speeds have been truly terrible. i have done a few speedtests consistently last few days and have attached the results here. i'm residing in the kuilsriver area 021 903 ***. Are there any problems in the area as this has been going on for two weeks. I have had a telkom tech out here two weeks ago and all line tests are fine, copper is brandnew and ive never had trouble before untill now. any help is much appreciated.

Average download speed local 0.36mbps download and 0.35mbps upload same for local and international. pings of between 520 and 782 ms all day on a 4mbps uncapped account. Any help would be much appreciated:)
 
Gmoboy said:
Hey Mweb Guy. Ive been a mweb subscriber for more than a year nw. I have a 4mbps uncapped account for the last two weeks my speeds have been truly terrible. i have done a few speedtests consistently last few days and have attached the results here. i'm residing in the kuilsriver area 021 903 ***. Are there any problems in the area as this has been going on for two weeks. I have had a telkom tech out here two weeks ago and all line tests are fine, copper is brandnew and ive never had trouble before untill now. any help is much appreciated.

Average download speed local 0.36mbps download and 0.35mbps upload same for local and international. pings of between 520 and 782 ms all day on a 4mbps uncapped account. Any help would be much appreciated:)
Click to expand...

Hi

We are not experiencing any trouble in your area.
Send me your MWEB details and a trace route to a local and international site please.
 
Any reason for the increased international latency?

Pinging bbc.co.uk [212.58.241.131] with 32 bytes of data:
Reply from 212.58.241.131: bytes=32 time=252ms TTL=241
Reply from 212.58.241.131: bytes=32 time=243ms TTL=241
Reply from 212.58.241.131: bytes=32 time=244ms TTL=241
Reply from 212.58.241.131: bytes=32 time=243ms TTL=241

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

About 50ms higher then normal and its rather annoying while gaming.
 
And here we go AGAIN with the international latency issue :mad: Absolute crap that this keeps happening and still no word from Mweb.



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

Pinging bbc.co.uk [212.58.241.131] with 32 bytes of data:
Reply from 212.58.241.131: bytes=32 time=259ms TTL=238
Reply from 212.58.241.131: bytes=32 time=254ms TTL=238
Reply from 212.58.241.131: bytes=32 time=253ms TTL=238
Reply from 212.58.241.131: bytes=32 time=253ms TTL=238

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

C:\Users\Andre>tracert bbc.co.uk

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

1 8 ms 7 ms 9 ms 41-133-68-1.dsl.mweb.co.za [41.133.68.1]
2 9 ms 9 ms 9 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
3 9 ms 95 ms 11 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
4 266 ms 267 ms 264 ms 176.67.177.131
5 271 ms 263 ms 262 ms xe-8-1-0.edge3.London1.Level3.net [195.50.124.13
3]
6 271 ms 265 ms 264 ms vl-3504-ve-118.csw1.London1.Level3.net [4.69.166
.141]
7 272 ms 260 ms 253 ms ae-1-51.edge4.London1.Level3.net [4.69.139.74]
8 260 ms 254 ms 252 ms BBC-TECHNOL.edge4.London1.Level3.net [212.113.14
.222]
9 * * * Request timed out.
10 271 ms 264 ms 264 ms ae1.er01.thdow.bbc.co.uk [132.185.254.18]
11 264 ms 271 ms 263 ms 132.185.255.92
12 253 ms 253 ms 254 ms 212.58.241.131

Trace complete.
Click to expand...


Test conducted on Mon Sep 24 2012 23:38:42 GMT+0200 (South Africa Standard Time)

Download Speed: 2285 kbps (285.6 KB/sec transfer rate)
Upload Speed: 324 kbps (40.5 KB/sec transfer rate)
Latency: 279 ms
Click to expand...


Nothing running. So either we have -

Some kind of throttle happening with or without Mweb's knowledge because it's always round the same time that it craps out.
Really bum links that Mweb needs to sort out pronto without giving us bs stories.
A network that cannot handle the load anymore.
 
Last edited:
MrBroadBand said:
Yip my coms haven't stopped dropping for two weeks now and its not the good dam line noise OKAY mweb douche bag guy/s ...
Click to expand...

As hella frustrating as all this may be, there is no place for you to call the 1 guy who works his ass off trying to help us here names. Be mad at Mweb the ISP, no need to get personal.
 
Mephisto_Helix said:
And here we go AGAIN with the international latency issue :mad: Absolute crap that this keeps happening and still no word from Mweb.

Nothing running. So either we have -

Some kind of throttle happening with or without Mweb's knowledge because it's always round the same time that it craps out.
Really bum links that Mweb needs to sort out pronto without giving us bs stories.
A network that cannot handle the load anymore.
Click to expand...

MrBroadBand said:
Yip my coms haven't stopped dropping for two weeks now and its not the good dam line noise OKAY mweb douche bag guy/s ...
Click to expand...

dasco144 said:
Any reason for the increased international latency?

Pinging bbc.co.uk [212.58.241.131] with 32 bytes of data:
Reply from 212.58.241.131: bytes=32 time=252ms TTL=241
Reply from 212.58.241.131: bytes=32 time=243ms TTL=241
Reply from 212.58.241.131: bytes=32 time=244ms TTL=241
Reply from 212.58.241.131: bytes=32 time=243ms TTL=241

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

About 50ms higher then normal and its rather annoying while gaming.
Click to expand...

Gmoboy said:
Here is the speedtest result to Johannesburg
http://www.speedtest.net/result/2199982307.png

Speedtest result
http://www.speedtest.net/result/2199986647.png
Result to london

ping average to 520 ms local and international. its always the same.
Click to expand...

assagai said:
can't get through to various international sites, eg: http://mhsecure.com/
Click to expand...

Good Morning Guys,

There seems to have been a decrease in international traffic yesterday evening, it seems to be back to normal this morning.

Please let me know if you are still encountering any problems with international traffic.
 
I heard from a inside source MWEB where busy upgrading some parts of their fiber ring last night.. so good things.. putting aside the disconnects and bad latency experienced, as it's all good now
 
Issues started late last night and still going on this morning.

ping www.google.com

Pinging www.google.com [74.125.233.19] with 32 bytes of data:

Reply from 74.125.233.19: bytes=32 time=19ms TTL=54
Reply from 74.125.233.19: bytes=32 time=20ms TTL=54
Reply from 74.125.233.19: bytes=32 time=20ms TTL=54
Reply from 74.125.233.19: bytes=32 time=19ms TTL=54

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

tracert www.facebook.com

Tracing route to www.facebook.com [69.171.247.21]
over a maximum of 30 hops:

1 3 ms 2 ms 3 ms 10.0.0.2
2 16 ms 15 ms 15 ms 41-132-38-1.dsl.mweb.co.za [41.132.38.1]
3 16 ms 17 ms 17 ms te1-1-0.508.cpt-ipc-1.mweb.co.za [196.28.178.190
]
4 16 ms 17 ms 17 ms 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 166 ms 162 ms 163 ms TenGigE0-7-0-2.12.cpt-p-2.mweb.co.za [196.28.178
.114]
6 166 ms * * 197-84-4-195.cpt.mweb.co.za [197.84.4.195]
7 195 ms 204 ms * 176.67.177.131
8 285 ms 295 ms 204 ms 176.67.177.133
9 386 ms 204 ms * linx.br01.lhr1.tfbnw.net [195.66.225.69]
10 379 ms 409 ms 408 ms ae15.bb02.iad2.tfbnw.net [204.15.22.245]
11 372 ms 260 ms 409 ms 31.13.24.86
12 430 ms 409 ms 408 ms ae4.dr03.frc1.tfbnw.net [31.13.27.71]
13 532 ms 306 ms 409 ms po1020.csw03d.frc1.tfbnw.net [31.13.26.165]
14 430 ms 409 ms 409 ms www-slb-10-03-frc1.facebook.com [69.171.247.21]


Trace complete.

tracert www.mybroadband.co.za

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

1 3 ms 3 ms 2 ms 10.0.0.2
2 16 ms 16 ms 16 ms 41-132-38-1.dsl.mweb.co.za [41.132.38.1]
3 33 ms * 33 ms 197-84-8-10.cpt.mweb.co.za [197.84.8.10]
4 50 ms 40 ms 46 ms 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 45 ms 35 ms 35 ms TenGigE0-7-0-2.12.cpt-p-2.mweb.co.za [196.28.178
.114]
6 34 ms 33 ms 34 ms tengig0-0-0.cpt-pr-2.mweb.co.za [197.84.4.165]
7 35 ms 35 ms 35 ms mtn-pp.cpt-cinx-2.mweb.co.za [196.28.178.142]
8 35 ms 35 ms 35 ms 196.44.0.75
9 64 ms 62 ms 63 ms rb-cr-1.za--ct-cr-1.za.mtnns.net [196.44.31.128]

10 64 ms 63 ms 63 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.22
1]
11 65 ms 63 ms 63 ms ge4-0-0.gw17.jnb6.za.mtnbusiness.net [196.30.1.3
7]
12 66 ms * 64 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.13
6]
13 * 67 ms 61 ms core-router1.jnb2.host-h.net [196.30.213.108]
14 66 ms 64 ms 63 ms core-access-switch1-vlan1001.jnb.host-h.net [41.
72.136.53]
15 65 ms 63 ms 63 ms mybroadband.co.za [41.203.21.137]

Trace complete.
 
GrootBaas said:
Issues started late last night and still going on this morning.

ping www.google.com

Pinging www.google.com [74.125.233.19] with 32 bytes of data:

Reply from 74.125.233.19: bytes=32 time=19ms TTL=54
Reply from 74.125.233.19: bytes=32 time=20ms TTL=54
Reply from 74.125.233.19: bytes=32 time=20ms TTL=54
Reply from 74.125.233.19: bytes=32 time=19ms TTL=54

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

tracert www.facebook.com

Tracing route to www.facebook.com [69.171.247.21]
over a maximum of 30 hops:

1 3 ms 2 ms 3 ms 10.0.0.2
2 16 ms 15 ms 15 ms 41-132-38-1.dsl.mweb.co.za [41.132.38.1]
3 16 ms 17 ms 17 ms te1-1-0.508.cpt-ipc-1.mweb.co.za [196.28.178.190
]
4 16 ms 17 ms 17 ms 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 166 ms 162 ms 163 ms TenGigE0-7-0-2.12.cpt-p-2.mweb.co.za [196.28.178
.114]
6 166 ms * * 197-84-4-195.cpt.mweb.co.za [197.84.4.195]
7 195 ms 204 ms * 176.67.177.131
8 285 ms 295 ms 204 ms 176.67.177.133
9 386 ms 204 ms * linx.br01.lhr1.tfbnw.net [195.66.225.69]
10 379 ms 409 ms 408 ms ae15.bb02.iad2.tfbnw.net [204.15.22.245]
11 372 ms 260 ms 409 ms 31.13.24.86
12 430 ms 409 ms 408 ms ae4.dr03.frc1.tfbnw.net [31.13.27.71]
13 532 ms 306 ms 409 ms po1020.csw03d.frc1.tfbnw.net [31.13.26.165]
14 430 ms 409 ms 409 ms www-slb-10-03-frc1.facebook.com [69.171.247.21]


Trace complete.

tracert www.mybroadband.co.za

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

1 3 ms 3 ms 2 ms 10.0.0.2
2 16 ms 16 ms 16 ms 41-132-38-1.dsl.mweb.co.za [41.132.38.1]
3 33 ms * 33 ms 197-84-8-10.cpt.mweb.co.za [197.84.8.10]
4 50 ms 40 ms 46 ms 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 45 ms 35 ms 35 ms TenGigE0-7-0-2.12.cpt-p-2.mweb.co.za [196.28.178
.114]
6 34 ms 33 ms 34 ms tengig0-0-0.cpt-pr-2.mweb.co.za [197.84.4.165]
7 35 ms 35 ms 35 ms mtn-pp.cpt-cinx-2.mweb.co.za [196.28.178.142]
8 35 ms 35 ms 35 ms 196.44.0.75
9 64 ms 62 ms 63 ms rb-cr-1.za--ct-cr-1.za.mtnns.net [196.44.31.128]

10 64 ms 63 ms 63 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.22
1]
11 65 ms 63 ms 63 ms ge4-0-0.gw17.jnb6.za.mtnbusiness.net [196.30.1.3
7]
12 66 ms * 64 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.13
6]
13 * 67 ms 61 ms core-router1.jnb2.host-h.net [196.30.213.108]
14 66 ms 64 ms 63 ms core-access-switch1-vlan1001.jnb.host-h.net [41.
72.136.53]
15 65 ms 63 ms 63 ms mybroadband.co.za [41.203.21.137]

Trace complete.
Click to expand...

Good Morning GrootBaas, Thanks for the tracers. The tracer to Facebook show's high latency, please provide me a tracer to bbc.co.uk as well. Please also provide me your MWEB account details.
 
MWEB Guy said:
Good Morning GrootBaas, Thanks for the tracers. The tracer to Facebook show's high latency, please provide me a tracer to bbc.co.uk as well. Please also provide me your MWEB account details.
Click to expand...

I quickly did the tests at home this morning but had to bring it to the office as I couldn't load mbb at home. Will only be able to assist you tonight again unfortunately. (btw I am in Stellenbosch, Dalsig)

Will PM you account information.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X