Comcast XFINITY → [IPv6] IPv6 Issues with Google Sites?

Is anyone else seeing issues with IPv6 pings to google sites? Starting yesterday I noticed ~ 50 to 75% of the time I was unable to ping google sites ... google.com, gmail.com youtube.com with IPv6. ~ 25% of the time it would work fine though. The sites appear to work fine in my browsers and IPv4 ping are also great with no packet loss.

Checked today and now all packets are failing to googles sites using IPv6. All my other IPv6 pings to other sites appear to be fine, and IPv4 to google stuff is still OK. I don't think it's my modem and router as I checked with a neighbor who is running a Comcast gateway and he's seeing the same thing. I'm just outside of Philly in the northeast US.

Currently not a major issue as everything seems to be working but it's odd if they are now blocking ping packets. I lost IPv6 to apple sites a few times a while back, and that resolved itself on its' own. Apple said it was most likely an issue on Comcast's side.

Just checking to see if it may only be isolated to my area?

Seeing it here in Chicago, too. Almost looks like it goes to Google then bounced back to Comcast?

Microsoft Windows [Version 10.0.19044.1889]
(c) Microsoft Corporation. All rights reserved.
 
c:\downloads>ping google.com
 
Pinging google.com [2607:f8b0:4009:803::200e] with 32 bytes of data:
Request timed out.
Request timed out.
 
Ping statistics for 2607:f8b0:4009:803::200e:
    Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),
Control-C
^C
c:\downloads>tracert google.com
 
Tracing route to google.com [2607:f8b0:4009:803::200e]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  2601:249:1980:7e50::1
  2     7 ms     8 ms     8 ms  2001:558:100f:da::2
  3    10 ms    10 ms     8 ms  2001:558:322:303::1
  4     9 ms     8 ms     8 ms  2001:558:300:211d::2
  5     9 ms     8 ms     8 ms  be-52-sur03.wchicago.il.chicago.comcast.net [2001:558:300:211c::2]
  6     *        *        *     Request timed out.
  7     *        *       13 ms  be-32231-cs03.350ecermak.il.ibone.comcast.net [2001:558:3:20e::1]
  8     *       11 ms     *     be-2312-pe12.350ecermak.il.ibone.comcast.net [2001:558:3:76::2]
  9    12 ms    12 ms    12 ms  2001:559::1322
 10    13 ms    12 ms    12 ms  2607:f8b0:8313::1
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13    15 ms    14 ms    13 ms  2001:4860::c:4002:a0bf
 14    12 ms    15 ms    14 ms  2001:4860::1:4000:d31c
 15     *        *        *     Request timed out.
 16    12 ms    13 ms    12 ms  2001:4860:0:1::63b7
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20  ^C
c:\downloads>
 

Oddly only affecting pings. Going to the web site shows an IPv6 according to FlagFox:

Yep ... that's what I'm seeing. Thanks for verifying! I agree that it only seems to affect pings. Probably just a coincidence, but it did appear to start almost the same time Comcast ran into e-mail issues a couple days ago. I can't see how the two would be related though

Beefing up firewall/security rules.

I don't think this issue is specific to Comcast. I'm seeing the same thing in southeast Michigan on AT&T Internet.

I am getting the same thing on FIOS. Getting a different IPv6 address for google though. Probably either that I am in a different geographic location or I am using Google DNS.

Tracing route to google.com [2607:f8b0:4006:80f::200e]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 2600:4040:302a:8800::1
2 5 ms 3 ms 3 ms 2600:4040:3020::1
3 6 ms 6 ms 7 ms 2600:4000:1:130::5e
4 * * * Request timed out.
5 * * * Request timed out.
6 16 ms 15 ms 14 ms 2600:802::81
7 14 ms 15 ms 15 ms 2001:4860:1:1::8e6
8 * * * Request timed out.
9 * 16 ms 14 ms 2001:4860:0:1::2f6e
10 13 ms * 14 ms 2001:4860:0:1126::14
11 * * 13 ms 2001:4860::c:4001:29de
12 * * * Request timed out.
13 14 ms 15 ms 15 ms 2001:4860:0:1::574f
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 ^C

I also posted on the Comcast forums.
»forums.xfinity.com/conve ··· e604fa2d

Who is 2001:4860?

Apparently it is Google: »whois.arin.net/rest/net/ ··· :1::574f

Maybe Google decided to turn off the ping service for IPv6.

What you see from a traceroute isn't 'exactly' the same as a ping. It is a different icmp response noting the allowed number of hops for a packet expired.

I saw the same thing at a smallish FTTH ISP in the rural midwest while working on [slowly] getting ready to roll out IPv6, and originally attributed it to having screwed something up in that network, until I tested at home on Comcast and saw the same thing you are all seeing. So I'm still able to replicate the problem both inside and outside Comcast's network as of today. (But to the other point, ipv6.google.com still loads in the browser, so maybe they are no longer responding to ping, but HTTP is working)

Appears to be working for me again as of this morning.

Same here on AT&T.