Unable to load image

Our clone site moved from M5 to AWS :!marsoyhype:

https://news.ycombinator.com/item?id=32030400

After many years of remaining static, HN's IP address changed.^1

Old: 209.216.230.240

New: 50.112.136.166

Perhaps this is temporary.

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

  1. Years ago someone on HN tried to argue with me that IP addresses will never stay the same for very long. I used HN as an example of an address that does not change very often. I have been waiting for years. I collect historical DNS data. When I remind HN readers that most site addresses are more static than dynamic, I am basing that statement on evidence i have collected.

  2. Across the board, so to speak. Every CF-hosted site I have encountered supports TLS1.3. Not true for AWS. Many (most?^3) only offer TLS1.2.

  3. Perhaps a survey is in order.

> dang: It's temporary.

> > Maybe you should pin this comment? I almost lost it in the shuffle.

> > > dang: I thought about it, but it's fun to leave rewards for people who read entire threads. :marseytroublemaker:

https://news.ycombinator.com/item?id=32031136

9
Jump in the discussion.

No email address required.

I remember because just two days before we had fully switched over to AWS and hadn’t done multi-region yet. We got our first downtime in 10 years and there was nothing we could do, unlike when we had the servers in a colo. We were at the mercy of Amazon. After that, we moved everything back to real physical servers.

Why would you actually want to maintain hardware though. Huge hassle, and I doubt they are running important workloads anyway.

Jump in the discussion.

No email address required.

Link copied to clipboard
Action successful!
Error, please refresh the page and try again.