toejam316:

sorceror:

 

 

 

except it's not, because if it was an IPv6 implementation issue all traffic would be affected, not just IPv6 traffic going via AKL-IX. 

 

 

 

how does that saying go, everything looks like a nail if all you have is a hammer.

 

I feel like you're missing the bit where the error has been proven into the IPv6 implementation of 2Degrees and out of my local network, making it an issue outside the scope of what I can resolve.
As 2degrees aren't paying me to resolve the issue and I have a work around.
If you can make changes to 2degrees and their partners network, feel free to continue troubleshooting and implement a solution.

not having a go at you, my issue is with the lazy response of turning IPv6 off with little to no troubleshooting, which invariably leads to incorrect assumptions and mitigations.