Open warthog9 opened 2 years ago
Thank you @warthog9, I've submitted this information to Fastly Support.
Just noting I'm still seeing the issue, don't know if you've heard anything from Fastly Support on it
@ewdurbin just as a note this is still ongoing, is there any additional data I can get to pypi or for Fastly that would help?
My Platform
I'm seeing this on 2001:470:b:312::/64 subnet, which happens to be an HE Tunnel Broker network. This specific /64 has been under my control since 2014. Issue is seen regardless of client, browser, curl, etc attempting to connect via the subnet to pypi.org results in a connection reset. Using a different v6 subnet (in my case using one out of AS53758), or via normal IPv4, works fine and as expected.
This has been going on for a couple of weeks now, so this isn't something transient, and given it's affecting my HE Tunnel Broker subnet my suspicion is that it's affecting the entire HE Tunnel Broker IPv6 subnet, and this is not explicitly targeting me.
Fastly Debug
From an affected machine, HOWEVER fastly-debug.com does not provide any IPv6 addresses
So this isn't using the same IP as where I'm having problems at (this seems like a bug on Fastly's part)
DNS Resolution
Traceroutes / IPv4
Traceroutes / IPv6 (If available)
HTTPS Requests / IPv4
HTTPS Requests / IPv6 (If available)
TLS Debug / IPv4
TLS Debug / IPv6 (If available)
Code of Conduct