IPv6 version of www.qwest.com/www.centurylink.com has been down for 10 days

Sat Jan 7 21:30:05 UTC 2012

HTTP both www.qwest.com and www.centurylink.com have been in and out since
December 27.  Sometimes it responds in less than 10 seconds, other times it
connects and there's no TCP response for minutes.  This was tested from two
different networks.

If anyone from CenturyLink is lurking, could you please notify your NOC or
IT department?

Frank

-----Original Message-----
From: Frank Bulk [mailto:frnkblk at iname.com] 
Sent: Thursday, December 01, 2011 1:43 PM
To: nanog at nanog.org
Subject: RE: IPv6 version of www.qwest.com/www.centurylink.com has been down
for 10 days

AAAA and IPv6 access to www.centurylink.com were restored around 11:30 am
U.S. Central.

Frank

-----Original Message-----
From: Frank Bulk [mailto:frnkblk at iname.com] 
Sent: Wednesday, November 30, 2011 6:59 AM
To: 'nanog at nanog.org'
Subject: RE: IPv6 version of www.qwest.com/www.centurylink.com has been down
for 10 days

Well, sometime yesterday www.centurylink.com removed it AAAA record(s).

www.qwest.com still has them.

Frank

-----Original Message-----
From: Frank Bulk [mailto:frnkblk at iname.com] 
Sent: Monday, October 24, 2011 1:47 PM
To: 'nanog at nanog.org'
Subject: RE: IPv6 version of www.qwest.com/www.centurylink.com has been down
for 10 days

Good news: access to the v6 version of www.qwest.com came up at 12:30 pm
today -- it redirects to www.centurylink.com, but at least it's working.

Only www.savvis.com remains in my list of service provider websites that
have non-working IPv6.

Frank

-----Original Message-----
From: Frank Bulk [mailto:frnkblk at iname.com] 
Sent: Thursday, August 18, 2011 12:35 AM
To: nanog at nanog.org
Subject: IPv6 version of www.qwest.com/www.centurylink.com has been down for
10 days

The IPv6 version of www.qwest.com has been down for 10 days.  Wget shows a
301 to www.centurylink.com, but that also fails.  Emails to the nocs at both
companies have gone unanswered.  Unless HE is deployed in a web browser,
this behavior leads to a bad end-user experience.

If anyone can prod either of these two companies that would be much
appreciated.

Frank

nagios:/home/fbulk# wget -6 www.qwest.com
--2011-08-18 00:32:40--  http://www.qwest.com/
Resolving www.qwest.com... 2001:428:b21:1::20
Connecting to www.qwest.com|2001:428:b21:1::20|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://www.centurylink.com/ [following]
--2011-08-18 00:32:40--  http://www.centurylink.com/
Resolving www.centurylink.com... 2001:428:b21:1::22
Connecting to www.centurylink.com|2001:428:b21:1::22|:80... failed:
Connection timed out.
Retrying.

--2011-08-18 00:33:02--  (try: 2)  http://www.centurylink.com/
Connecting to www.centurylink.com|2001:428:b21:1::22|:80... failed:
Connection timed out.
Retrying.

--2011-08-18 00:33:25--  (try: 3)  http://www.centurylink.com/
Connecting to www.centurylink.com|2001:428:b21:1::22|:80... failed:
Connection timed out.
Retrying.

--2011-08-18 00:33:49--  (try: 4)  http://www.centurylink.com/
Connecting to www.centurylink.com|2001:428:b21:1::22|:80... failed:
Connection timed out.
Retrying.

Etc...