www.java.com

[#1]

Quote from: jelv

What IP address is that using?

See Reply #20

[#2]

It's doing it again now. Two traceroutes (20 secs apart):

Quote

Andrew$ traceroute6 2a02:26f0:5a:282::1ba3 traceroute6 to 2a02:26f0:5a:282::1ba3 (2a02:26f0:5a:282::1ba3) from 2a02:16c8:2000:1100:xxxx:xxxx:xxxx:xxxx, 64 hops max, 12 byte packets 1  2a02:16c8:2000:1100:5246:xxxx:xxxx:xxxx  0.382 ms  0.296 ms  0.283 ms 2  2a02:16c8:0:1::12  73.493 ms  65.786 ms  70.083 ms 3  2a02:16c8:1:2::19  5.223 ms  4.737 ms  4.915 ms 4  2a02:16c8::d  32.959 ms  4.936 ms  11.068 ms 5  2a02:16c8:1:2::8  4.793 ms  5.182 ms  4.750 ms 6  lonap.he.net  7.796 ms  4.844 ms  4.955 ms 7  10ge3-1.core1.lon2.he.net  4.707 ms  14.238 ms  4.874 ms 8  ge-2-1-0-zpr1.lnt.cw.net  5.341 ms  19.345 ms  27.926 ms 9  so-0-1-0-r1-ipv6.de.cw.net  6.277 ms  5.508 ms  5.584 ms 10  akamai-gw2.lns.cw.net  5.622 ms  5.640 ms  5.518 ms 11  * * *

Quote

Andrew$ traceroute6 2a02:26f0:5a:282::1ba3 traceroute6 to 2a02:26f0:5a:282::1ba3 (2a02:26f0:5a:282::1ba3) from 2a02:16c8:2000:1100:xxxx:xxxx:xxxx:xxxx, 64 hops max, 12 byte packets 1  2a02:16c8:2000:1100:5246:xxxx:xxxx:xxxx  0.377 ms  0.302 ms  0.291 ms 2  2a02:16c8:0:1::12  23.638 ms  11.484 ms  5.052 ms 3  2a02:16c8:1:2::19  4.956 ms  4.796 ms  4.646 ms 4  2a02:16c8::d  4.814 ms  4.726 ms  4.905 ms 5  2a02:16c8:1:2::8  4.843 ms  5.595 ms  4.776 ms 6  * * * 7  * * *

[#3]

From another topic:

Quote from: paulmh5

I've made some changes to stop traffic going over the Akamai PNI links.  Hopefully this will be a bit more stable while they have a look at what's going on.

I wonder if this will affect the www.java.com issues?

[#4]

Yeah, it's fixed it - the site should load fine now in v6.

[#5]

Yep, that's what I'm finding.

[#6]

confirmed fixed here.

[#7]

I ended up turning fast fallback back on its an eye opener with it off how many hostnames have dodgy ipv6 configuration.

[#8]

It's dead again over IPv6. Probably because of http://community.plus.net/forum/index.php/topic,126633.msg1112479.html#msg1112479