MWEB Uncapped ADSL Feedback - Part 2

[MyWorld]

Is there something wrong on the network? My speed internationally has dropped considerably.

 

[Necuno]

Is there something wrong on the network? My speed internationally has dropped considerably.

I'm downloading. Sorry.

 

[Gimaru]

been having a lot of drops and high latency in gaming recently.

Game latency would sky rocket to 40k, and even msn would disconnect before returning to normal again after a minute, so it's not the games in fault. Been happening very often the last 2 weeks.

 

[MWEBHelp]

Is there something wrong on the network? My speed internationally has dropped considerably.

has your speeds increased ?

 

[MWEBHelp]

been having a lot of drops and high latency in gaming recently.

Game latency would sky rocket to 40k, and even msn would disconnect before returning to normal again after a minute, so it's not the games in fault. Been happening very often the last 2 weeks.

I reauthed your account now, allow 30 minutes then restart your router and test.

If your speeds do not improve then provide me with a trace route to a local and international site.

 

[Gimaru]

I reauthed your account now, allow 30 minutes then restart your router and test.

If your speeds do not improve then provide me with a trace route to a local and international site.

Thank you, will keep an eye on it

 

[Necuno]

can anyone actually ping this 159.153.235.32
its suppose to be one of origins (ea) servers.

Seems dns is ****ed or something at mweb's level. Without vpn its not working, with my vpn its working:

mweb:
C:\Windows\system32>ping 159.153.235.32

Pinging 159.153.235.32 with 32 bytes of data:
General failure.
General failure.
General failure.
General failure.

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


VPN exist in london:
C:\Users\Jade>ping 159.153.235.32

Pinging 159.153.235.32 with 32 bytes of data:
Reply from 159.153.235.32: bytes=32 time=288ms TTL=244
Reply from 159.153.235.32: bytes=32 time=289ms TTL=244
Reply from 159.153.235.32: bytes=32 time=288ms TTL=244
Reply from 159.153.235.32: bytes=32 time=287ms TTL=244

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


mweb:
C:\>tracert 159.153.235.32

Tracing route to 159.153.235.32 over a maximum of 30 hops

1 General failure.

Trace complete.

vpn exit in london
C:\>tracert 159.153.235.32

Tracing route to 159.153.235.32 over a maximum of 30 hops

1 215 ms 213 ms 212 ms 10.6.0.1
2 212 ms 246 ms 206 ms 84.39.116.177
3 367 ms 432 ms 418 ms te-6-2-0.core-dc1.man4.uk.m247.com [77.243.176.1
05]
4 247 ms 246 ms 282 ms te-5-5-0.bb1.lon2.uk.m247.com [77.243.176.57]
5 338 ms 287 ms 299 ms ge-2-1-0.mpr1.lhr2.uk.above.net [195.66.224.76]

6 216 ms 274 ms 292 ms ge-3-0-0.mpr1.lhr2.uk.above.net [64.125.28.126]

7 411 ms 308 ms 332 ms so-0-1-0.mpr1.dca2.us.above.net [64.125.27.57]
8 331 ms 287 ms 300 ms xe-1-3-0.cr1.dca2.us.above.net [64.125.29.21]
9 288 ms 288 ms 298 ms xe-0-0-1.er1.iad10.us.above.net [64.125.31.206]

10 293 ms 289 ms 288 ms 64.125.199.186.t00673-01.above.net [64.125.199.1
86]
11 324 ms 351 ms 306 ms 159.153.93.2
12 402 ms 310 ms 314 ms 159.153.225.14
13 338 ms 348 ms 341 ms 159.153.235.32

Trace complete.

 

[Necuno]

comparative post against ip using Afrihost. working.

C:\>ping 159.153.235.32

Pinging 159.153.235.32 with 32 bytes of data:
Reply from 159.153.235.32: bytes=32 time=341ms TTL=232
Reply from 159.153.235.32: bytes=32 time=292ms TTL=232
Reply from 159.153.235.32: bytes=32 time=325ms TTL=232
Reply from 159.153.235.32: bytes=32 time=395ms TTL=232

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


C:\>tracert 159.153.235.32

Tracing route to 159.153.235.32 over a maximum of 30 hops

1 11 ms 8 ms 34 ms 105-236-3-129-esr-lo.mtnbusiness.co.za [105.236.
3.129]
2 103 ms 37 ms 33 ms ipc-recieve-rb-2a.za.mtnbusiness.net [41.181.178
.65]
3 37 ms 87 ms 24 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.1
20]
4 25 ms 10 ms 15 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
5 57 ms 77 ms 85 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
6 213 ms 249 ms 247 ms xe-4-1-0.edge5.Amsterdam1.Level3.net [212.72.41.
89]
7 224 ms 278 ms 253 ms 4.69.162.133
8 247 ms 225 ms 225 ms ae-1-51.edge3.Amsterdam1.Level3.net [4.69.139.13
7]
9 268 ms 250 ms 255 ms 4.68.70.42
10 223 ms 217 ms 229 ms xe-0-0-1.mpr1.ams10.nl.above.net [64.125.22.233]

11 238 ms 222 ms 217 ms xe-0-3-0.cr1.ams10.nl.above.net [64.125.22.37]
12 216 ms 236 ms 233 ms ge-1-1-0.mpr1.lhr3.uk.above.net [64.125.27.221]

13 313 ms 293 ms 290 ms xe-4-3-0.cr2.dca2.us.above.net [64.125.24.41]
14 274 ms 274 ms 284 ms xe-0-0-0.cr1.dca2.us.above.net [64.125.28.241]
15 278 ms 356 ms 278 ms xe-1-0-1.er1.iad10.us.above.net [64.125.26.238]

16 479 ms 292 ms 298 ms 64.125.199.186.t00673-01.above.net [64.125.199.1
86]
17 306 ms 324 ms 343 ms 159.153.93.2
18 308 ms 304 ms 306 ms 159.153.225.14
19 292 ms 320 ms 331 ms 159.153.235.32

Trace complete.

C:\>

again with mweb:
C:\>tracert 159.153.235.32

Tracing route to 159.153.235.32 over a maximum of 30 hops

1 General failure.

Trace complete.

 

[Necuno]

more fail with gosredirector.ea.com, can't ping, can't trace. Exactly the same thing. Dead with mweb.

mweb:
C:\>ping gosredirector.ea.com

Pinging gosredirector.ea.com [159.153.235.22] with 32 bytes of data:
General failure.
General failure.
General failure.
General failure.

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

C:\>tracert gosredirector.ea.com

Tracing route to gosredirector.ea.com [159.153.235.22]
over a maximum of 30 hops:

1 General failure.

Trace complete.

C:\>

vpn exit:
C:\>ping gosredirector.ea.com

Pinging gosredirector.ea.com [159.153.235.22] with 32 bytes of data:
Reply from 159.153.235.22: bytes=32 time=300ms TTL=244
Reply from 159.153.235.22: bytes=32 time=327ms TTL=244
Reply from 159.153.235.22: bytes=32 time=291ms TTL=244
Reply from 159.153.235.22: bytes=32 time=333ms TTL=244

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

C:\>

afrihost:
C:\>ping gosredirector.ea.com

Pinging gosredirector.ea.com [159.153.235.22] with 32 bytes of data:
Reply from 159.153.235.22: bytes=32 time=339ms TTL=234
Reply from 159.153.235.22: bytes=32 time=292ms TTL=234
Reply from 159.153.235.22: bytes=32 time=290ms TTL=234
Reply from 159.153.235.22: bytes=32 time=293ms TTL=234

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

C:\>

C:\>tracert gosredirector.ea.com

Tracing route to gosredirector.ea.com [159.153.235.22]
over a maximum of 30 hops:

1 52 ms 84 ms 91 ms 105-236-3-129-esr-lo.mtnbusiness.co.za [105.236.
3.129]
2 32 ms 61 ms 35 ms ipc-recieve-rb-2a.za.mtnbusiness.net [41.181.178
.65]
3 14 ms 13 ms 10 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
4 54 ms 20 ms 38 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95
]
5 76 ms 86 ms 156 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
6 267 ms 209 ms 203 ms xe-4-1-0.edge5.Amsterdam1.Level3.net [212.72.41.
89]
7 234 ms 230 ms 216 ms 4.69.162.137
8 273 ms 237 ms 211 ms ae-1-51.edge3.Amsterdam1.Level3.net [4.69.139.13
7]
9 236 ms 208 ms 211 ms 4.68.70.42
10 248 ms 257 ms 257 ms xe-0-0-1.mpr1.ams10.nl.above.net [64.125.22.233]

11 243 ms 221 ms 247 ms xe-0-3-0.cr1.ams10.nl.above.net [64.125.22.37]
12 243 ms 218 ms 215 ms ge-1-1-0.mpr1.lhr3.uk.above.net [64.125.27.221]

13 292 ms 291 ms 289 ms xe-4-3-0.cr2.dca2.us.above.net [64.125.24.41]
14 358 ms 305 ms 340 ms xe-0-0-0.cr1.dca2.us.above.net [64.125.28.241]
15 278 ms 314 ms 275 ms xe-1-0-1.er1.iad10.us.above.net [64.125.26.238]

16 321 ms 332 ms 300 ms 64.125.199.186.t00673-01.above.net [64.125.199.1
86]
17 362 ms 391 ms 419 ms 159.153.93.2
18 301 ms 310 ms 315 ms 159.153.225.14
19 328 ms 312 ms 329 ms gosredirector.ea.com [159.153.235.22]

Trace complete.

C:\>

 

[Necuno]

workaround for now

opendns
208.67.222.222
208.67.220.220

ipconfig /flushdns
ipconfig /registerdns

results in
C:\>ping goredirector.ea.com

Pinging goredirector.ea.com [67.215.65.132] with 32 bytes of data:
Reply from 67.215.65.132: bytes=32 time=229ms TTL=49
Reply from 67.215.65.132: bytes=32 time=209ms TTL=49
Reply from 67.215.65.132: bytes=32 time=224ms TTL=49
Reply from 67.215.65.132: bytes=32 time=209ms TTL=49

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

C:\>

 

[Necuno]

Going to be a long week if it starts out like this:
http://mybroadband.co.za/vb/showthread.php/548227-EA-dead-on-mweb?p=10847711&viewfull=1#post10847711

Sorry. Configuration setup.

 

[pjjdp]

Hi,

I'm not aware of any issues at the moment with authentication.
There are however a few Telkom outages, please see our notice board for details.
http://www.mweb.co.za/helpcentre/NetworkStatusNotices.aspx

Hi,

It's sorted. Apparently something was broken at my exchange.

Regards

 

[Gtx Gaming]

thanx for new router mweb , great service !!

Connection Speed 6136 Kbps 635 Kbps
Line Attenuation 34.5 dB 19.3 dB
Noise Margin 14.4 dB 19.4 dB

new line stats is awesome , use to have 41 line attenuation!

 

[MWEBHelp]

thanx for new router mweb , great service !!

Connection Speed 6136 Kbps 635 Kbps
Line Attenuation 34.5 dB 19.3 dB
Noise Margin 14.4 dB 19.4 dB

new line stats is awesome , use to have 41 line attenuation!

Hi hereticangel

Great stuff and thanks for the feedback.

 

[kienah]

Im at my wits end.
For approx 4 weeks now, Mweb's speeds have dropped significantly.
On my 4meg line i was averaging all day and night close to 400k/sec. Now im down to 150k/sec.
On advice from a friend Axxess was giving out 3GB data to trial, i utilized that and was back onto the high speeds again.
If that is what they can give me im seriously considering moving. Been a loyal MWEB supporter for a while now. Was told my exchange is 10MBPS enabled, but they need to upgrade the DSLAM?

 

[MWEBHelp]

Im at my wits end.
For approx 4 weeks now, Mweb's speeds have dropped significantly.
On my 4meg line i was averaging all day and night close to 400k/sec. Now im down to 150k/sec.
On advice from a friend Axxess was giving out 3GB data to trial, i utilized that and was back onto the high speeds again.
If that is what they can give me im seriously considering moving. Been a loyal MWEB supporter for a while now. Was told my exchange is 10MBPS enabled, but they need to upgrade the DSLAM?

Hi kienah

Please provide me with your MWEB account details and the speed test result of both ISP accounts.

 

[Jupejupe]

Wow.. Congestion is becoming worse and worse...
Results:
Download Speed: 353 kbps (44.1 KB/sec transfer rate)
Upload Speed: 350 kbps (43.8 KB/sec transfer rate)
7/30/2013 7:01:21 PM

On a 4mb line sigh...

 

[MWEBHelp]

Wow.. Congestion is becoming worse and worse...
Results:
Download Speed: 353 kbps (44.1 KB/sec transfer rate)
Upload Speed: 350 kbps (43.8 KB/sec transfer rate)
7/30/2013 7:01:21 PM

On a 4mb line sigh...

Hi Jupejupe

I have refreshed your ADSL port and MWEB account. Please allow for 30min to pass then reboot router and test again.

Here is also some info on congestion and how to test for it:

http://mybroadband.co.za/news/adsl/82251-how-to-test-for-adsl-exchange-congestion.html

 

[Dysphoric]

Hi

Does mweb offer no support in dealing with telkom, and getting them to do something about congested exchanges? My line rental is with mweb - are you not therefore meant to interact with telkom them on my behalf?

Congestion seems to have severely increased in the last week, I have gone from 150 local pings (bad enough) to the following:


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

1 <1 ms <1 ms 1 ms 192.168.1.1
2 705 ms 637 ms 587 ms 41-133-112-1.dsl.mweb.co.za [41.133.112.1]
3 741 ms 760 ms 648 ms 196-28-178-234.adsl.mweb.co.za [196.28.178.234]

4 620 ms 699 ms 670 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 715 ms 521 ms 511 ms 196.28.178.66
6 596 ms 673 ms 761 ms cte-core-sw2.vwol.net [196.41.144.35]
7 676 ms 729 ms 801 ms www.mweb.co.za [196.2.63.110]

Trace complete.


600+ ms local every night, until well after midnight. Service is basically unusable. And I'm supposed to accept this?

 

[MWEBHelp]

Hi

Does mweb offer no support in dealing with telkom, and getting them to do something about congested exchanges? My line rental is with mweb - are you not therefore meant to interact with telkom them on my behalf?

Congestion seems to have severely increased in the last week, I have gone from 150 local pings (bad enough) to the following:


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

1 <1 ms <1 ms 1 ms 192.168.1.1
2 705 ms 637 ms 587 ms 41-133-112-1.dsl.mweb.co.za [41.133.112.1]
3 741 ms 760 ms 648 ms 196-28-178-234.adsl.mweb.co.za [196.28.178.234]

4 620 ms 699 ms 670 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 715 ms 521 ms 511 ms 196.28.178.66
6 596 ms 673 ms 761 ms cte-core-sw2.vwol.net [196.41.144.35]
7 676 ms 729 ms 801 ms www.mweb.co.za [196.2.63.110]

Trace complete.


600+ ms local every night, until well after midnight. Service is basically unusable. And I'm supposed to accept this?

Hi Dysphoric

Yes we do speak to Telkom on a customers behalf if the line is with MWEB.

Please be advised that no ISP can change congestion at an exchange as it belongs to Telkom and they do upgrades to the exchange.

We can bring it to their attention for you. Would you like me to log it for you?

Here is also some info on congestion and how to test for it:

http://mybroadband.co.za/news/adsl/8...ongestion.html