 |
 |
This isn't a MICE-related question, but since so many MICE members are in the Minnesota area I thought I would ask. Sunday morning from 1:11 am to about 4:20 am we saw an unusually high number of websites time out over IPv6. We monitor 50 IPv6-enabled web sites over IPv6, performing both an ICMP check (if possible) and then HTTP over IPv6. There were at least 17 sites during that time frame that timed out on our monitoring systems' HTTP GET request. One pattern emerged -- 14 of them traceroute through an XO link that goes through Minneapolis. Here's a sample: traceroute to ipv6.test.Level3.com (2001:1900:2018:3000::105) from 2607:fe28:0:1000::5, port 80, from port 36274, 30 hops max, 60 bytes packets 1 router-core.mtcnet.net (2607:fe28:0:1000::1) 0.395 ms 0.325 ms 0.319 ms 2 sxct.sxcy.mtcnet.net (2607:fe28:11:1002::197) 0.188 ms 0.135 ms 0.185 ms 3 v6-premier.sxcy-mlx.fbnt.netins.net (2001:5f8:7f0a:2::1) 1.612 ms 1.545 ms 1.613 ms 4 v6-ins-db1-te-13-2-219.desm.netins.net (2001:5f8:1:1::1) 6.667 ms 6.566 ms 8.002 ms 5 v6-ins-dc1-et-8-2.desm.netins.net (2001:5f8::1:1) 6.624 ms 7.995 ms 6.602 ms 6 2610:18:18b:c000::11 (2610:18:18b:c000::11) 12.108 ms 12.075 ms 12.137 ms 7 mcr1.minneapolis-mn.us.xo.net (2610:18::30b8) 21.431 ms 21.452 ms 21.421 ms 8 vb1710.rar3.chicago-il.us.xo.net (::ffff:216.156.0.169) 30.701 ms 23.639 ms 23.771 ms .... I then looked at the daily traceroutes we have on file for all 50 sites we monitor and it looks like 15 of them go through XO. So over 93% (14 out of 15) of the sites that go through XO timed out during the 1:11 am to 4:20 am time period. Did anyone with XO connectivity see issues Sunday morning? Frank ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1