Dear Swisscom Routing-Experts

Are you not peeing at swissIX anymore?

Your webserver www.swisscom.ch (2a02:a90:c400:4001::2) gives me a hard time to be reached. Either it wants it traffic to be routed from Berne via NL, UK, US and ends in a sinkhole or it uses what looks like using private peering from tineo/netrics/finecom to the same sinkhole:

tracepath6 2a02:a90:c400:4001::2  1?: [LOCALHOST]                        0.367ms pmtu 1500  1:  sv96.hilotec.net                                      0.776ms  1:  sv96.hilotec.net                                      0.740ms  2:  2a00:c38::1:0:2a                                      1.538ms  3:  lo0.01.p.cbn.ch.as15576.nts.ch                        1.725ms  4:  lo0.01.p.czh.ch.as15576.nts.ch                        4.075ms  5:  lo0.02.p.czh.ch.as15576.nts.ch                        4.354ms  6:  zayog.swissix.ch                                     10.184ms  7:  no reply  8:  ae2.cs1.ams17.nl.eth.zayo.com                       151.857ms asymm 25  9:  no reply 10:  no reply 11:  no reply 12:  ae5.cs1.lhr11.uk.eth.zayo.com                       153.354ms asymm 21 13:  no reply 14:  2001:438:ffff::407d:1d13                            151.202ms asymm 19 15:  ae6.cs1.sjc2.us.eth.zayo.com                        159.227ms asymm 18 16:  ae9.mpr1.pao1.us.zip.zayo.com                       152.345ms 17:  2001:438:fffe::2456                                 153.873ms asymm 10 18:  2001:c10:80:1::e51                                  259.737ms asymm 10 19:  2001:c10:80:1::b96                                  265.511ms asymm 11 20:  2001:c10:80:2::ad2                                  243.109ms asymm 10 21:  geb-030-lo0-0.ip6.ip-plus.net                       247.019ms asymm  9 22:  geb-015-loo6.ip6.ip-plus.net                        236.957ms asymm  8 23:  gem-005-loo6.ip6.ip-plus.net                        242.943ms asymm  8 24:  2001:918:100:63::1                                  230.491ms asymm  7 25:  2001:918:100:4c::1                                  240.121ms asymm  8 26:  2001:918:100:52::1                                  247.741ms asymm  7 27:  2001:918:ce::49                                     241.013ms asymm  8 28:  2a02:a90:4024:fff::14                               247.804ms asymm  9 29:  2a02:a90:4024:fff::15                               234.473ms asymm  8 30:  no reply      Too many hops: pmtu 1500      Resume: pmtu 1500

tracepath 2a02:a90:c400:4001::2  1?: [LOCALHOST]                        0.030ms pmtu 1500  1:  router.3550.ch                                        0.418ms  1:  router.3550.ch                                        0.410ms  2:  bd4.lar01.lna001.bb.fcom.ch                           4.561ms  3:  no reply  4:  no reply  5:  2001:4d98:a000::1b4                                   3.218ms asymm  4  6:  zhh-015-lo0-0.ip6.ip-plus.net                        11.088ms asymm  5  7:  2001:918:ce::45                                       6.146ms asymm  6  8:  2a02:a90:4024:fff:8000::15                            5.452ms  9:  no reply 10:  no reply 11:  no reply 12:  no reply 13:  no reply 14:  no reply 15:  no reply 16:  no reply 17:  no reply 18:  no reply 19:  no reply 20:  no reply 21:  no reply 22:  no reply 23:  no reply 24:  no reply 25:  no reply 26:  no reply 27:  no reply 28:  no reply 29:  no reply 30:  no reply      Too many hops: pmtu 1500      Resume: pmtu 1500

Is that a management decision or a technical issue?

Cheers

Jean-Pierre