zlacker

> Little known fact: HN is also available through Cloudflare. Unlike CF, AWS does not support TLS1.3. This is not working while HN uses the AWS IP.

What does that mean? How do you access HN through CloudFlare and what do you mean by AWS not supporting TLS1.3? You can certainly run any https server on EC2, including one that supports TLS1.3.

>>olalon+(OP)
I too have no idea what OP means by saying it's "available through Cloudflare"

  $ dig +noall +answer A news.ycombinator.com
  news.ycombinator.com. 0 IN A 50.112.136.166
  
  $ nslookup 50.112.136.166
  166.136.112.50.in-addr.arpa name = ec2-50-112-136-166.us-west-2.compute.amazonaws.com.

>>olalon+(OP)
> > Little known fact: HN is also available through Cloudflare. ...

> What does that mean? How do you access HN through CloudFlare ...

As written, it seems to suggest HN is in the Cloudflare cache. But, I don't think there's a way to access the cached version if a site's not down. I wasn't around during today's outage, so I can't speak to whether a generic Cloudflare cached version of HN was available during the downtime.

>>olalon+(OP)

   drill news.ycombinator.com @108.162.192.195

Those are CF IP addresses. Before HN switched from M5 to AWS, CF was an alternative way to access HN.

   echo|openssl s_client -connect 50.112.136.166:443 -tls1_3