MWEB Uncapped Subscribers Feedback

Status
Not open for further replies.
Our engineers picked up some issues on one of the London peering links and have rerouted traffic temporarily while they address the issue. It should settle down again shortly, please let me know if you are still having problems.

Zero connectivity in CT at 11am. DNS fails (Edit:bbc.co.uk dead...)
 
Last edited:
11:05am, it lives again! Probably going to be back to the same WoW issues we had before the upgrade in CT though.
 
Tracing route to bbc-vip112.telhc.bbc.co.uk [212.58.244.67]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 17 ms 17 ms 32 ms 41-132-50-1.dsl.mweb.co.za [41.132.50.1]
3 16 ms 16 ms 16 ms tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.16
9.170]
4 25 ms 16 ms 16 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 18 ms 19 ms 23 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.16
9.241]
6 25 ms 16 ms 16 ms g-0-3-vic-jinx-2.mweb.co.za [196.22.163.1]
7 52 ms 241 ms 211 ms tenet.jinx.net.za [198.32.142.33]
8 32 ms 31 ms 31 ms dur1-t100-pta1-t45.net.tenet.ac.za [155.232.6.30
]
9 31 ms 31 ms 29 ms dur2.lb.net.tenet.ac.za [155.232.2.5]
10 356 ms 315 ms * lnd1-ub-pos400-dur1-pos300.net.tenet.ac.za [196.
32.209.45]
11 260 ms 253 ms 252 ms 83.231.146.65
12 263 ms 254 ms 255 ms 129.250.3.46
13 252 ms 250 ms 250 ms 129.250.2.77
14 249 ms 243 ms 245 ms bbc-gw0-linx.prt0.thdoe.bbc.co.uk [195.66.224.10
3]
15 265 ms 262 ms 269 ms 212.58.238.153
16 264 ms 261 ms 262 ms 212.58.239.62
17 245 ms 244 ms 252 ms 212.58.251.44
18 326 ms 262 ms 312 ms bbc-vip112.telhc.bbc.co.uk [212.58.244.67]

Trace complete.


That's what I get.
 
My voip phone reconnected to the UK, my vpn to my office is working fine (it's a local connection though). But WoW still states I have no internet connectivity. :< Was hoping to get some farming done..
 
Mine is cutting in and out. Can't even access local at times.
 
Just received some feedback now Gordon, it seems the problem is a bit more serious than the original assessment. Our engineers are attending to this urgently and notices are posted. We will update you as soon as we have an ETR.
 
I just switched to my freeadsl.co.za @tlantic account, everything working fine.
 
Code:
7 52 ms 241 ms 211 ms tenet.jinx.net.za [198.32.142.33]
8 32 ms 31 ms 31 ms dur1-t100-pta1-t45.net.tenet.ac.za [155.232.6.30]
9 31 ms 31 ms 29 ms dur2.lb.net.tenet.ac.za [155.232.2.5]
10 356 ms 315 ms * lnd1-ub-pos400-dur1-pos300.net.tenet.ac.za [196.32.209.45]

That's what I get.

Looks like MWeb is routing via JINX-TENET-SEACOM. Weird...

Edit: You can see a spike on the TENET-SEACOM graph around 11am:
http://monitor.net.tenet.ac.za/cacti/graph_view.php?action=tree&tree_id=6&leaf_id=874

P.S. I'm still dead on CT DNS to bbc.co.uk.

Edit: CT DNS seems better at 11.20am.
 
Last edited:
My voip phone reconnected to the UK, my vpn to my office is working fine (it's a local connection though). But WoW still states I have no internet connectivity. :< Was hoping to get some farming done..

Similar problems here with Aion. And the ping lowering service I use is having major problems right now..

Just received some feedback now Gordon, it seems the problem is a bit more serious than the original assessment. Our engineers are attending to this urgently and notices are posted. We will update you as soon as we have an ETR.

Horrifying. Lets hope this doesn't last till the new year.
 
I found going to Google DNS helped me, which makes no sense if International is wonky.
 
International traffic from CT seems to be back to 'normal' now (latency 160ms), but MWeb are using alternate routing in London (CogentCo and Telia.net, instead of the previous Above.net).

I have no idea what routing Joburg users are on, but the CINX, JINX and TENET-SEACOM graphs have dropped to normal levels since 11.30am:
http://stats.jinx.net.za/showtotal.php?img=hour

Code:
Tracing route to newswww.bbc.net.uk [212.58.246.83]
over a maximum of 30 hops:

   1   <10 ms   <10 ms   <10 ms  home.gateway [192.168.1.254]
   2     6 ms     7 ms     6 ms  41-132-48-1.dsl.mweb.co.za [41.132.48.1]
   3     8 ms     8 ms     8 ms  196-28-178-166.adsl.mweb.co.za [196.28.178.166]
   4    34 ms     8 ms     8 ms  196-28-179-11.adsl.mweb.co.za [196.28.179.11]
   5     9 ms    10 ms    10 ms  196-28-178-97.adsl.mweb.co.za [196.28.178.97]
   6   159 ms   159 ms   160 ms  196.22.164.2
   7   159 ms   160 ms   159 ms  149.6.98.17
   8   268 ms   499 ms   160 ms  te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
   9   160 ms   160 ms   160 ms  te4-4.mpd02.lon01.atlas.cogentco.com [130.117.1.134]
  10   160 ms   160 ms   159 ms  ldn-b4-link.telia.net [213.248.70.237]
  11   160 ms   160 ms   160 ms  ldn-bb2-link.telia.net [80.91.246.146]
  12   159 ms   159 ms   160 ms  ldn-b3-link.telia.net [80.91.254.17]
  13   160 ms   160 ms   160 ms  siemens-ic-119241-ldn-b2.c.telia.net [213.248.104.70]
  14   160 ms   161 ms   161 ms  212.58.238.133
  15   161 ms   161 ms   161 ms  te12-1.hsw0.cwwtf.bbc.co.uk [212.58.239.222]
  16   161 ms   161 ms   162 ms  212.58.255.12
  17   161 ms   162 ms   178 ms  newswww.bbc.net.uk [212.58.246.83]

Trace complete.
 
We seem to be back to normal now via alternate routing. I have not cleared the outage notice yet as engineers have not officially cleared the fault. Our networks notices page was updated just before 11h00 Gordon so not sure why you couldn't see it, perhaps you had the page cached?
 
We seem to be back to normal now via alternate routing. I have not cleared the outage notice yet as engineers have not officially cleared the fault. Our networks notices page was updated just before 11h00 Gordon so not sure why you couldn't see it, perhaps you had the page cached?

Not showing for me either, and this is the first time today I am visiting the page. Here's what it looked like at 12:40. All the notices are area-specific.

MWEBnotices1240on2010-12-30.png
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X