MWEB Uncapped ADSL Feedback

MWEBHelp · Nov 29, 2011

CVRChameleon said:
My downloading was fast early evening, and played for the first time in a week without lag on Battlefield 3. Then at about 10:15, the internet just went down, couldnt update after I uninstalled BF3, no browsing, Origin just stood there for 20 minutes on 0Kb/s :/ This morning it seemed to have finished, but Im dissapointed at the 4Mb account. Gaming has bad latencies international, but even local Battlefield 3 is so frustrating sometimes.

Hi CVRChameleon,

Have you brought your gaming issues to the attention of our Gaming admins on our dedicated forum: http://forums.gamezone.co.za/

Regards,

MWEB Guy

Dett234()&&))&&65 · Nov 29, 2011

How does Mweb's acceptable usage policy work? Do they throttle your connection at all or do they just give different things like email and browsing priority?

Apoptosis · Nov 29, 2011

Brandcaul said:
How does Mweb's acceptable usage policy work? Do they throttle your connection at all or do they just give different things like email and browsing priority?

The give email and browsing the highest priority,torrents are the lowest priority and games are also somewhat high on the priority list.

MWEBHelp · Nov 29, 2011

Brandcaul said:
How does Mweb's acceptable usage policy work? Do they throttle your connection at all or do they just give different things like email and browsing priority?

Hi Brandcaul,

We do not throttle any of our ADSL services. Email and Browsing is given high priority.

Gaming is also given high priority on our Network.

Info on our AUP can be found on the following link:
http://www.mweb.co.za/legalpolicies/Terms/MWEBGeneralTermsandConditions.aspx

Regards,

MWEB Guy

CVRChameleon · Nov 29, 2011

MWEB Guy said:
Hi CVRChameleon,

Have you brought your gaming issues to the attention of our Gaming admins on our dedicated forum: http://forums.gamezone.co.za/

Regards,

MWEB Guy

Hi, I have now registered on gamezone; and have submitted my query.

Thanks.

MWEBHelp · Nov 29, 2011

CVRChameleon said:
My downloading was fast early evening, and played for the first time in a week without lag on Battlefield 3. Then at about 10:15, the internet just went down, couldnt update after I uninstalled BF3, no browsing, Origin just stood there for 20 minutes on 0Kb/s :/ This morning it seemed to have finished, but Im dissapointed at the 4Mb account. Gaming has bad latencies international, but even local Battlefield 3 is so frustrating sometimes.

Hi CVRChameleon,

Could you please send me a tracert & ping test results from an international & local site done during the day and 1 in the early evening.

Regards,

MWEB Guy

CVRChameleon · Nov 29, 2011

Hi again

Unfortunately Im at work every day so its going to be hard to get a test done during the day, I will try to do it today before 17:00 which will be some indication of during the day, and then also tonight.

Suggestions on which sites to test?

MWEBHelp · Nov 29, 2011

CVRChameleon said:
Hi again

Unfortunately Im at work every day so its going to be hard to get a test done during the day, I will try to do it today before 17:00 which will be some indication of during the day, and then also tonight.

Suggestions on which sites to test?

You can do a traceroute and ping test to the following sites:

International: bbc.co.uk
Local: mweb.co.za

Also, PM me your MWEB details in order for me to look further into it as well.

Thanks,
MWEB Guy

CVRChameleon · Nov 29, 2011

Code:

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

  1    <1 ms    <1 ms    <1 ms  billion [10.0.0.2]
  2    17 ms    16 ms    17 ms  41-132-32-1.dsl.mweb.co.za [41.132.32.1]
  3    58 ms    56 ms    42 ms  tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.16
9.146]
  4    19 ms    19 ms    20 ms  vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
  5     *       21 ms    24 ms  TenGigE0-0-0-0.11.vic-up-1.mweb.co.za [196.22.16
9.225]
  6    25 ms    26 ms    31 ms  197-80-4-125.jhb.mweb.co.za [197.80.4.125]
  7    90 ms    31 ms    30 ms  tengige0-3-1-0.mid-up-1.mweb.co.za [196.22.169.9
4]
  8   244 ms   249 ms   256 ms  pos0-1-0-1.lon-up-1.mweb.co.za.175.22.196.in-add
r.arpa [196.22.175.222]
  9   256 ms   266 ms   254 ms  149.6.98.17
 10     *      264 ms   240 ms  te7-6.ccr01.lon01.atlas.cogentco.com [154.54.36.
165]
 11   290 ms   240 ms   255 ms  te0-1-0-4.mpd21.lon13.atlas.cogentco.com [154.54
.57.98]
 12   268 ms     *      267 ms  ldn-b4-link.telia.net [213.248.70.237]
 13   261 ms   245 ms   247 ms  ldn-bb2-link.telia.net [80.91.247.93]
 14   240 ms   241 ms   241 ms  ldn-b3-link.telia.net [213.155.133.33]
 15   247 ms   257 ms   258 ms  siemens-ic-119241-ldn-b2.c.telia.net [213.248.10
4.70]
 16   250 ms   258 ms   272 ms  212.58.238.137
 17   253 ms   269 ms   286 ms  virtual-vip-231.thdo.bbc.co.uk [212.58.241.131]


Trace complete.

Code:

C:\Users\ChameleonDevil>ping bbc.co.uk -t

Pinging bbc.co.uk [212.58.241.131] with 32 bytes of data
Reply from 212.58.241.131: bytes=32 time=313ms TTL=238
Reply from 212.58.241.131: bytes=32 time=254ms TTL=238
Reply from 212.58.241.131: bytes=32 time=250ms TTL=238
Reply from 212.58.241.131: bytes=32 time=261ms TTL=238
Reply from 212.58.241.131: bytes=32 time=254ms TTL=238
Reply from 212.58.241.131: bytes=32 time=245ms TTL=238
[B]Request timed out.
Request timed out.[/B]
Reply from 212.58.241.131: bytes=32 time=241ms TTL=238
Reply from 212.58.241.131: bytes=32 time=247ms TTL=238
Reply from 212.58.241.131: bytes=32 time=251ms TTL=238
Reply from 212.58.241.131: bytes=32 time=240ms TTL=238
Reply from 212.58.241.131: bytes=32 time=243ms TTL=238
Reply from 212.58.241.131: bytes=32 time=249ms TTL=238
[B]Request timed out.[/B]
Reply from 212.58.241.131: bytes=32 time=251ms TTL=238
Reply from 212.58.241.131: bytes=32 time=254ms TTL=238
Reply from 212.58.241.131: bytes=32 time=257ms TTL=238
Reply from 212.58.241.131: bytes=32 time=244ms TTL=238
Reply from 212.58.241.131: bytes=32 time=250ms TTL=238
Reply from 212.58.241.131: bytes=32 time=243ms TTL=238
Reply from 212.58.241.131: bytes=32 time=248ms TTL=238

[B]Ping statistics for 212.58.241.131:
    Packets: Sent = 22, Received = 19, Lost = 3 (13% loss)
Approximate round trip times in milli-seconds:
    Minimum = 240ms, Maximum = 313ms, Average = 252ms[/B]
Control-C

Code:

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

  1    <1 ms    <1 ms    <1 ms  billion [10.0.0.2]
  2    31 ms    22 ms    17 ms  41-132-32-1.dsl.mweb.co.za [41.132.32.1]
  3    20 ms    25 ms    30 ms  tengig-0-0-0-104.vic-ipc-2.mweb.co.za [196.22.16
3.218]
  4    25 ms    26 ms    24 ms  vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
  5    45 ms    55 ms    44 ms  TenGigE0-0-0-0.11.vic-up-2.mweb.co.za [196.22.16
9.226]
  6     *       46 ms    43 ms  197-84-4-34.cpt.mweb.co.za [197.84.4.34]
  7    40 ms    45 ms    46 ms  vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
  8    56 ms    45 ms    41 ms  196-28-178-34.adsl.mweb.co.za [196.28.178.34]
  9     *       52 ms    48 ms  www.mweb.co.za [196.2.63.110]

Trace complete.

Code:

Pinging mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=54ms TTL=119
Reply from 196.2.63.110: bytes=32 time=41ms TTL=119
Reply from 196.2.63.110: bytes=32 time=40ms TTL=119
Reply from 196.2.63.110: bytes=32 time=51ms TTL=119
Reply from 196.2.63.110: bytes=32 time=42ms TTL=119
Reply from 196.2.63.110: bytes=32 time=41ms TTL=119
Reply from 196.2.63.110: bytes=32 time=49ms TTL=119
Reply from 196.2.63.110: bytes=32 time=44ms TTL=119
Reply from 196.2.63.110: bytes=32 time=57ms TTL=119
Reply from 196.2.63.110: bytes=32 time=40ms TTL=119
Reply from 196.2.63.110: bytes=32 time=55ms TTL=119
Reply from 196.2.63.110: bytes=32 time=46ms TTL=119
Reply from 196.2.63.110: bytes=32 time=46ms TTL=119
Reply from 196.2.63.110: bytes=32 time=41ms TTL=119

Ping statistics for 196.2.63.110:
    Packets: Sent = 14, Received = 14, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 40ms, Maximum = 57ms, Average = 46ms
Control-C

Code:

  1    <1 ms    <1 ms    <1 ms  billion [10.0.0.2]
  2    28 ms    30 ms    30 ms  41-132-32-1.dsl.mweb.co.za [41.132.32.1]
  3    31 ms    23 ms    21 ms  tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.16
9.146]
  4    31 ms    32 ms    30 ms  vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
  5    24 ms    23 ms    21 ms  TenGigE0-0-0-0.11.vic-up-2.mweb.co.za [196.22.16
9.226]
  6    22 ms    20 ms    21 ms  197-80-4-131.jhb.mweb.co.za [197.80.4.131]
  7    32 ms    30 ms    24 ms  tengige0-3-1-0.mid-up-1.mweb.co.za [196.22.169.2
10]
  8     *      257 ms   244 ms  pos0-1-0-1.lon-up-1.mweb.co.za.175.22.196.in-add
r.arpa [196.22.175.222]
  9     *      253 ms   244 ms  149.6.98.5
 10   289 ms   244 ms   241 ms  te7-6.ccr01.lon01.atlas.cogentco.com [154.54.36.
165]
 11   343 ms   334 ms   331 ms  te0-0-0-4.ccr21.lon13.atlas.cogentco.com [154.54
.57.110]
 12   342 ms   317 ms   324 ms  te0-0-0-1.ccr21.jfk02.atlas.cogentco.com [154.54
.44.225]
 13   316 ms   328 ms   322 ms  te0-4-0-1.ccr21.jfk07.atlas.cogentco.com [154.54
.80.174]
 14   336 ms   330 ms   335 ms  gblx.jfk07.atlas.cogentco.com [154.54.14.70]
 15     *      335 ms     *     ae7.scr3.NYC1.gblx.net [67.16.142.49]
 16   336 ms   356 ms   349 ms  lag1.ar9.NYC1.gblx.net [67.16.142.50]
 17   328 ms   314 ms   342 ms  softlayer-technologies-inc.ethernet11-3.ar9.nyc1
.gblx.net [206.165.75.234]
 18   324 ms   321 ms   317 ms  ae7.bbr02.tl01.nyc01.networklayer.com [173.192.1
8.177]
 19   343 ms   350 ms   335 ms  ae1.bbr01.eq01.chi01.networklayer.com [173.192.1
8.132]
 20   340 ms   348 ms   349 ms  ae7.bbr02.eq01.chi01.networklayer.com [173.192.1
8.171]
 21   386 ms   378 ms   386 ms  ae1.bbr02.cf01.den01.networklayer.com [173.192.1
8.131]
 22   398 ms   426 ms   385 ms  ae7.bbr01.cf01.den01.networklayer.com [173.192.1
8.168]
 23   398 ms   398 ms   389 ms  ae0.bbr01.wb01.sea02.networklayer.com [173.192.1
8.144]
 24   399 ms   413 ms   389 ms  ae0.dar02.sr01.sea01.networklayer.com [173.192.1
8.159]
 25   393 ms   397 ms   428 ms  po2.fcr02.sr03.sea01.networklayer.com [67.228.11
8.227]
 26   389 ms   391 ms   389 ms  174.37.182.114-static.reverse.softlayer.com [174
.37.182.114]

Trace complete.

Code:

Pinging heroesofnewerth.com [174.37.182.114] with 32 bytes of data:
Reply from 174.37.182.114: bytes=32 time=396ms TTL=41
Reply from 174.37.182.114: bytes=32 time=392ms TTL=41
Reply from 174.37.182.114: bytes=32 time=402ms TTL=41
Reply from 174.37.182.114: bytes=32 time=396ms TTL=41
Request timed out.
Reply from 174.37.182.114: bytes=32 time=390ms TTL=41
Reply from 174.37.182.114: bytes=32 time=391ms TTL=41
Reply from 174.37.182.114: bytes=32 time=389ms TTL=41
Reply from 174.37.182.114: bytes=32 time=396ms TTL=41
Reply from 174.37.182.114: bytes=32 time=404ms TTL=41
Reply from 174.37.182.114: bytes=32 time=402ms TTL=41
Reply from 174.37.182.114: bytes=32 time=390ms TTL=41
Request timed out.
Reply from 174.37.182.114: bytes=32 time=388ms TTL=41
Reply from 174.37.182.114: bytes=32 time=401ms TTL=41
Reply from 174.37.182.114: bytes=32 time=389ms TTL=41
Reply from 174.37.182.114: bytes=32 time=399ms TTL=41
Reply from 174.37.182.114: bytes=32 time=398ms TTL=41

Ping statistics for 174.37.182.114:
    Packets: Sent = 18, Received = 16, Lost = 2 (11% loss),
Approximate round trip times in milli-seconds:
    Minimum = 388ms, Maximum = 404ms, Average = 395ms
Control-C
^C

Seriously, 0.26Mbps ??

All browsing is very slow currently, decided to submit heroesofnewerth.com test too, as it was taking a long time to load...

I will PM you with my account details.

MWEBHelp · Nov 29, 2011

CVRChameleon said:

Code:

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

  1    <1 ms    <1 ms    <1 ms  billion [10.0.0.2]
  2    17 ms    16 ms    17 ms  41-132-32-1.dsl.mweb.co.za [41.132.32.1]
  3    58 ms    56 ms    42 ms  tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.16
9.146]
  4    19 ms    19 ms    20 ms  vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
  5     *       21 ms    24 ms  TenGigE0-0-0-0.11.vic-up-1.mweb.co.za [196.22.16
9.225]
  6    25 ms    26 ms    31 ms  197-80-4-125.jhb.mweb.co.za [197.80.4.125]
  7    90 ms    31 ms    30 ms  tengige0-3-1-0.mid-up-1.mweb.co.za [196.22.169.9
4]
  8   244 ms   249 ms   256 ms  pos0-1-0-1.lon-up-1.mweb.co.za.175.22.196.in-add
r.arpa [196.22.175.222]
  9   256 ms   266 ms   254 ms  149.6.98.17
 10     *      264 ms   240 ms  te7-6.ccr01.lon01.atlas.cogentco.com [154.54.36.
165]
 11   290 ms   240 ms   255 ms  te0-1-0-4.mpd21.lon13.atlas.cogentco.com [154.54
.57.98]
 12   268 ms     *      267 ms  ldn-b4-link.telia.net [213.248.70.237]
 13   261 ms   245 ms   247 ms  ldn-bb2-link.telia.net [80.91.247.93]
 14   240 ms   241 ms   241 ms  ldn-b3-link.telia.net [213.155.133.33]
 15   247 ms   257 ms   258 ms  siemens-ic-119241-ldn-b2.c.telia.net [213.248.10
4.70]
 16   250 ms   258 ms   272 ms  212.58.238.137
 17   253 ms   269 ms   286 ms  virtual-vip-231.thdo.bbc.co.uk [212.58.241.131]


Trace complete.

Code:

C:\Users\ChameleonDevil>ping bbc.co.uk -t

Pinging bbc.co.uk [212.58.241.131] with 32 bytes of data
Reply from 212.58.241.131: bytes=32 time=313ms TTL=238
Reply from 212.58.241.131: bytes=32 time=254ms TTL=238
Reply from 212.58.241.131: bytes=32 time=250ms TTL=238
Reply from 212.58.241.131: bytes=32 time=261ms TTL=238
Reply from 212.58.241.131: bytes=32 time=254ms TTL=238
Reply from 212.58.241.131: bytes=32 time=245ms TTL=238
[B]Request timed out.
Request timed out.[/B]
Reply from 212.58.241.131: bytes=32 time=241ms TTL=238
Reply from 212.58.241.131: bytes=32 time=247ms TTL=238
Reply from 212.58.241.131: bytes=32 time=251ms TTL=238
Reply from 212.58.241.131: bytes=32 time=240ms TTL=238
Reply from 212.58.241.131: bytes=32 time=243ms TTL=238
Reply from 212.58.241.131: bytes=32 time=249ms TTL=238
[B]Request timed out.[/B]
Reply from 212.58.241.131: bytes=32 time=251ms TTL=238
Reply from 212.58.241.131: bytes=32 time=254ms TTL=238
Reply from 212.58.241.131: bytes=32 time=257ms TTL=238
Reply from 212.58.241.131: bytes=32 time=244ms TTL=238
Reply from 212.58.241.131: bytes=32 time=250ms TTL=238
Reply from 212.58.241.131: bytes=32 time=243ms TTL=238
Reply from 212.58.241.131: bytes=32 time=248ms TTL=238

[B]Ping statistics for 212.58.241.131:
    Packets: Sent = 22, Received = 19, Lost = 3 (13% loss)
Approximate round trip times in milli-seconds:
    Minimum = 240ms, Maximum = 313ms, Average = 252ms[/B]
Control-C

Code:

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

  1    <1 ms    <1 ms    <1 ms  billion [10.0.0.2]
  2    31 ms    22 ms    17 ms  41-132-32-1.dsl.mweb.co.za [41.132.32.1]
  3    20 ms    25 ms    30 ms  tengig-0-0-0-104.vic-ipc-2.mweb.co.za [196.22.16
3.218]
  4    25 ms    26 ms    24 ms  vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
  5    45 ms    55 ms    44 ms  TenGigE0-0-0-0.11.vic-up-2.mweb.co.za [196.22.16
9.226]
  6     *       46 ms    43 ms  197-84-4-34.cpt.mweb.co.za [197.84.4.34]
  7    40 ms    45 ms    46 ms  vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
  8    56 ms    45 ms    41 ms  196-28-178-34.adsl.mweb.co.za [196.28.178.34]
  9     *       52 ms    48 ms  www.mweb.co.za [196.2.63.110]

Trace complete.

Code:

Pinging mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=54ms TTL=119
Reply from 196.2.63.110: bytes=32 time=41ms TTL=119
Reply from 196.2.63.110: bytes=32 time=40ms TTL=119
Reply from 196.2.63.110: bytes=32 time=51ms TTL=119
Reply from 196.2.63.110: bytes=32 time=42ms TTL=119
Reply from 196.2.63.110: bytes=32 time=41ms TTL=119
Reply from 196.2.63.110: bytes=32 time=49ms TTL=119
Reply from 196.2.63.110: bytes=32 time=44ms TTL=119
Reply from 196.2.63.110: bytes=32 time=57ms TTL=119
Reply from 196.2.63.110: bytes=32 time=40ms TTL=119
Reply from 196.2.63.110: bytes=32 time=55ms TTL=119
Reply from 196.2.63.110: bytes=32 time=46ms TTL=119
Reply from 196.2.63.110: bytes=32 time=46ms TTL=119
Reply from 196.2.63.110: bytes=32 time=41ms TTL=119

Ping statistics for 196.2.63.110:
    Packets: Sent = 14, Received = 14, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 40ms, Maximum = 57ms, Average = 46ms
Control-C

Code:

  1    <1 ms    <1 ms    <1 ms  billion [10.0.0.2]
  2    28 ms    30 ms    30 ms  41-132-32-1.dsl.mweb.co.za [41.132.32.1]
  3    31 ms    23 ms    21 ms  tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.16
9.146]
  4    31 ms    32 ms    30 ms  vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
  5    24 ms    23 ms    21 ms  TenGigE0-0-0-0.11.vic-up-2.mweb.co.za [196.22.16
9.226]
  6    22 ms    20 ms    21 ms  197-80-4-131.jhb.mweb.co.za [197.80.4.131]
  7    32 ms    30 ms    24 ms  tengige0-3-1-0.mid-up-1.mweb.co.za [196.22.169.2
10]
  8     *      257 ms   244 ms  pos0-1-0-1.lon-up-1.mweb.co.za.175.22.196.in-add
r.arpa [196.22.175.222]
  9     *      253 ms   244 ms  149.6.98.5
 10   289 ms   244 ms   241 ms  te7-6.ccr01.lon01.atlas.cogentco.com [154.54.36.
165]
 11   343 ms   334 ms   331 ms  te0-0-0-4.ccr21.lon13.atlas.cogentco.com [154.54
.57.110]
 12   342 ms   317 ms   324 ms  te0-0-0-1.ccr21.jfk02.atlas.cogentco.com [154.54
.44.225]
 13   316 ms   328 ms   322 ms  te0-4-0-1.ccr21.jfk07.atlas.cogentco.com [154.54
.80.174]
 14   336 ms   330 ms   335 ms  gblx.jfk07.atlas.cogentco.com [154.54.14.70]
 15     *      335 ms     *     ae7.scr3.NYC1.gblx.net [67.16.142.49]
 16   336 ms   356 ms   349 ms  lag1.ar9.NYC1.gblx.net [67.16.142.50]
 17   328 ms   314 ms   342 ms  softlayer-technologies-inc.ethernet11-3.ar9.nyc1
.gblx.net [206.165.75.234]
 18   324 ms   321 ms   317 ms  ae7.bbr02.tl01.nyc01.networklayer.com [173.192.1
8.177]
 19   343 ms   350 ms   335 ms  ae1.bbr01.eq01.chi01.networklayer.com [173.192.1
8.132]
 20   340 ms   348 ms   349 ms  ae7.bbr02.eq01.chi01.networklayer.com [173.192.1
8.171]
 21   386 ms   378 ms   386 ms  ae1.bbr02.cf01.den01.networklayer.com [173.192.1
8.131]
 22   398 ms   426 ms   385 ms  ae7.bbr01.cf01.den01.networklayer.com [173.192.1
8.168]
 23   398 ms   398 ms   389 ms  ae0.bbr01.wb01.sea02.networklayer.com [173.192.1
8.144]
 24   399 ms   413 ms   389 ms  ae0.dar02.sr01.sea01.networklayer.com [173.192.1
8.159]
 25   393 ms   397 ms   428 ms  po2.fcr02.sr03.sea01.networklayer.com [67.228.11
8.227]
 26   389 ms   391 ms   389 ms  174.37.182.114-static.reverse.softlayer.com [174
.37.182.114]

Trace complete.

Code:

Pinging heroesofnewerth.com [174.37.182.114] with 32 bytes of data:
Reply from 174.37.182.114: bytes=32 time=396ms TTL=41
Reply from 174.37.182.114: bytes=32 time=392ms TTL=41
Reply from 174.37.182.114: bytes=32 time=402ms TTL=41
Reply from 174.37.182.114: bytes=32 time=396ms TTL=41
Request timed out.
Reply from 174.37.182.114: bytes=32 time=390ms TTL=41
Reply from 174.37.182.114: bytes=32 time=391ms TTL=41
Reply from 174.37.182.114: bytes=32 time=389ms TTL=41
Reply from 174.37.182.114: bytes=32 time=396ms TTL=41
Reply from 174.37.182.114: bytes=32 time=404ms TTL=41
Reply from 174.37.182.114: bytes=32 time=402ms TTL=41
Reply from 174.37.182.114: bytes=32 time=390ms TTL=41
Request timed out.
Reply from 174.37.182.114: bytes=32 time=388ms TTL=41
Reply from 174.37.182.114: bytes=32 time=401ms TTL=41
Reply from 174.37.182.114: bytes=32 time=389ms TTL=41
Reply from 174.37.182.114: bytes=32 time=399ms TTL=41
Reply from 174.37.182.114: bytes=32 time=398ms TTL=41

Ping statistics for 174.37.182.114:
    Packets: Sent = 18, Received = 16, Lost = 2 (11% loss),
Approximate round trip times in milli-seconds:
    Minimum = 388ms, Maximum = 404ms, Average = 395ms
Control-C
^C

Seriously, 0.26Mbps ??

All browsing is very slow currently, decided to submit heroesofnewerth.com test too, as it was taking a long time to load...

I will PM you with my account details.

Hi CVRChameleon,

Thank you for the information you have provided, I will keep you posted.

Regards,
MWEB Guy

Apoptosis · Nov 29, 2011

My internet just died and is crawling at less then 5kb/s.it was fine at over 400kb/s a moment ago.

TmanSA · Nov 30, 2011

How late did you r downloads go down to 5K ?

AthenianOwl · Nov 30, 2011

Hey

1. My browsing speed is very very slow. Always get the connection time-out error

2. Torrent speed is good.
3. HTTP download speed is good.

How do I fix it?

CVRChameleon · Nov 30, 2011

Hi MWEB guy, as per the previous page info supplied, I am still waiting on a response from last night, nothing improved last night, browsing was impossible, downloads was slow, gaming was laggy and frustrating. If I have to get 0.26Mbps international I can just cancel my 4Mbps account and get dialup.

TmanSA · Nov 30, 2011

Hi CVR

Have you tried turning ur modem of for 30 min and then putting it back on... If my connection gets slow that is what I do 9/10 times it works.

MWEBHelp · Nov 30, 2011

Kitty09 said:
Hey

1. My browsing speed is very very slow. Always get the connection time-out error
2. Torrent speed is good.
3. HTTP download speed is good.

How do I fix it?

Hi Kitty09,

Have you tried a different browser? Have you tried clearing your temporary internet files & cookies?

Are you browsing while running DL in the background?

Regards,

MWEB Guy

MWEBHelp · Nov 30, 2011

CVRChameleon said:
Hi MWEB guy, as per the previous page info supplied, I am still waiting on a response from last night, nothing improved last night, browsing was impossible, downloads was slow, gaming was laggy and frustrating. If I have to get 0.26Mbps international I can just cancel my 4Mbps account and get dialup.

Hi CVRChameleon,

Will look into it now.

Regards,

MWEB Guy

AthenianOwl · Nov 30, 2011

MWEB Guy said:
Hi Kitty09,

Have you tried a different browser? Have you tried clearing your temporary internet files & cookies?

Are you browsing while running DL in the background?

Regards,

MWEB Guy

Hey, now my browsing speed is normal. I can't reproduce this problem. It happened right after turning my computer on.

No, but I will download the latest version of Chrome now.
No running DLs in the background at that time.

Will let you know when it happens again

PostmanPot · Nov 30, 2011

Something's up with my 1Mbit.

Local/international browsing sometimes timing out, slow to respond.

Gtx Gaming · Nov 30, 2011

They told me backbone in cpt is dead getting 800ms with packet,loss in cpt

Im on bussiness adsl at work atm

Sent from my GT-S5830 using MyBroadband Android App

Join the MyBroadband community

Get started

MWEB Uncapped ADSL Feedback

MWEB Representative

Active Member

Active Member

MWEB Representative

Well-Known Member

MWEB Representative

Well-Known Member

MWEB Representative

Well-Known Member

MWEB Representative

Active Member

Well-Known Member

Executive Member

Well-Known Member

Well-Known Member

MWEB Representative

MWEB Representative

Executive Member

Honorary Master

Gtx Gaming