Is anyone able to reach treasurydirect.gov over IPv6? Unable to do so over Verizon Fios, and I’m not sure if it is a routing issue or an issue on Treasury’s end.
You can utilize online (i.e. https://dnstools.ws/) or ISP looking glass tools to check for routing issues.
It's up for us via AS12129
It appears that holow29 <email@example.com> said:
Is anyone able to reach treasurydirect.gov over IPv6? Unable to do so over
Verizon Fios, and I'm not sure if it is a routing issue or an issue on
Works fine via a HE tunnel.
Reachable from AS4927 in California.
Verizon has IPv6?
Given that traceroute can reach Zayo and Zayo appears to have route to Treasury’s AS13506, is it reasonable to assume this is on Treasury’s end, potentially blocking traffic from VZ’s AS701?
@John Lightfoot: Yes, they rolled out largely throughout last year.
From Spectrum, I'm able to hit port 80, but the redirect to 443 fails.
% curl -6IL treasurydirect.gov
HTTP/1.0 302 Moved Temporarily
curl: (35) Recv failure: Connection reset by peer
Smells like broken PMTUD to me.
Once upon a time, Jay Hennigan <firstname.lastname@example.org> said: