MWEB Uncapped Subscribers Feedback

Status
Not open for further replies.
Hmm, switched to my WA backup the pages work, switch back to Mweb they're dead again

I experienced the same problem with mediafire.com last night. Purchased a 1GB capped account with another ISP and when I used that, everything opened fine. Switched back to MWEB and the page doesn't load.
 
Hi All,

Please provide me ping and traceroute results in order for me to follow up on this from our side.

Regards,
MWEB Guy

Seems fine, just the specific links seem to be a problem (http://www.fileserve.com/upload-file.php and http://www.fileserve.com/remote-upload.php)

C:\Users\xxx>ping www.fileserve.com

Pinging www.fileserve.com [209.222.23.221] with 32 bytes of data:
Reply from 209.222.23.221: bytes=32 time=238ms TTL=47
Reply from 209.222.23.221: bytes=32 time=236ms TTL=47
Reply from 209.222.23.221: bytes=32 time=261ms TTL=47
Reply from 209.222.23.221: bytes=32 time=234ms TTL=47

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

C:\Users\xxx>tracert www.fileserve.com

Tracing route to www.fileserve.com [209.222.23.221]
over a maximum of 30 hops:

1 7 ms 7 ms 6 ms 41-132-48-1.dsl.mweb.co.za [41.132.48.1]
2 12 ms 7 ms 7 ms Te1-1-0.511.cpt-ipc-1.mweb.co.za [196.28.178.202
]
3 7 ms 8 ms 7 ms Vlan92.cpt-hscore-1.mweb.co.za [196.28.179.11]
4 11 ms 13 ms 11 ms TenGigE0-2-0-0.11.cpt-up-1.mweb.co.za [196.28.17
8.97]
5 159 ms 159 ms 160 ms pos0-0-3-0.lon-up-1.mweb.co.za [196.22.164.2]
6 161 ms 162 ms 160 ms 149.6.98.5
7 226 ms 208 ms 209 ms te7-6.ccr01.lon01.atlas.cogentco.com [154.54.36.
165]
8 289 ms 297 ms 288 ms te0-2-0-4.ccr21.lon13.atlas.cogentco.com [154.54
.57.114]
9 282 ms 288 ms 283 ms te0-5-0-4.ccr21.jfk02.atlas.cogentco.com [154.54
.44.229]
10 242 ms 233 ms 233 ms te0-4-0-0.ccr21.jfk07.atlas.cogentco.com [154.54
.44.218]
11 234 ms 249 ms 236 ms ntt.jfk07.atlas.cogentco.com [154.54.11.66]
12 242 ms 237 ms 239 ms xe-5-0-5.ar1.nyc3.us.nlayer.net [69.31.34.196]
13 237 ms 236 ms 236 ms vlan-75.ar2.ewr1.us.nlayer.net [69.31.34.129]
14 235 ms 246 ms 242 ms as20473.ae3.ar2.ewr1.us.nlayer.net [69.31.34.214
]
15 237 ms 240 ms 235 ms vl3-c58-c6-1.ewr3.choopa.net [66.55.134.186]
16 286 ms 282 ms 282 ms 209.222.7.130
17 237 ms 235 ms 235 ms 209.222.7.134
18 234 ms 234 ms 235 ms 209.222.23.221

Trace complete.
 
Code:
C:\Windows\system32>ping fileserve.com

Pinging fileserve.com [209.222.23.221] with 32 bytes of data:
Reply from 209.222.23.221: bytes=32 time=331ms TTL=43
Reply from 209.222.23.221: bytes=32 time=328ms TTL=43
Reply from 209.222.23.221: bytes=32 time=329ms TTL=43
Reply from 209.222.23.221: bytes=32 time=329ms TTL=43

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

[B]Fileserve tracert:[/B]
  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     8 ms     7 ms     8 ms  41-133-48-1.dsl.mweb.co.za [41.133.48.1]
  3    21 ms    21 ms    21 ms  41-86-107-18.mweb.co.za [41.86.107.18]
  4    20 ms    20 ms    21 ms  vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
  5    22 ms    22 ms    22 ms  TenGigE0-0-0-0.11.vic-up-1.mweb.co.za [196.22.169.225]
  6    22 ms    22 ms    21 ms  tengige0-3-1-0.mid-up-1.mweb.co.za [196.22.169.210]
  7   247 ms   247 ms   247 ms  pos0-0-2-1.lon-up-1.mweb.co.za [196.22.163.234]
  8   393 ms   439 ms   422 ms  149.6.98.17
  9   248 ms   250 ms   248 ms  te7-6.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
 10   322 ms   323 ms   322 ms  te0-3-0-4.mpd21.lon13.atlas.cogentco.com [154.54.57.90]
 11   325 ms   325 ms   325 ms  te0-2-0-4.ccr21.bos01.atlas.cogentco.com [66.28.4.189]
 12   325 ms   326 ms   331 ms  te0-2-0-1.mpd22.jfk02.atlas.cogentco.com [154.54.44.21]
 13   323 ms   324 ms   323 ms  te0-0-0-6.ccr21.jfk07.atlas.cogentco.com [154.54.3.2]
 14   322 ms   319 ms   320 ms  ntt.jfk07.atlas.cogentco.com [154.54.12.66]
 15   321 ms   324 ms   322 ms  xe-7-0-3.ar1.nyc3.us.nlayer.net [69.31.34.202]
 16   327 ms   325 ms   321 ms  vlan-75.ar2.ewr1.us.nlayer.net [69.31.34.129]
 17   326 ms   322 ms   323 ms  as20473.ae3.ar2.ewr1.us.nlayer.net [69.31.34.214]
 18   339 ms   324 ms   325 ms  vl3-c58-c6-1.ewr3.choopa.net [66.55.134.186]
 19   326 ms   325 ms   328 ms  209.222.7.82
 20   324 ms   326 ms   324 ms  209.222.7.86
 21   324 ms   325 ms   324 ms  209.222.23.221

Isn't hop 2 supposed to be my IP address?
 
Last edited:
Can't download any fileserve.

Traceroute:
Code:
traceroute to www.fileserve.com (209.222.23.221), 64 hops max, 52 byte packets
 1  192.168.1.1 (192.168.1.1)  2.233 ms  1.395 ms  1.250 ms
 2  41-133-84-1.dsl.mweb.co.za (41.133.84.1)  20.432 ms  46.098 ms  39.353 ms
 3  41-86-107-6.mweb.co.za (41.86.107.6)  43.180 ms  23.632 ms  20.384 ms
 4  vl-92.vic-hscore-2.mweb.co.za (196.22.189.3)  27.454 ms  48.443 ms  37.673 ms
 5  tengige0-1-0-0.12.vic-up-1.mweb.co.za (196.22.169.241)  43.004 ms
    tengige0-0-0-0.11.vic-up-1.mweb.co.za (196.22.169.225)  42.388 ms  49.761 ms
 6  tengige0-3-1-0.mid-up-1.mweb.co.za (196.22.169.210)  47.182 ms *  26.249 ms
 7  pos0-0-2-1.lon-up-1.mweb.co.za (196.22.163.234)  321.107 ms  282.291 ms  259.236 ms
 8  * 149.6.98.17 (149.6.98.17)  269.775 ms
    149.6.98.5 (149.6.98.5)  263.693 ms
 9  te7-6.ccr01.lon01.atlas.cogentco.com (154.54.36.165)  270.914 ms  248.195 ms *
10  te0-1-0-4.ccr21.lon13.atlas.cogentco.com (154.54.57.106)  348.431 ms  337.805 ms  335.016 ms
11  te0-0-0-1.ccr21.jfk02.atlas.cogentco.com (154.54.44.225)  350.541 ms
    te0-1-0-4.ccr21.bos01.atlas.cogentco.com (154.54.1.93)  327.226 ms
    te0-0-0-4.ccr21.bos01.atlas.cogentco.com (154.54.5.161)  351.875 ms
12  te0-3-0-1.ccr21.jfk07.atlas.cogentco.com (154.54.7.30)  324.215 ms
    te0-2-0-0.ccr21.jfk07.atlas.cogentco.com (154.54.2.186)  323.894 ms
    te0-2-0-1.mpd21.jfk02.atlas.cogentco.com (154.54.44.9)  409.024 ms
13  te0-0-0-6.ccr21.jfk07.atlas.cogentco.com (154.54.3.2)  560.713 ms
    ntt.jfk07.atlas.cogentco.com (154.54.11.66)  359.345 ms
    ntt.jfk07.atlas.cogentco.com (154.54.12.66)  439.159 ms
14  ntt.jfk07.atlas.cogentco.com (154.54.11.66)  408.818 ms
    ntt.jfk07.atlas.cogentco.com (154.54.12.66)  408.670 ms
    xe-1-0-4.ar1.nyc3.us.nlayer.net (69.31.34.182)  408.557 ms
15  vlan-75.ar2.ewr1.us.nlayer.net (69.31.34.129)  379.485 ms
    xe-1-0-4.ar1.nyc3.us.nlayer.net (69.31.34.182)  410.174 ms  336.119 ms
16  as20473.ae3.ar2.ewr1.us.nlayer.net (69.31.34.214)  344.904 ms  337.696 ms
    vlan-75.ar2.ewr1.us.nlayer.net (69.31.34.129)  334.080 ms
17  as20473.ae3.ar2.ewr1.us.nlayer.net (69.31.34.214)  525.148 ms
    vl3-c58-c6-1.ewr3.choopa.net (66.55.134.186)  410.140 ms  344.993 ms
18  vl3-c58-c6-1.ewr3.choopa.net (66.55.134.186)  339.300 ms  336.144 ms *
19  209.222.7.86 (209.222.7.86)  338.480 ms *
    209.222.7.82 (209.222.7.82)  377.867 ms
20  209.222.23.221 (209.222.23.221)  429.095 ms  317.710 ms
    209.222.7.86 (209.222.7.86)  400.922 ms
 
Seems fine, just the specific links seem to be a problem (http://www.fileserve.com/upload-file.php and http://www.fileserve.com/remote-upload.php)

Code:
C:\Windows\system32>ping fileserve.com

Pinging fileserve.com [209.222.23.221] with 32 bytes of data:
Reply from 209.222.23.221: bytes=32 time=331ms TTL=43
Reply from 209.222.23.221: bytes=32 time=328ms TTL=43
Reply from 209.222.23.221: bytes=32 time=329ms TTL=43
Reply from 209.222.23.221: bytes=32 time=329ms TTL=43

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

[B]Fileserve tracert:[/B]
  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     8 ms     7 ms     8 ms  41-133-48-1.dsl.mweb.co.za [41.133.48.1]
  3    21 ms    21 ms    21 ms  41-86-107-18.mweb.co.za [41.86.107.18]
  4    20 ms    20 ms    21 ms  vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
  5    22 ms    22 ms    22 ms  TenGigE0-0-0-0.11.vic-up-1.mweb.co.za [196.22.169.225]
  6    22 ms    22 ms    21 ms  tengige0-3-1-0.mid-up-1.mweb.co.za [196.22.169.210]
  7   247 ms   247 ms   247 ms  pos0-0-2-1.lon-up-1.mweb.co.za [196.22.163.234]
  8   393 ms   439 ms   422 ms  149.6.98.17
  9   248 ms   250 ms   248 ms  te7-6.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
 10   322 ms   323 ms   322 ms  te0-3-0-4.mpd21.lon13.atlas.cogentco.com [154.54.57.90]
 11   325 ms   325 ms   325 ms  te0-2-0-4.ccr21.bos01.atlas.cogentco.com [66.28.4.189]
 12   325 ms   326 ms   331 ms  te0-2-0-1.mpd22.jfk02.atlas.cogentco.com [154.54.44.21]
 13   323 ms   324 ms   323 ms  te0-0-0-6.ccr21.jfk07.atlas.cogentco.com [154.54.3.2]
 14   322 ms   319 ms   320 ms  ntt.jfk07.atlas.cogentco.com [154.54.12.66]
 15   321 ms   324 ms   322 ms  xe-7-0-3.ar1.nyc3.us.nlayer.net [69.31.34.202]
 16   327 ms   325 ms   321 ms  vlan-75.ar2.ewr1.us.nlayer.net [69.31.34.129]
 17   326 ms   322 ms   323 ms  as20473.ae3.ar2.ewr1.us.nlayer.net [69.31.34.214]
 18   339 ms   324 ms   325 ms  vl3-c58-c6-1.ewr3.choopa.net [66.55.134.186]
 19   326 ms   325 ms   328 ms  209.222.7.82
 20   324 ms   326 ms   324 ms  209.222.7.86
 21   324 ms   325 ms   324 ms  209.222.23.221

Isn't hop 2 supposed to be my IP address?

Can't download any fileserve.

Traceroute:
Code:
traceroute to www.fileserve.com (209.222.23.221), 64 hops max, 52 byte packets
 1  192.168.1.1 (192.168.1.1)  2.233 ms  1.395 ms  1.250 ms
 2  41-133-84-1.dsl.mweb.co.za (41.133.84.1)  20.432 ms  46.098 ms  39.353 ms
 3  41-86-107-6.mweb.co.za (41.86.107.6)  43.180 ms  23.632 ms  20.384 ms
 4  vl-92.vic-hscore-2.mweb.co.za (196.22.189.3)  27.454 ms  48.443 ms  37.673 ms
 5  tengige0-1-0-0.12.vic-up-1.mweb.co.za (196.22.169.241)  43.004 ms
    tengige0-0-0-0.11.vic-up-1.mweb.co.za (196.22.169.225)  42.388 ms  49.761 ms
 6  tengige0-3-1-0.mid-up-1.mweb.co.za (196.22.169.210)  47.182 ms *  26.249 ms
 7  pos0-0-2-1.lon-up-1.mweb.co.za (196.22.163.234)  321.107 ms  282.291 ms  259.236 ms
 8  * 149.6.98.17 (149.6.98.17)  269.775 ms
    149.6.98.5 (149.6.98.5)  263.693 ms
 9  te7-6.ccr01.lon01.atlas.cogentco.com (154.54.36.165)  270.914 ms  248.195 ms *
10  te0-1-0-4.ccr21.lon13.atlas.cogentco.com (154.54.57.106)  348.431 ms  337.805 ms  335.016 ms
11  te0-0-0-1.ccr21.jfk02.atlas.cogentco.com (154.54.44.225)  350.541 ms
    te0-1-0-4.ccr21.bos01.atlas.cogentco.com (154.54.1.93)  327.226 ms
    te0-0-0-4.ccr21.bos01.atlas.cogentco.com (154.54.5.161)  351.875 ms
12  te0-3-0-1.ccr21.jfk07.atlas.cogentco.com (154.54.7.30)  324.215 ms
    te0-2-0-0.ccr21.jfk07.atlas.cogentco.com (154.54.2.186)  323.894 ms
    te0-2-0-1.mpd21.jfk02.atlas.cogentco.com (154.54.44.9)  409.024 ms
13  te0-0-0-6.ccr21.jfk07.atlas.cogentco.com (154.54.3.2)  560.713 ms
    ntt.jfk07.atlas.cogentco.com (154.54.11.66)  359.345 ms
    ntt.jfk07.atlas.cogentco.com (154.54.12.66)  439.159 ms
14  ntt.jfk07.atlas.cogentco.com (154.54.11.66)  408.818 ms
    ntt.jfk07.atlas.cogentco.com (154.54.12.66)  408.670 ms
    xe-1-0-4.ar1.nyc3.us.nlayer.net (69.31.34.182)  408.557 ms
15  vlan-75.ar2.ewr1.us.nlayer.net (69.31.34.129)  379.485 ms
    xe-1-0-4.ar1.nyc3.us.nlayer.net (69.31.34.182)  410.174 ms  336.119 ms
16  as20473.ae3.ar2.ewr1.us.nlayer.net (69.31.34.214)  344.904 ms  337.696 ms
    vlan-75.ar2.ewr1.us.nlayer.net (69.31.34.129)  334.080 ms
17  as20473.ae3.ar2.ewr1.us.nlayer.net (69.31.34.214)  525.148 ms
    vl3-c58-c6-1.ewr3.choopa.net (66.55.134.186)  410.140 ms  344.993 ms
18  vl3-c58-c6-1.ewr3.choopa.net (66.55.134.186)  339.300 ms  336.144 ms *
19  209.222.7.86 (209.222.7.86)  338.480 ms *
    209.222.7.82 (209.222.7.82)  377.867 ms
20  209.222.23.221 (209.222.23.221)  429.095 ms  317.710 ms
    209.222.7.86 (209.222.7.86)  400.922 ms

Hi,

Thank you for the results, I have logged this with our Technical Specialists and as soon as I hear anything from them, I will inform you thereof.

Regards,
MWEB Guy
 
I now did a mediafire test, downloads don't even start, they time out.

Code:
C:\Windows\system32>ping mediafire.com

Pinging mediafire.com [205.196.120.6] with 32 bytes of data:
Reply from 205.196.120.6: bytes=32 time=369ms TTL=45
Reply from 205.196.120.6: bytes=32 time=369ms TTL=45
Reply from 205.196.120.6: bytes=32 time=369ms TTL=45
Reply from 205.196.120.6: bytes=32 time=368ms TTL=45

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

C:\Windows\system32>tracert mediafire.com

Tracing route to mediafire.com [205.196.120.6]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  192.168.0.1
  2     8 ms     7 ms     7 ms  41-133-48-1.dsl.mweb.co.za [41.133.48.1]
  3    23 ms    23 ms    22 ms  tengig-0-0-0-101.vic-ipc-1.mweb.co.za [196.22.169.134]
  4    24 ms    23 ms    24 ms  vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
  5    25 ms    24 ms    26 ms  TenGigE0-1-0-0.12.vic-up-1.mweb.co.za [196.22.169.241]
  6    29 ms    27 ms    26 ms  tengige0-3-1-0.mid-up-1.mweb.co.za [196.22.169.94]
  7   255 ms   255 ms   255 ms  pos-1-2-0.lon-up-1.mweb.co.za [196.22.163.230]
  8   262 ms   257 ms   261 ms  149.6.98.5
  9   269 ms   260 ms   259 ms  te7-6.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
 10   334 ms   334 ms   334 ms  te0-3-0-4.mpd21.lon13.atlas.cogentco.com [154.54.57.90]
 11   340 ms   336 ms   337 ms  te0-3-0-4.ccr21.bos01.atlas.cogentco.com [154.54.30.129]
 12   341 ms   337 ms   336 ms  te0-2-0-1.mpd21.jfk02.atlas.cogentco.com [154.54.44.9]
 13   344 ms   343 ms   343 ms  te0-0-0-6.mpd21.dca01.atlas.cogentco.com [154.54.5.98]
 14   369 ms   368 ms   367 ms  te0-1-0-7.mpd21.atl01.atlas.cogentco.com [154.54.1.225]
 15   374 ms   362 ms   362 ms  te0-0-0-1.mpd21.iah01.atlas.cogentco.com [154.54.24.6]
 16   375 ms   368 ms   367 ms  te4-1.ccr01.iah03.atlas.cogentco.com [154.54.7.198]
 17   365 ms   376 ms   365 ms  GDD.demarc.cogentco.com [38.104.60.138]
 18   368 ms   404 ms   369 ms  205.196.120.6
 
MWEB Guy - internet has been extra faulty for the past few days... What's going on! If anything, since the cable break the other day, its been crap to say the least! My Torrents are Dead, with the odd 0.3k flicker here and there... The music sites I buy from loads, but i have to constantly refresh to tracks to get them to play. The online radio station i'm listening to tonight, buffers badly from time to time, right now its playing... All the popular sites seem to run okayish... but the rest of it... slow! VERY Slow... Browsing feels like 384k at best...

Mybroadband is also crawling!...

1437390487.png


1437404951.png


for 4meg, not good at all!.......
 
Last edited:
MWEB Guy - internet has been extra faulty for the past few days... What's going on! If anything, since the cable break the other day, its been crap to say the least! My Torrents are Dead, with the odd 0.3k flicker here and there... The music sites I buy from loads, but i have to constantly refresh to tracks to get them to play. The online radio station i'm listening to tonight, buffers badly from time to time, right now its playing... All the popular sites seem to run okayish... but the rest of it... slow! VERY Slow... Browsing feels like 384k at best...

Mybroadband is also crawling!...

1437390487.png


1437404951.png


for 4meg, not good at all!.......

Hi LabAnimal,

I had a look at your account, everything seems fine, your line readings as well. What I would suggest is contact Telkom, have them re-create your port and test thereafter. Please keep me posted.

Regards,
MWEB Guy
 
Hey mweb guy. Can you tell me if mweb added any new sites to their shaping list?I used to get full line speed on a service I pay for and no longer do since today. Did a speedtest to US and london servers anf getting proper line speed. P
 
Hey mweb guy. Can you tell me if mweb added any new sites to their shaping list?I used to get full line speed on a service I pay for and no longer do since today. Did a speedtest to US and london servers anf getting proper line speed. P

Hi zain76,

There has been no change to our shaping policy that I am aware of.

Regards,
MWEB Guy
 
My mweb is fine so far, I can't complain, my fileserve and filesonic is dead, sometimes filesonic downloads but fileserve is dead for the past 2 days. It is not mweb at fault on my side cause fileserve is even not working on my afrishost account...don't know what's up with fileserve
 
My mweb is fine so far, I can't complain, my fileserve and filesonic is dead, sometimes filesonic downloads but fileserve is dead for the past 2 days. It is not mweb at fault on my side cause fileserve is even not working on my afrishost account...don't know what's up with fileserve

This is the message on the fileserve site.

Dear FileServe users,

For the next 48 hours, the API will undergo maintenance. This renders some 3rd party programs (JDownloader, Fileserve Manager, et.al.) to not function properly.

We suggest that you use either our Web Interface, IDM or MiPony to download your necessary files.

We apologize for any inconvenience caused
Best regards,
FileServe
 
Ok so for the past 3 days I have been unable to raid in WoW. Last week I was perfect. Something happened on the weekend and I have no idea what it was. I am getting terrible spike lag and it makes the game unplayable during times of high throughput. I am currently using Mweb Uncapped Unshaped 1mbit. For literally the past 3 months I have had 0 problems with it. Since Sunday night I have been unable to raid, which is highly frustrating. I thought it was my Mweb account so I purchased 1 gig of Unshaped Bandwidth from WebAfrica which uses Sat3 instead of Seacom. Still the same problems. I logged a fault with Telkom but they said there is nothing wrong with my line. I looked at the router stats and nothing has really changed, some downstream Noise Margin fluctuations which I guess are normal. I did a tracert to eu.logon.battle.net and simultaneously pinged the congentco hop and the next hop which was to Telia. The Congentco hop had 0 packet loss while the Telia hop had about 2% of packet loss. I have no idea what is going on. Please help me.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X