IPv6 side of www.charter.com has been down since Friday, September 16 5:12 am Central

The IPv6 side of www.charter.com has been down since Friday, September 16
5:12 am Central. Emails to their NOC have gone unanswered. If anyone on
list can nudge their ops group that would be appreciated.

Frank

nagios:/home/fbulk# wget -6 www.charter.com
--2011-09-19 08:23:58-- http://www.charter.com/
Resolving www.charter.com... 2607:f428:3:1:80:80:80:1
Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed:
Connection timed out.
Retrying.

--2011-09-19 08:24:20-- (try: 2) http://www.charter.com/
Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed:
Connection timed out.
Retrying.

--2011-09-19 08:24:43-- (try: 3) http://www.charter.com/
Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed:
Connection timed out.
Retrying.

--2011-09-19 08:25:07-- (try: 4) http://www.charter.com/
Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed:
Connection timed out.
Retrying.

--2011-09-19 08:25:32-- (try: 5) http://www.charter.com/
Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed:
Connection timed out.
Retrying.

--2011-09-19 08:25:58-- (try: 6) http://www.charter.com/
Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed:
Connection timed out.
Retrying.

--2011-09-19 08:26:25-- (try: 7) http://www.charter.com/
Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed:
Connection timed out.
Retrying.

--2011-09-19 08:26:53-- (try: 8) http://www.charter.com/
Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed:
Connection timed out.
Retrying.

--2011-09-19 08:27:22-- (try: 9) http://www.charter.com/
Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed:
Connection timed out.
Retrying.

--2011-09-19 08:27:52-- (try:10) http://www.charter.com/
Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed:
Connection timed out.
Retrying.

--2011-09-19 08:28:23-- (try:11) http://www.charter.com/
Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed:
Connection timed out.
Retrying.

--2011-09-19 08:28:54-- (try:12) http://www.charter.com/
Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed:
Connection timed out.
Retrying.

--2011-09-19 08:29:25-- (try:13) http://www.charter.com/
Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed:
Connection timed out.
Retrying.

--2011-09-19 08:29:56-- (try:14) http://www.charter.com/
Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed:
Connection timed out.
Retrying.

--2011-09-19 08:30:27-- (try:15) http://www.charter.com/
Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed:
Connection timed out.
Retrying.

--2011-09-19 08:30:58-- (try:16) http://www.charter.com/
Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed:
Connection timed out.
Retrying.

--2011-09-19 08:31:29-- (try:17) http://www.charter.com/
Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed:
Connection timed out.
Retrying.

--2011-09-19 08:32:00-- (try:18) http://www.charter.com/
Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed:
Connection timed out.
Retrying.

--2011-09-19 08:32:31-- (try:19) http://www.charter.com/
Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed:
Connection timed out.
Retrying.

--2011-09-19 08:33:02-- (try:20) http://www.charter.com/
Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed:
Connection timed out.
Giving up.

nagios:/home/fbulk#

Works fine here.

# wget -6 www.charter.com
--2011-09-19 10:24:37-- http://www.charter.com/
Resolving www.charter.com... 2607:f428:3:1:80:80:80:1
Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `index.html'

    [
<=>
] 112,940 288K/s in 0.4s

2011-09-19 10:24:43 (288 KB/s) - `index.html' saved [112940]

traceroute to www.charter.com (2607:f428:3:1:80:80:80:1), 30 hops max, 80
byte packets
1 2607:f2f8:xxxx::1 (2607:f2f8:xxxx::1) 18.721 ms 18.699 ms 18.689 ms
2 2001:504:13::1a (2001:504:13::1a) 1.256 ms 1.672 ms 1.428 ms
3 10gigabitethernet1-2.core1.den1.he.net (2001:470:0:15d::1) 26.498 ms
26.486 ms 26.466 ms
4 10gigabitethernet1-1.core1.chi1.he.net (2001:470:0:1af::1) 49.986 ms
49.529 ms 49.521 ms
5 2001:470:0:114::2 (2001:470:0:114::2) 50.105 ms 49.632 ms 49.626 ms
6 bbr02chcgil-tge0-1-0-0.il.chcg.charter.com (2001:506:100:313::1) 55.805
ms 54.254 ms bbr02chcgil-tge0-0-0-0.il.chcg.charter.com(2001:506:100:305::1)
55.880 ms
7 bbr01olvemo-tge0-4-0-4.mo.olve.charter.com (2001:506:100:55::1) 69.465
ms 63.351 ms 63.314 ms
8 bdr01tncomo-tge1-1.mo.tnco.charter.com (2001:506:100:23::2) 60.018 ms
59.597 ms 59.586 ms
9 2001:506:100:6c::2 (2001:506:100:6c::2) 60.251 ms 60.245 ms 60.236 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *

I've been told by someone else offline that it's fine for them, too. Last
hop according to tcptraceroute6 is Qwest. Anyone else going to
www.charter.com (IPv6) through Qwest?

nagios:/home/fbulk# tcptraceroute6 www.charter.com

traceroute to www.charter.com (2607:f428:3:1:80:80:80:1) from
2607:fe28:0:1000::5, port 80, from port 43838, 30 hops max, 60 bytes packets

1 2607:fe28:0:1003::2 (2607:fe28:0:1003::2) 1.075 ms 1.258 ms 1.857 ms

2 router-core.mtcnet.net (2607:fe28:0:1000::1) 1.625 ms 2.271 ms 1.331
ms

3 sxct.sxcy.mtcnet.net (2607:fe28:11:1002::197) 2.581 ms 1.568 ms 1.215
ms

4 v6-siouxcenter.sxcy.137.netins.net (2001:5f8:7f06::5) 3.347 ms 3.007 ms
2.640 ms

5 v6-ins-db1-te-13-2-219.desm.netins.net (2001:5f8:1:1::1) 7.441 ms 7.121
ms 6.798 ms

6 v6-ins-dc1-et-8-2.desm.netins.net (2001:5f8::1:1) 8.682 ms 8.294 ms
7.910 ms

7 2001:428:3801:210:0:1:0:1 (2001:428:3801:210:0:1:0:1) 20.790 ms 20.447
ms 20.133 ms

8 * * *

9 * * *

10 * * *

11 * * *

12 * * *

13 * * *

14 * * *

15 * * *

16 * * *

17 * * *

18 * * *

19 * * *

20 * * *

21 * * *

22 * * *

23 * * *

24 * * *

25 * * *

26 * * *

27 * * *

28 * * *

29 * * *

30 * * *

nagios:/home/fbulk#

Frank

It looks like we have identified the issue, and we are currently working to resolve as quickly as possible.

-Brian

Our monitoring system reported that the site now is accessible -- thanks!

Frank