Apparently my ISP routes my IPv6 to MikroTik's sites via Hurricane Electric's network. I'm curious if the issues reaching *.mikrotik.com sites only affects people routing along similar paths (i.e. via HE.net), or is more global in nature?
Code: Select all
user@host:~$ ping6 forum.mikrotik.com PING6(56=40+8+8 bytes) --> 2a02:610:7501:1000::201 --- forum.mikrotik.com ping6 statistics --- 100 packets transmitted, 0 packets received, 100.0% packet loss user@host:~$ traceroute6 forum.mikrotik.com traceroute6 to forum.mikrotik.com (2a02:610:7501:1000::201), 64 hops max, 12 byte packets ... 6 v6-10gigabitethernet1-3.core1.sea1.he.net 36.414 ms 40.620 ms 49.199 ms 7 10gigabitethernet3-1.core1.den1.he.net 71.635 ms 68.934 ms 69.898 ms 8 10gigabitethernet1-1.core1.chi1.he.net 108.138 ms 93.704 ms 115.358 ms 9 10gigabitethernet7-2.core1.nyc4.he.net 130.926 ms 143.679 ms 109.993 ms 10 10gigabitethernet3-3.core1.lon1.he.net 176.192 ms 177.757 ms 188.958 ms 11 10gigabitethernet4-2.core1.fra1.he.net 208.305 ms 195.920 ms 200.634 ms 12 * * * 13 * * * ... this continues until I terminate the traceroute ...
Or could MikroTik have their web servers behind a RouterOS router, and perhaps they're finally experiencing the random IPv6 routing issues I keep experiencing with RouterOS and IPv6 routes wherein when my IPv6 connectivity fails, I simply fiddle with my router's IPv6 default route distance (changing it, then changing it back to what it was before) and like magic, the route starts working like it should have in the first place?