Part of the Consumer Reports web content delivery network (CDN) service CloudFront can’t get to the Consumer Reports website.
Caching services are used to cache web content from the website, to reduce server load, and to blunt denials of service.
Requests from the Consumer Reports CDN to the Consumer Reports web server(s) are getting HTTP 403 “forbidden” errors.
CDNs usually have lots of servers involved, often geographically distributed, and which means a problem with a subset of the caching servers can be hard to replicate as different accesses can reach different (working) caching servers.
There were some denials-of-service running on the ‘net earlier today too (I’m aware of several websites that got wobbly, including at least one Amazon zone), and it wouldn’t surprise me to see one of the caching services or potentially the Consumer Reports web servers a little wobbly, too.
If this were a block at the CDN (it’s not) then changing DNS or restarting the router (to get a different IP address) or such might be useful. But this is an internal error within the Consumer Reports website configuration. (that much is obvious from the error message shown.) But you’re not getting the HTTP 403 “forbidden” error here (from the CDN), it’s the CDN that’s getting the 403 from the Consumer Reports web server “behind” the CDN.
Which means it’s a problem with the Consumer Reports website.
Not with your browser.
By all appearances, the Consumer Reports web services are malfunctioning.
Either Consumer Reports will sort it out, or the CDN will sort it out. Somebody hopefully notices the CDN getting 403 errors. Not much anybody out here can really do about this, absent a different path to report this into Consumer Reports, or maybe finding a different path into a different (and working) part of the CDN.