MWEB Uncapped Subscribers Feedback

[SabreWolfy]

http://mybroadband.co.za/news/telecoms/12208-SEACOM-still-down.html

 

[hambone]

Everyone back up and running? Torrents averaging around 60Kb/s here... back to the Off Peak complaints

 

[cavedog]

Everyone back up and running? Torrents averaging around 60Kb/s here... back to the Off Peak complaints

Ive been getting 160kbs all day on Usenet. p2p going @ 60kbs

 

[hambone]

Would anyone be able to tell me whether MWEB traffic is going along SEACOM again?

Tracing route to www.l.google.com [74.125.79.147]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  . [192.168.2.1]
  2     *        *        *     Request timed out.
  3    44 ms    43 ms    42 ms  tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.16
9.170]
  4    49 ms    46 ms    43 ms  vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
  5    76 ms   194 ms    60 ms  tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.16
9.241]
  6    46 ms    44 ms    50 ms  rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.
249]
  7   255 ms   255 ms   254 ms  lon-ip-dir-telecity-gig-4-0-1025.telkom-ipnet.co
.za [196.43.18.121]
  8   285 ms   265 ms   278 ms  221-76-245-83.packetexchange.net [83.245.76.221]

  9   269 ms   271 ms   268 ms  209.85.252.76
 10   286 ms   270 ms   270 ms  216.239.43.123
 11   271 ms   270 ms   375 ms  72.14.239.197
 12   269 ms   280 ms   272 ms  209.85.255.118
 13   268 ms   277 ms   281 ms  ey-in-f147.1e100.net [74.125.79.147]

Trace complete.

 

[randomwalsh]

is anyone else having problems accessing the site demonoid?

 

[Gordon_R]

Would anyone be able to tell me whether MWEB traffic is going along SEACOM again?

Tracing route to www.l.google.com [74.125.79.147]
over a maximum of 30 hops:

6 46 ms 44 ms 50 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]

If you see telkom-ipnet.co.za in a tracert then its not via SEACOM.

You may have to try a few sites, since each is routed differently. I haven't found any yet, so MWeb may still be using mostly SAT-3.

Edit: I found an isolated site route that goes via SEACOM and TE Data (Egypt). That may change as MWeb reconfigures.

 

[greywolfe]

is anyone else having problems accessing the site demonoid?

they currently have a denial of service attack problem.

 

[SabreWolfy]

[-]Tracepaths to MWeb or MyBroadband take about 120ms to get to the first node (MWeb), with the entire tracepath taking about 135ms. Once before when I experienced this I followed advice to restart my router, which solved the problem. Not so this time. Any suggestions?[/-]

Edit: Curious. I notice that the tracepath (to a site in the UK) is (still) routing via Telkom. Not that this would make the first node slow though.

 

[Yarik11]

I still have terrible speeds. News crawling at 63 kb/s. Did a speed test and got something like 0.83 MB for download and 0.19 MB for upload

 

[hambone]

If you see telkom-ipnet.co.za in a tracert then its not via SEACOM.

You may have to try a few sites, since each is routed differently. I haven't found any yet, so MWeb may still be using mostly SAT-3.

Thanks for that, running trace routes can get very addictive.

 

[submethod]

is anyone else having problems accessing the site demonoid?

It's down... http://torrentfreak.com/demonoid-faces-major-downtime-once-again-100428/

 

[Wasp_21]

they currently have a denial of service attack problem.

What does that mean? tried last night...very bad. Hope they not going down again.

 

[Gordon_R]

Bump.

Does anyone else notice that MWeb (local) ping times from Cape Town are very slow today (lunchtime Mon 3rd)?

   1   <10 ms   <10 ms   <10 ms  home.gateway [192.168.1.254]
   2     7 ms     7 ms     6 ms  41-132-48-1.dsl.mweb.co.za [41.132.48.1]
   3    94 ms    95 ms    94 ms  tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.169.146]

 

[SabreWolfy]

Bump.

Does anyone else notice that MWeb (local) ping times from Cape Town are very slow today (lunchtime Mon 3rd)?

   1   <10 ms   <10 ms   <10 ms  home.gateway [192.168.1.254]
   2     7 ms     7 ms     6 ms  41-132-48-1.dsl.mweb.co.za [41.132.48.1]
   3    94 ms    95 ms    94 ms  tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.169.146]

Restarting my router has previously solved this for me...

(Is that a ping or a tracepath?)

 

[Gordon_R]

Restarting my router has previously solved this for me...

(Is that a ping or a tracepath?)

Those are the first 3 hops of tracert (to any destination via MWeb). I have consistently got 30ms for the last month, ever since MWeb's last routing problem:
http://mybroadband.co.za/vb/showthread.php?223147-Tracert-on-Mweb-uncapped
http://mybroadband.co.za/vb/showthread.php?223531-Mweb-local-pings!!!!!!!

If it were my router, then the 2nd hop would be slow (and my CRC errors would be high).

The fact that the delay is between the 2nd and 3rd hop indicates to me that there is congestion on MWeb's circuit between my DSLAM and the Victory Park 10Gbps Metro Ethernet hub. This may be due to Telkom, or MWeb reconfiguring their network.

I was just curious if anyone else had noticed this?

 

[SabreWolfy]

Seems to be the case:

 2:  home.gateway (192.168.1.254)                           0.519ms pmtu 1492
 2:  *****.dsl.mweb.co.za (*****)             118.932ms 
 3:  tengig-0-0-0-110.vic-ipc-1.mweb.co.za (196.22.169.170) 120.574ms asymm  4

 

[aborg]

Browsing and general internet speed really sucked the last two days (April was really good)... can barely get past 0.2 Mb/s for download on speedtest.net doesn't matter where I test from in the world. My steam updates are also very slow. The term hook line and sinker comes to mind.... please don't let it be true Mr MWEB.

 

[farimir]

I am also starting to feel a bit ticket off with these slow speeds. Utterly useless at the moment.

 

[Gordon_R]

I'm guessing, but last time MWeb did some network 'reconfiguration' things were very slow for a day or two. In the Q&A thread the MWeb representative suggests that this process may be happening now, and the current mismatch between demand and capacity is causing a bottleneck:
http://mybroadband.co.za/vb/showthr...cial-Q-amp-A&p=3871980&viewfull=1#post3871980

It is also possible that the extra bandwidth that was purchased as an alternative for SEACOM downtime has now expired, or been exceeded by uptake in demand from new users.

It may just be very heavy congestion, since many people were 'warned-off' about SEACOM, and may have returned en-masse today. At least we can be fairly sure its not SEACOM itself thats to blame...

 

[gregmcc]

Speeds are really low atm - only getting a max of 80Kbps for the past few hours