MWEB Int. Down?!

MonTage

Well-Known Member
Joined
Oct 13, 2009
Messages
309
Reaction score
0
Hey does anyone know if international is down, i can only browse local sites
 
Only select local sites it seems and that too very slow...........
 
Hey does anyone know if international is down, i can only browse local sites

Seems to come and go. And by the traceroutes it seems that MWEB is switching between different links at the moment. May be a while before everything is stable. Right now:

Code:
 2  41-133-86-1.dsl.mweb.co.za (41.133.86.1)  6.954 ms  8.680 ms  9.137 ms
 3  tengig-0-0-0-110.vic-ipc-1.mweb.co.za (196.22.169.170)  12.983 ms  14.105 ms  15.901 ms
 4  vl-92.vic-hscore-2.mweb.co.za (196.22.189.3)  16.972 ms  18.052 ms  20.572 ms
 5  * * *
 6  jx2621-1-S1-AP.mweb.net (196.22.163.5)  26.788 ms  27.906 ms  25.833 ms
 7  tenet.jinx.net.za (198.32.142.33)  26.920 ms  27.896 ms  28.858 ms
 8  cpt1-t101-bfn1-t100.net.tenet.ac.za (155.232.6.38)  55.865 ms  53.977 ms  54.150 ms
 9  unknown.uni.net.za (155.232.253.254)  246.574 ms  244.210 ms  244.862 ms
10  209.85.248.215 (209.85.248.215)  246.076 ms  241.822 ms  242.119 ms
11  209.85.252.44 (209.85.252.44)  262.098 ms  260.972 ms  258.965 ms
12  72.14.232.134 (72.14.232.134)  248.103 ms  230.990 ms  229.953 ms
13  216.239.49.45 (216.239.49.45)  229.802 ms 209.85.252.83 (209.85.252.83)  258.897 ms  257.259 ms
14  209.85.243.81 (209.85.243.81)  237.103 ms 209.85.243.77 (209.85.243.77)  240.140 ms 209.85.243.81 (209.85.243.81)  234.129 ms
15  google-public-dns-a.google.com (8.8.8.8)  231.946 ms  231.596 ms  230.106 ms

Seems they are using TENET's links.
 
Some international is working for me but most just times out, starting to consider other isp's atm :whistle:
 
AFAIK Google is cached on TENET, so that tracert may not be representative.

The primary TENET-SEACOM graph has been dead since 5.30am:
http://monitor.net.tenet.ac.za/cacti/graph_view.php?action=tree&tree_id=6&leaf_id=874

Seems this has changed. More route tweaking, likely.

Code:
 2  41-133-86-1.dsl.mweb.co.za (41.133.86.1)  6.923 ms  8.954 ms  9.982 ms
 3  tengig-0-0-0-110.vic-ipc-1.mweb.co.za (196.22.169.170)  12.363 ms  14.835 ms  15.051 ms
 4  vl-92.vic-hscore-2.mweb.co.za (196.22.189.3)  17.745 ms  18.428 ms  20.921 ms
 5  tengig-0-0-0-0-12.vic-up-2.mweb.co.za (196.22.169.242)  23.637 ms  23.809 ms  26.806 ms
 6  tengig-0-3-1-0.mid-1.mweb.co.za (196.22.169.211)  29.034 ms  29.695 ms  29.130 ms
 7  pos-0-0-0-0.lon-1.mweb.co.za (196.22.163.230)  369.548 ms  370.226 ms *
 8  195.66.224.125 (195.66.224.125)  372.053 ms  370.992 ms  371.761 ms
 9  64.233.175.27 (64.233.175.27)  372.281 ms  371.138 ms  372.122 ms
10  66.249.95.173 (66.249.95.173)  377.123 ms  375.874 ms  377.005 ms
11  209.85.251.231 (209.85.251.231)  377.055 ms 72.14.236.191 (72.14.236.191)  374.976 ms  376.578 ms
12  209.85.243.81 (209.85.243.81)  384.030 ms 209.85.243.73 (209.85.243.73)  359.943 ms 209.85.243.81 (209.85.243.81)  364.115 ms
13  google-public-dns-a.google.com (8.8.8.8)  356.933 ms  356.259 ms  356.983 ms

MWEB -> London is now up, as hop #8 is registered to LINX (London Internet Exchange).
 
My guess is that traffic may be going via another cable such as SEA-ME-WE-3 (which only has 25% of the capacity). This would explain the severe congestion...
 
Wonder whose trying to hijack that Seacom cable again?

Sent from my iPhone using Tapatalk
 
Top
Sign up to the MyBroadband newsletter
X