3 ms·
Click on the link to read about this: 403 ERROR The request could not be satisfied. Request blocked. We can't connect to the server for this app
by ColinWright 9mo ago
Click on the link to read about this:
403 ERROR
The request could not be satisfied.
Request blocked. We can't connect to the server for this app
or website at this time. There might be too much traffic or
a configuration error. Try again later, or contact the app
or website owner.
If you provide content to customers through CloudFront, you
can find steps to troubleshoot and help prevent this error by
reviewing the CloudFront documentation.
Generated by cloudfront (CloudFront)
Request ID: IFiQvbhPlrP5MaRdM5km5yAdFAEmvC_IUx2LA899aXly11zm3wAoKg==
Is it the HN "Hug of Death" ?
- jsheard 9mo agoI doubt HN could knock over an Amazon site. They're probably geoblocking regions where that service never operated.
- swiftcoder 9mo ago> I doubt HN could knock over an Amazon site Not every amazon site is cloud-scale. Niche product like this might be running bare metal under someone's desk
- ErroneousBosh 9mo agoNo, apparently eu-west-1 went castors up earlier. I wouldn't be surprised if there was something related to this error. The site came back around eu-west-1 which, while correlation isn't causation, it does look meaningfully in causation's direction and wiggle an eyebrow suggestively.
- tecleandor 9mo agoSame right now from Spain. I guess it could be a geoblock, although I expected something more from Amazon