tedjp

Update: This has been fixed

For the last week or so, Comcast's IPv6 routing from Salt Lake City to Denver has been hosed. It's dropping packets, not even sending ICMPv6 failure messages. I thought users here might be outraged on my behalf and get it seen by someone who has the power to get it fixed.

Tracing route to he.net [2001:470:0:76::2] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 2601:b:5880:520:xxxx:xxxx:xxxx:xxxx
2 9 ms 8 ms 8 ms 2001:558:6008:40::1
3 8 ms 8 ms 8 ms te-0-5-0-4-sur02.orem.ut.utah.comcast.net [2001:558:102:2036::1]
4 12 ms 14 ms 13 ms te-0-7-0-0-ar02.sandy.ut.utah.comcast.net [2001:558:100:63::1]
5 11 ms 14 ms 14 ms te-7-4-ar02.

With the success of World IPv6 Day 2011, it seems the result was that brokenness was very minor and with IPv6 becoming increasingly prominent in peoples minds, how about we have another World IPv6 Day in 2012 for the purpose of enabling IPv6, AAAA records and leaving it on.

It would give slow-movers a target date to aim for rather than dragging their heels indefinitely, and by co-ordinating the "turn-on" of major websites on a single day, there's an improved chance of quick diagnosis & remedy for users with problems.