3 ms·
Tell HN: HN's IPv6 address is down
HN on IPv4 works fine (209.216.230.207) but appears down on IPv6 (2606:7100:1:67::26), checked from multiple points. None of the HN status monitors appear to catch this. “Happy eyeballs” keeps everything working fine on a dual IPv4/IPv6 network, but in my case I am visiting via a proxy that apparently prefers IPv6, switching over only when it hits a timeout. (It’s a testament to the gradual IPv6 rollout that this works 99.9% of the time!).
- Bender 1mo agoBest to email them in such cases. [1] hn@ycombinator.com [1] - https://www.ssllabs.com/ssltest/analyze.html?d=news.ycombinator.com https://www.ssllabs.com/ssltest/analyze.html?d=news.ycombina...
- nneonneo 1mo agoThanks, good call. I posted this partly hoping that one of those status sites could add IPv6 testing as a feature, but that’s probably asking too much :)
- miyuru 1mo agoI am working on a IPv6 only monitoring tool for the past 2 years. https://v6monitor.com/domains/history/79/news-ycombinator-com https://v6monitor.com/domains/history/79/news-ycombinator-co... Since I am working on other projects, its not fully what I want it to be ATM.
- dang 1mo agoYes, sorry. There is a trickle of IPv6 traffic in the logs, but nothing like what it should be. I've opened a ticket with our hosting provider. Edit: they made a change and it should be working now. Can you try again and let us know?
- timpera 1mo agoHi! Thanks for looking into this. I have also been having this issue for the last two days. It looks like it might still be broken: https://news.ycombinator.com/item?id=49528768 https://news.ycombinator.com/item?id=49528768
- pfa87 1mo agoIf you want to confirm the client path has working v6 (separate from HN's AAAA), curl -6sS https://ip.pfa87.cc https://ip.pfa87.cc vs curl -4sS https://ip.pfa87.cc https://ip.pfa87.cc is a dual-stack plaintext echo; nothing stored.