[outages] Can anyone else confirm slow web page loads of ipv6.comcast.com

[Owen DeLong]

>From HE takes approximately 60-120 seconds for each connection to ipv6.comcast.com
to start loading data. Data loads at normal speed thereafter.

However, this affects each element and each redirect. There are about 4 redirects between
http://ipv6.comcast.com and actually getting data back and about 20 elements that comprise
the page once you get there, so, it takes a LONG time to get to the point of seeing anything
on the page.

Does not appear to be related to IPv6 transit times or connectivity:

[owen-delongs-macbook-pro:~] owen% ping6 ipv6.comcast.com
PING6(56=40+8+8 bytes) 2001:470::a9:225:4bff:feb9:2be --> 2001:558:1002:5:68:87:64:59
16 bytes from 2001:558:1002:5:68:87:64:59, icmp_seq=0 hlim=51 time=88.698 ms
16 bytes from 2001:558:1002:5:68:87:64:59, icmp_seq=1 hlim=51 time=92.542 ms
16 bytes from 2001:558:1002:5:68:87:64:59, icmp_seq=2 hlim=51 time=92.622 ms
^C
--- ipv6.comcast.com ping6 statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 88.698/91.287/92.622/1.831 ms

[owen-delongs-macbook-pro:~] owen% host ipv6.comcast.com
ipv6.comcast.com has address 68.87.64.59
ipv6.comcast.com has address 69.252.76.96
ipv6.comcast.com has IPv6 address 2001:558:1002:5:68:87:64:59
ipv6.comcast.com has IPv6 address 2001:558:1004:9:69:252:76:96

Though, interestingly, the published IPv4 A records are not responding to
ping:

[owen-delongs-macbook-pro:~] owen% host ipv6.comcast.com
ipv6.comcast.com has address 68.87.64.59
ipv6.comcast.com has address 69.252.76.96
ipv6.comcast.com has IPv6 address 2001:558:1002:5:68:87:64:59
ipv6.comcast.com has IPv6 address 2001:558:1004:9:69:252:76:96
[owen-delongs-macbook-pro:~] owen% ping ipv6.comcast.com
PING ipv6.comcast.com (68.87.64.59): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
^C
--- ipv6.comcast.com ping statistics ---
7 packets transmitted, 0 packets received, 100.0% packet loss
[owen-delongs-macbook-pro:~] owen% ping 69.252.76.96
PING 69.252.76.96 (69.252.76.96): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
^C
--- 69.252.76.96 ping statistics ---
5 packets transmitted, 0 packets received, 100.0% packet loss


Owen

On Mar 16, 2011, at 7:04 PM, Frank Bulk wrote:

> I’ve been in contact with an internal Comcast contact, but it would be
> helpful if others could confirm or deny that web page loads of
> ipv6.comcast.com are slow (yes, you'll need IPv6 access to test -- and yes,
> I have native, non-tunneled access).  I’ve measured load times of 1.5 to 2.5
> minutes.  There’s two AAAA records, so you many need to use wget to be aware
> of which one you're hitting.
> 
> The issue started around 3:10 pm Central.  The other 10 IPv6 sites I monitor
> aren't having issues.
> 
> =========================================
> nagios:# wget ipv6.comcast.com
> --2011-03-16 16:57:02--  http://ipv6.comcast.com/
> Resolving ipv6.comcast.com... 2001:558:1004:9:69:252:76:96,
> 2001:558:1002:5:68:87:64:59, 69.252.76.96, ...
> Connecting to ipv6.comcast.com|2001:558:1004:9:69:252:76:96|:80...
> connected.
> HTTP request sent, awaiting response... 301 Moved Permanently
> Location: http://ipv6.comcast.com/default.cspx [following]
> --2011-03-16 16:57:34--  http://ipv6.comcast.com/default.cspx
> Connecting to ipv6.comcast.com|2001:558:1004:9:69:252:76:96|:80...
> connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 32377 (32K) [text/html]
> Saving to: âindex.htmlâ
> 
> 100%[=======================================================================
> ==================================>] 32,377      26.0K/s   in 1.2s
> 
> 2011-03-16 16:59:35 (26.0 KB/s) - âindex.htmlâ
> 
> nagios:#
> =========================================
> 
> =========================================
> nagios:# wget ipv6.comcast.com
> --2011-03-16 17:03:22--  http://ipv6.comcast.com/
> Resolving ipv6.comcast.com... 2001:558:1002:5:68:87:64:59,
> 2001:558:1004:9:69:252:76:96, 69.252.76.96, ...
> Connecting to ipv6.comcast.com|2001:558:1002:5:68:87:64:59|:80... connected.
> HTTP request sent, awaiting response... 301 Moved Permanently
> Location: http://ipv6.comcast.com/default.cspx [following]
> --2011-03-16 17:05:05--  http://ipv6.comcast.com/default.cspx
> Connecting to ipv6.comcast.com|2001:558:1002:5:68:87:64:59|:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 32377 (32K) [text/html]
> Saving to: âindex.html.1â
> 
> 100%[=======================================================================
> ==================================>] 32,377      69.5K/s   in 0.5s
> 
> 2011-03-16 17:05:08 (69.5 KB/s) - âindex.html.1â
> 
> nagios:#
> =========================================
> 
> 
> _______________________________________________
> Outages mailing list
> Outages at outages.org
> https://puck.nether.net/mailman/listinfo/outages