Can anyone else confirm slow web page loads of ipv6.comcast.com
Ive 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). Ive measured load times of 1.5 to 2.5 minutes. Theres 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:# =========================================
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@outages.org https://puck.nether.net/mailman/listinfo/outages
Confirmed from Hurricane Electric Fremont Location: http://ipv6.comcast.com/default.cspx [following] --2011-03-16 19:44:04-- 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... [sleeping] -- Jason Fesler, email/jabber <jfesler@gigo.com> resume: http://jfesler.com "Give a man fire, and he'll be warm for a day; set a man on fire, and he'll be warm for the rest of his life." On Wed, 16 Mar 2011, 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@outages.org https://puck.nether.net/mailman/listinfo/outages
Confirmed slow loads via native IPv6 at Layer42.net. -G graham@manage01:~$ traceroute6 ipv6.comcast.com traceroute to ipv6.comcast.com (2001:558:1004:9:69:252:76:96) from 2001:1868:a001:1::11, 30 hops max, 24 byte packets [elided] 3 2001:1868::288 (2001:1868::288) 0.585 ms 0.781 ms 0.64 ms 4 2001:1868::298 (2001:1868::298) 1.018 ms 7.815 ms 1.677 ms 5 2001:1868::259 (2001:1868::259) 37.158 ms 21.063 ms 3.568 ms 6 te-8-1.car2.SanJose1.Level3.net (2001:1900:2100::12d) 200.538 ms 2.323 ms 79.244 ms 7 vl-80.edge1.SanJose1.Level3.net (2001:1900:1a:7::8) 1.306 ms 1.317 ms 1.29 ms 8 COMCAST-IP.edge1.SanJose1.Level3.net (2001:1900:4:2::192) 13.88 ms 2.416 ms 1.839 ms 9 pos-0-14-0-0-cr01.denver.co.ibone.comcast.net (2001:558:0:f560::1) 38.14 ms 37.968 ms 37.78 ms 10 2001:558:0:f6c2::2 (2001:558:0:f6c2::2) 38.681 ms 38.478 ms 38.464 ms 11 2001:558:d0:12::1 (2001:558:d0:12::1) 39.216 ms 39.426 ms 39.023 ms 12 2001:558:d0:5::1 (2001:558:d0:5::1) 39.363 ms 39.079 ms 39.045 ms 13 2001:558:1004:9:69:252:76:96 (2001:558:1004:9:69:252:76:96) 39.101 ms 39.322 ms 39.099 ms graham@manage01:~$ wget http://ipv6.comcast.com --2011-03-16 20:15:49-- http://ipv6.comcast.com/ Resolving ipv6.comcast.com... 2001:558:1004:9:69:252:76:96, 2001:558:1002:5:68:87:64:59, 68.87.64.59, ... Connecting to ipv6.comcast.com|2001:558:1004:9:69:252:76:96|:80... connected. HTTP request sent, awaiting response... [waited at least 60 seconds] ^C graham@manage01:~$
Thanks, everyone. Jason B's last e-mail to me (sent after I sent a note to outages) confirmed that it was not a "just me" issue and that Comcast staff are actively working on it. Frank -----Original Message----- From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Frank Bulk Sent: Wednesday, March 16, 2011 9:05 PM To: outages@outages.org Subject: [outages] Can anyone else confirm slow web page loads of ipv6.comcast.com Ive 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). Ive measured load times of 1.5 to 2.5 minutes. Theres 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@outages.org https://puck.nether.net/mailman/listinfo/outages
participants (4)
-
Frank Bulk -
Graham Freeman -
Jason Fesler -
Owen DeLong