Neotel IS peering problem

[boerseun]

We have Neotel 10Mbps fibre at the office, trying to ping our servers at IS up the road in CT and is being routed via Lisbon and London.

 

[kilos]

Its does not seem to be a Neotel IS problem but a CINX - IS peering link went down but is now up
Mweb CINX is still down, look at traceroute below

Neotel has lthe following ocal peering links in Cape Town
MTN Business
Tenet
Telkom SAIX

besides the Neotel - CINX link


traceroute to 196.33.166.200 (196.33.166.200), 30 hops max, 60 byte packets
1 41.164.8.x (41.164.8.x) 2.022 ms 2.259 ms 2.324 ms
2 41.164.20.1 (41.164.20.1) 13.900 ms 13.965 ms 14.031 ms
3 41.164.113.1 (41.164.113.1) 14.931 ms 14.998 ms 15.063 ms
4 41.164.0.244 (41.164.0.244) 15.128 ms 15.194 ms 15.259 ms
5 is.cinx.net.za (196.223.22.10) 15.582 ms 15.648 ms 15.711 ms [CINX]
6 core2a-ctn-gi0-2.ip.isnet.net (168.209.6.6) 19.465 ms 15.999 ms 16.076 ms
7 168.209.100.213 (168.209.100.213) 41.282 ms 41.711 ms 41.851 ms
8 csw5-pkl-te1-7.ip.isnet.net (196.26.0.188) 41.616 ms 41.756 ms csw5-pkl-tg2-7.ip.isnet.net (168.209.1.188) 42.748 ms
9 a196-33-166-200.deploy.akamaitechnologies.com (196.33.166.200) 42.463 ms 42.554 ms 42.635 ms

MWEB
traceroute to speedtest.cpt.mweb.co.za (41.86.121.228), 30 hops max, 60 byte packets
1 41.164.8.x (41.164.8.x) 1.520 ms 1.581 ms 1.903 ms
2 41.164.20.1 (41.164.20.1) 13.088 ms 13.154 ms 13.219 ms
3 41.164.113.1 (41.164.113.1) 13.283 ms 13.929 ms 13.985 ms
4 41.160.0.244 (41.160.0.244) 33.894 ms 35.006 ms 35.071 ms
5 mweb-1.jinx.net.za (196.223.14.25) 35.136 ms 35.938 ms 36.003 ms
6 TenGigE0-2-0-0.vic-up-1.mweb.co.za (196.22.163.6) 60.025 ms 56.246 ms 59.640 ms
7 TenGigE0-0-0-0.cpt-p-1.mweb.co.za (197.84.4.34) 58.878 ms 58.581 ms 59.323 ms
8 196.28.178.115 (196.28.178.115) 55.114 ms 55.305 ms 56.464 ms
9 196.28.178.70 (196.28.178.70) 56.651 ms 56.837 ms 57.014 ms
10 gig5-2-cpt-opt-65-1.optinet.net (196.41.133.166) 57.200 ms 57.385 ms 57.570 ms