International down on Mweb?

And according to Afrihost network status nothing wrong.
 
I am on Seacom line, it's fine, maybe IS is having some issues...
 
Gordon_R said:
MWeb seem to have switched from SEACOM to SAT-3 (all my tracert's indicate that somethign changed just after 2pm).
Click to expand...

I can't ping Mumbai (or Marseilles), the normal route that SEACOM follows, in anything under 400ms.

Since MWeb were having high latency this morning, I would put the blame on Neotel or DFA, since they also manage the gateway to SEACOM.

Eidt: The TENET SEACOM traffic chart shows normal activity:
http://monitor.net.tenet.ac.za/cacti/graph_view.php?action=tree&tree_id=6&leaf_id=874
They have a separate (dedicated) gateway via DFA.
 
Last edited:
My trace with mweb to google.com is going through Turkey?

Proxy trace to
google.com
33 hops / 20.2 seconds

1. Unknown
2. mweb.co.za
3. mweb.co.za
4. mweb.co.za
5. Unknown
6. 195.175.5.70
7. turktelekom.com.tr
8. 212.156.120.30
9. 81.212.212.57
10. turktelekom.com.tr
 
Vonnii said:
My trace with mweb to google.com is going through Turkey?

Proxy trace to
google.com
33 hops / 20.2 seconds

1. Unknown
2. mweb.co.za
3. mweb.co.za
4. mweb.co.za
5. Unknown
6. 195.175.5.70
7. turktelekom.com.tr
8. 212.156.120.30
9. 81.212.212.57
10. turktelekom.com.tr
Click to expand...

MWeb are throwing all their standby bandwidth at the problem, including TE Data (Egypt).

Code: 
Tracing route to www.capetown-webcam.com [87.106.136.238]
over a maximum of 30 hops:

   1   <10 ms   <10 ms   <10 ms  home.gateway [192.168.1.254]
   2     8 ms     8 ms     8 ms  41-132-48-1.dsl.mweb.co.za [41.132.48.1]
   3    29 ms    30 ms    28 ms  tengig-0-0-0-101.vic-ipc-1.mweb.co.za [196.22.169.134]
   4    35 ms    32 ms    28 ms  vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
   5    67 ms    48 ms    58 ms  tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.169.241]
   6    32 ms    32 ms    35 ms  tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]
   7   205 ms   205 ms   206 ms  host-81.10.87.13.tedata.net [81.10.87.13]
   8   208 ms   208 ms   209 ms  host-163.121.209.29.tedata.net [163.121.209.29]
   9   279 ms   210 ms   209 ms  host-163.121.209.34.tedata.net [163.121.209.34]
  10   241 ms   291 ms   249 ms  195.175.5.29
  11   283 ms   277 ms   241 ms  uls-t1-1-ulus-t2-1.turktelekom.com.tr [81.212.29.153]
  12   283 ms   285 ms   241 ms  212.156.119.242
  13   277 ms   295 ms   303 ms  212.156.103.13
  14   312 ms   280 ms   319 ms  linx.bb-d.ba.slo.gb.oneandone.net [195.66.226.98]
  15   281 ms   280 ms   318 ms  te-1-4.bb-c.bap.rhr.de.oneandone.net [212.227.120.42]
  16   311 ms   312 ms   313 ms  ae-11.gw-distp-a.bad.oneandone.net [212.227.122.5]
  17   314 ms   289 ms   360 ms  ae-1.gw-prtr-r161-1a.bad.oneandone.net [195.20.247.56]
  18   311 ms   356 ms   312 ms  www.capetown-webcam.com [87.106.136.238]

Trace complete.
 
Hi All,

Just to confirm, MWEB has experienced an outage on our primary Seacom circuit, we are re-routing via alternate capacity with some slight degradation. Engineers are investigating.

MWB.
 
MWEB said:
Hi All,

Just to confirm, MWEB has experienced an outage on our primary Seacom circuit, we are re-routing via alternate capacity with some slight degradation. Engineers are investigating.

MWB.
Click to expand...

This is why I currently love MWEB, you guys keep us informed and make a plan when Seacom goes down!

MWEB you guys rock!!!
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X