[outages] [EXTERNAL] IPv4 Issues Accessing apnews.com

[Jim Harton]

Getting the same as OP -- 404 from Google landing page from AS22773

On Sat, Feb 27, 2021 at 9:10 PM Ryan Kearney via Outages <
outages at outages.org> wrote:

> Most certainly not just them. It also produces the same Google 404 page
> for me no matter how many times I refresh. Happens across different
> browsers too.
>
> Coming from AS22909
>
>
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Saturday, February 27th, 2021 at 8:51 PM, Chapman, Brad
> \(NBCUniversal\) via Outages <outages at outages.org> wrote:
>
> downforeveryoneorjustme
>
> nope, just you.  also, a Google 404 error indicates that you were trying
> to load the story through AMP.  perhaps in the brief moments between the
> story being published and you loading the side, Google did not have a
> chance to load the AMP accelerated version of that page.
>
> —Sent from my iPhone
>
> On Feb 27, 2021, at 6:45 PM, Erik Ogren via Outages <outages at outages.org>
> wrote:
>
> 
>
> Is anybody else experiencing reachability issues getting to
> https://apnews.com
> <https://urldefense.com/v3/__https://apnews.com__;!!PIZeeW5wscynRQ!5BieAWWkSbzDhC8YhpOiy_BzNlOTel57Td9urwf2GUVVlkRamNeE0U0dZRbsJjBwZg$>
> over IPv4? If IPv6 is used it seems to work fine but if IPv4 is used
> occasionally we’re confronted by a custom Google 404 error page. Sometimes
> you can get the 404, refresh, get the expected/full APNews site, refresh
> again, then get another 404. APNews seems to be protected/hosted through
> Google’s Project Shield. We’re in the Mountain West region
> (Wyoming/Montana) and I have validated this using our own network (AS4474),
> Charter (Formerly Bresnan)/AS33588, AT&T cellular/AS20057, and
> CenturyLink/AS209 across multiple browsers and multiple devices with the
> same results. All devices across the various networks are resolving “
> apnews.com” to 34.96.67.30. We have a couple different connections to
> Google ASN15169 in different cities which I’ve tried to shift the egress
> traffic from our network towards 34.96.0.0/17 between the various Google
> datacenters we’re connected to but it didn’t seem to help. I did raise a
> “Reachability” ticket on our Google ISP portal for their NOC to
> investigate, was just curious how widespread this might be since none of
> the “usual” indicators like downdetector seem to be indicating a widespread
> issue at least not that I could see. Google Cloud’s status page also
> doesn’t seem to indicate any active issues, granted Project Shield is not
> explicitly mentioned there.
>
>
>
> Thank you,
>
>
>
> Erik Ogren
>
> Network Administrator (TCT AS4474)
> _______________________________________________
> Outages mailing list
> Outages at outages.org
>
> https://urldefense.com/v3/__https://puck.nether.net/mailman/listinfo/outages__;!!PIZeeW5wscynRQ!5BieAWWkSbzDhC8YhpOiy_BzNlOTel57Td9urwf2GUVVlkRamNeE0U0dZRYdzp9I5A$
>
> _______________________________________________
> Outages mailing list
> Outages at outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20210227/0e013068/attachment.htm>