Forum availability via IPv6

fewi · Mon Aug 01, 2011 8:07 am

So I'm using IPv6 at home. Great. Unfortunately that makes this place kind of unavailable a lot of the time on platforms that prefer IPv6.

Right now, for example:

sh-3.2$ dig forum.mikrotik.com | grep IN
;forum.mikrotik.com.		IN	A
forum.mikrotik.com.	        2184   	IN	A	159.148.147.201
sh-3.2$ dig AAAA forum.mikrotik.com | grep AAAA
; <<>> DiG 9.7.3 <<>> AAAA forum.mikrotik.com
;forum.mikrotik.com.		IN	AAAA
forum.mikrotik.com. 	7028 	IN	AAAA	2a02:610:7501:1000::201
sh-3.2$ ping 159.148.147.201
PING 159.148.147.201 (159.148.147.201): 56 data bytes
64 bytes from 159.148.147.201: icmp_seq=0 ttl=54 time=465.923 ms
64 bytes from 159.148.147.201: icmp_seq=1 ttl=54 time=385.715 ms
64 bytes from 159.148.147.201: icmp_seq=2 ttl=54 time=613.587 ms
64 bytes from 159.148.147.201: icmp_seq=3 ttl=54 time=533.988 ms
^C
--- 159.148.147.201 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 385.715/499.803/613.587/84.082 ms
sh-3.2$ ping6 2a02:610:7501:1000::201
PING6(56=40+8+8 bytes) 2001:470:f037:1:69d5:4e7e:8b9f:95aa --> 2a02:610:7501:1000::201
^C
--- 2a02:610:7501:1000::201 ping6 statistics ---
11 packets transmitted, 0 packets received, 100.0% packet loss

sh-3.2$ ping6 ipv6.google.com
PING6(56=40+8+8 bytes) 2001:470:f037:1:69d5:4e7e:8b9f:95aa --> 2001:4860:4001:803::1011
16 bytes from 2001:4860:4001:803::1011, icmp_seq=0 hlim=56 time=100.495 ms
16 bytes from 2001:4860:4001:803::1011, icmp_seq=1 hlim=56 time=52.778 ms
16 bytes from 2001:4860:4001:803::1011, icmp_seq=2 hlim=56 time=28.520 ms
16 bytes from 2001:4860:4001:803::1011, icmp_seq=3 hlim=56 time=28.183 ms
16 bytes from 2001:4860:4001:803::1011, icmp_seq=4 hlim=56 time=29.068 ms
^C
--- ipv6.l.google.com ping6 statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 28.183/47.809/100.495/27.961 ms

sh-3.2$ telnet -6 2a02:610:7501:1000::201 80
Trying 2a02:610:7501:1000::201...
telnet: connect to address 2a02:610:7501:1000::201: Operation timed out
telnet: Unable to connect to remote host
sh-3.2$

IPv4 latency is atrocious, IPv6 is just unavailable. Some platforms don't just ignore IPv6 when it's unavailable, so this resource is seen as unavailable when only IPv4 is up.

Mon Aug 01, 2011 8:08 am

what about a traceroute? i have seen that some IPv6 providers can't reach us, some can. Can you try from a different IPv6 provider (I assume you use HE?)

fewi · Mon Aug 01, 2011 8:11 am

I am using HE. I can't try using another provider, I'm afraid.
Here the traceroute - you're right, it does die within HE. Unfortunately for your North American audience that's going to be most of the traffic. Most of us can't get native IPv6 at home since US providers are way, way, way behind the curve on IPv6 while many of your users aren't.
Any chance of getting your IPv6 uplink to talk to HE about what's going on? The hop names indicate I'm making it to Germany, I guess?

sh-3.2$ traceroute6 forum.mikrotik.com
traceroute6 to forum.mikrotik.com (2a02:610:7501:1000::201) from 2001:470:f037:1:69d5:4e7e:8b9f:95aa, 64 hops max, 12 byte packets
 1  2001:470:f037:1::1  3902.205 ms  1.085 ms  0.913 ms
 2  [retracted].tunnel.tserv15.lax1.ipv6.he.net  21.600 ms  21.214 ms  19.362 ms
 3  gige-g4-6.core1.lax1.he.net  18.681 ms  33.925 ms  23.623 ms
 4  10gigabitethernet4-3.core1.nyc4.he.net  80.134 ms  80.096 ms  78.218 ms
 5  10gigabitethernet3-3.core1.lon1.he.net  147.565 ms  154.337 ms  146.257 ms
 6  10gigabitethernet4-2.core1.fra1.he.net  170.106 ms  158.448 ms  157.756 ms
 7  * * *
 8  * * *
 9  * *^C
sh-3.2$

lavv17 · Mon Aug 01, 2011 10:02 am

 3  2001:5a0:2800::e (2001:5a0:2800::e)  77.652 ms  77.582 ms  77.526 ms
 4  ffm-b10-link.telia.net (2001:2000:3080:30c::1)  79.093 ms  79.060 ms  77.255 ms
 5  s-b3-v6.telia.net (2001:2000:3018:9::1)  100.877 ms  99.454 ms  106.812 ms
 6  * * *
 7  * * *

It does not work here too.

Mon Aug 01, 2011 11:35 am

Did you try to contact your provider? It doesn't work from Fremont but it works from Frankfurt (tool http://lg.he.net/):

core1.fmt1.he.net> traceroute ipv6 2a02:610:7501:1000::2

Tracing the route to IPv6 node 2a02:610:7501:1000::2 from 1 to 30 hops

  1     9 ms    2 ms   33 ms 2001:470:0:2f::2
  2    34 ms   46 ms   27 ms 2001:470:0:1b4::2
  3    52 ms   51 ms   51 ms 2001:470:0:1af::1
  4    71 ms   71 ms   71 ms 2001:470:0:1c6::1
  5   149 ms  150 ms  149 ms 2001:470:0:128::2
  6   168 ms  157 ms  149 ms 2001:470:0:1d2::2
  7    *       *       *     ?
  8    *       *       *     ?
  9    *       *       *     ?
 10    *       *       *     ?
IP: Errno(8) Trace Route Failed, no response from target node.
# Entry cached for another 30 seconds.

core1.phx1.he.net> traceroute ipv6 2a02:610:7501:1000::2
Invalid input -> numeric# Entry cached for another 59 seconds.

core1.fra1.he.net> traceroute ipv6 2a02:610:7501:1000::2

Tracing the route to IPv6 node 2a02:610:7501:1000::2 from 1 to 30 hops

  1    35 ms   41 ms   40 ms 2001:7f8::a7e3:0:1
  2    54 ms   49 ms   56 ms 2a02:610:ffff:1800::2
  3    43 ms   49 ms   50 ms 2a02:610:ffff:1003::2
  4    41 ms   50 ms   49 ms 2a02:610:7500::1
  5    57 ms   50 ms   49 ms 2a02:610:7500:8::2
  6    50 ms   49 ms   50 ms 2a02:610:7500:9::2
  7    55 ms   52 ms   48 ms 2a02:610:7501:1000::1
  8    52 ms   47 ms   46 ms 2a02:610:7501:1000::2# Entry cached for another 51 seconds.

fewi · Mon Aug 01, 2011 7:37 pm

Oh well, made a thread with HE in their forums. That's about all I can do. It's not like I pay for my tunnel so there's no real support.

http://www.tunnelbroker.net/forums/inde ... pic=1928.0

bazzer · Mon Aug 01, 2011 8:19 pm

I have no joy reaching mikrotik web or forum either on IPv6. Its been dead most of the day.

traceroute to www.mikrotik.com (2a02:610:7501:1000::2), 30 hops max, 40 byte packets using UDP
1 mr-wooter.allness.net (2001:8b0:56::1) 0.172 ms 0.127 ms 0.136 ms
2 round.window.allness.net (2001:8b0:56

:18) 0.392 ms 0.282 ms 0.282 ms
3 a.gormless.thn.aaisp.net.uk (2001:8b0:0:53:203:97ff:fe05:8000) 10.636 ms 10.811 ms 10.829 ms
4 2001:7f8:4::50e8:1 (2001:7f8:4::50e8:1) 10.837 ms 11.174 ms *
5 10gigabitethernet1-1.core1.lon1.he.net (2001:7f8:4::1b1b:1) 20.422 ms 19.157 ms 11.655 ms
6 10gigabitethernet4-2.core1.fra1.he.net (2001:470:0:1d2::2) 22.748 ms 23.664 ms 23.448 ms
7 * * *
8 * * *
9 * * *

Signius · Mon Aug 01, 2011 9:00 pm

I been unable to access www.mikrotik.com all day with my HE 6 to 4 tunnel enabled it does load eventually but it takes minutes.

sudo rltraceroute6 www.mikrotik.com
traceroute to www.mikrotik.com (2a02:610:7501:1000::2) from 2001:470:1f09:1aa8:225:22ff:fe7a:4ff1, port 33434, from port 58938, 30 hops max, 60 bytes packets
1 2001:470:1f09:1aa8::1 (2001:470:1f09:1aa8::1) 0.195 ms 0.096 ms 0.137 ms
2 2001:470:1f08:1aa8::1 (2001:470:1f08:1aa8::1) 15.855 ms 15.633 ms 15.261 ms
3 gige-g4-6.core1.lon1.he.net (2001:470:0:67::1) 15.804 ms 23.469 ms 14.352 ms
4 10gigabitethernet4-2.core1.fra1.he.net (2001:470:0:1d2::2) 33.700 ms 24.800 ms 18.058 ms
5 * * *
6 * * *
7 * * *
8 * * *

As soon as disable my 6 to 4 tunnel ipv4 works fine but i not got any issues with any other ipv6 sites.

fewi · Mon Aug 01, 2011 9:06 pm

I've emailed HE support and have a ticket open.

bazzer · Tue Aug 09, 2011 5:33 pm

I can't believe routing is still dead via IPv6 to the mikrotik.com domain. Its been over a week now.

fewi · Tue Aug 09, 2011 5:49 pm

No kidding. It's extremely annoying. As a single user of an HE tunnel there isn't much I can do, I'm not even giving anyone money. Chances would be much, much better if Mikrotik used their IPv6 uplinks to lean on whoever is broken on the chain - at least there's money changing hands there somewhere, so there's incentive.

Wed Aug 10, 2011 7:51 am

Oh well, made a thread with HE in their forums. That's about all I can do. It's not like I pay for my tunnel so there's no real support.

http://www.tunnelbroker.net/forums/inde ... pic=1928.0

maybe you should ask if the HE guy got a response (see last post in that forum)

bazzer · Wed Aug 10, 2011 10:04 am

Oh well, made a thread with HE in their forums. That's about all I can do. It's not like I pay for my tunnel so there's no real support.

http://www.tunnelbroker.net/forums/inde ... pic=1928.0
maybe you should ask if the HE guy got a response (see last post in that forum)

Or maybe you could as you are the representative here for Mikrotik considering its MIkrotik that can't be reached. I know I'd track down the problem if it were my customers not able to reach me.

Wed Aug 10, 2011 10:09 am

we are working on it, but it's interesting what HE got from the other ISP.

From experience, lots of things can't be reached with ipv6. This is not a mikrotik problem. It times out way way before it reaches anything near us.

bazzer · Wed Aug 10, 2011 10:52 am

quote: "From experience, lots of things can't be reached with ipv6."

Strangely in the 6+ years I've been using IPv6, I can't recall having many issues with sites broadcasting AAAA DNS records. The only one that sticks in my mind is mikrotik.com.
Maybe its not so much as the internet as a whole but more localised that you base your experience.

Wed Aug 10, 2011 10:54 am

Tell me why most of the ipv6 ready sites have a separate domain name for it (ipv6.google.com etc).

bazzer · Wed Aug 10, 2011 11:08 am

I always presumed it was for testing in case end users were using broken browser implementations etc. By seperating into the 2 domain records it is easy to identify issues between ipv4 and ipv6 without losing traffic to the site. That said, www.google.com has AAAA records too that work fine but I'm sure you know this.

Wed Aug 10, 2011 11:10 am

www.google.com has AAAA records too that work fine but I'm sure you know this.

no, they don't work fine, that's why they have a separate domain. because there are too many problems with ipv6 still.

like I said, we will try to get our other ISP to give us IPv6, we will see if that makes a difference. The current ISP is unable to solve the HE problem.

changeip · Wed Aug 10, 2011 6:24 pm

I have native Level3 v6 and can't get there. It's probably something to do with peering agreements between providers. : )

Email NOC@HE.NET and ask them to look into it, give them the source IP and the destination IP. I've had many times where my v6 bgp prefix was still being announced to them but many of their routers lost it / or dampened it for a week at a time.

traceroute to 2a02:610:7501:1000::2 (2a02:610:7501:1000::2), 30 hops max, 40 byte packets
1 2620

5000:cafe::1 (2620

5000:cafe::1) 0.309 ms 0.432 ms 0.420 ms
2 v6-750.ais.as19557.net (2620

5000:1::1) 13.863 ms 13.852 ms 13.841 ms
3 vlan128.car2.sandiego1.level3.net (2001:1900:2100::609) 14.882 ms 14.885 ms 14.874 ms
4 * vl-11.car1.sandiego1.level3.net (2001:1900:4:1::299) 13.733 ms 14.759 ms
5 vl-4043.car1.losangeles1.level3.net (2001:1900:4:1::295) 20.025 ms 20.015 ms 20.004 ms
6 vl-70.edge1.losangeles9.level3.net (2001:1900:12:2::d) 19.923 ms 17.208 ms 17.172 ms
7 telia-level3-10g.losangeles9.level3.net (2001:1900:4:3::b2) 18.434 ms 32.860 ms 32.917 ms
8 s-b3-v6.telia.net (2001:2000:3018:9::1) 216.218 ms 215.664 ms *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *

astounding · Thu Aug 11, 2011 3:10 am

Hurricane Electric is still announcing the IPv6 prefix in question to my network. Various public looking glass sites show that Sprint and TATA (among others) can reach MikroTik's network just fine. I just sent off an email to HE.NET asking for more information. If I hear back, I will post in this thread. As we peer with HE.NET at http://www.seattleix.net/ and they provide us IPv6 transit for this particular prefix, I hope they'll respond in a timely fashion. I would at least like to know the AS number of the HE.NET peer that's injecting the prefix onto their network.

Aaron out.

fewi · Thu Aug 11, 2011 7:52 am

Did you guys withdraw your IPv6 DNS records? I was wondering why it was loading again at home.

sh-3.2$ dig AAAA www.mikrotik.com | grep AAAA
; <<>> DiG 9.7.3 <<>> AAAA www.mikrotik.com
;www.mikrotik.com.		IN	AAAA
sh-3.2$ dig AAAA forum.mikrotik.com | grep AAAA
; <<>> DiG 9.7.3 <<>> AAAA forum.mikrotik.com
;forum.mikrotik.com.		IN	AAAA
sh-3.2$ dig AAAA ipv6.google.com | grep AAAA
; <<>> DiG 9.7.3 <<>> AAAA ipv6.google.com
;ipv6.google.com.		IN	AAAA
ipv6.l.google.com.	265	IN	AAAA	2001:4860:4001:803::1012
sh-3.2$

Thu Aug 11, 2011 2:58 pm

it's back. let us know if you hear from HE

janisk · Thu Aug 11, 2011 3:05 pm

guys you could try to do traceroute to 2a02:610:7501:1000::2 and see if this is reachable. as there are some update in global routing tables and we can reach our other IPv6 addresses.

AAAA records indeed where pulled since a lot of customers could not reach forums and our main page. So if you know the address you can check it.

edit:

AAAA records are back

fewi · Thu Aug 11, 2011 4:24 pm

$ traceroute6 2a02:610:7501:1000::2
traceroute6 to 2a02:610:7501:1000::2 (2a02:610:7501:1000::2) from 2001:470:f037:1:7131:585a:d049:436, 64 hops max, 12 byte packets
 1  2001:470:f037:1::1  1.728 ms  1.105 ms  0.995 ms
 2  fwindt-1.tunnel.tserv15.lax1.ipv6.he.net  18.036 ms  17.865 ms  18.829 ms
 3  gige-g4-6.core1.lax1.he.net  13.578 ms  14.338 ms  15.360 ms
 4  10gigabitethernet7-4.core1.fmt2.he.net  25.981 ms  23.331 ms  24.018 ms
 5  10gigabitethernet1-1.core1.sjc2.he.net  24.472 ms  23.048 ms  27.925 ms
 6  sjo-eqx-s1-link.telia.net  24.073 ms  22.355 ms  23.461 ms
 7  s-b3-v6.telia.net  191.158 ms  195.046 ms  191.288 ms
 8  internetf-ic-142059-s-b3.c.telia.net  321.173 ms  191.740 ms  192.225 ms
 9  2a02:610:ffff::2  706.159 ms  530.765 ms  614.463 ms
10  2a02:610:ffff:800::2  202.342 ms  200.082 ms  406.142 ms
11  latnet.tv.riga.globalcom.lv  203.721 ms  201.455 ms  204.304 ms
12  titan-gw.v53.ls.lv  203.317 ms  203.947 ms  203.676 ms
13  2a02:610:7500:8::2  201.305 ms  204.173 ms  203.528 ms
14  2a02:610:7500:9::2  204.297 ms  203.132 ms  203.321 ms
15  2a02:610:7501:1000::1  218.454 ms  205.430 ms  399.724 ms
16  2a02:610:7501:1000::2  233.515 ms  229.538 ms  230.771 ms

The difference to when it wasn't working appears to be that I'm getting handed off to Telia in San Jose now rather than make it to Europe (Frankfurt) on HE.

astounding · Thu Aug 11, 2011 6:01 pm

Glad it's back! I didn't hear anything back from HE.net though. It appears HE.net is no longer announcing the prefix to us (which is a good thing if they were unable to transit the traffic to the destination). Looking at HE.net's looking glass via http://lg.he.net/ a traceroute on their network shows:

1 	44 ms 	13 ms 	24 ms 	10gigabitethernet1-2.core1.sjc2.he.net (2001:470:0:2f::2)
2 	7 ms 	1 ms 	1 ms 	sjo-eqx-s1-link.telia.net (2001:2000:3080:1b7::1)
3 	431 ms 	436 ms 	185 ms 	s-b3-v6.telia.net (2001:2000:3018:9::1)
4 	458 ms 	190 ms 	417 ms 	internetf-ic-142059-s-b3.c.telia.net (2001:2000:3080:1bf::2)
5 	179 ms 	468 ms 	191 ms 	2a02:610:ffff::2
6 	534 ms 	667 ms 	638 ms 	2a02:610:ffff:800::2
7 	227 ms 	428 ms 	213 ms 	latnet.tv.riga.globalcom.lv (2a02:610:ffff:1003::2)
8 	420 ms 	229 ms 	415 ms 	titan-gw.v53.ls.lv (2a02:610:7500::1)
9 	206 ms 	424 ms 	200 ms 	2a02:610:7500:8::2
10 	461 ms 	211 ms 	431 ms 	2a02:610:7500:9::2
11 	197 ms 	444 ms 	206 ms 	2a02:610:7501:1000::1
12 	467 ms 	211 ms 	465 ms 	2a02:610:7501:1000::2

That's MUCH better than before. So it looks like the issue is fixed even on HE.net.

Hope IPv6 routing remains stable now.

Aaron out.

janisk · Fri Aug 12, 2011 10:04 am

Hope IPv6 routing remains stable now.

fingers crossed

fewi · Sat Aug 13, 2011 6:43 am

It was stable for a while. Now it's down again. I've also now got two providers up at home: HE and SixXS (which is pretty much all anyone in the US can get if their provider doesn't do native IPv6, which sadly are very, very few). Both are currently down, and both go through a path via Telia to get to you guys (hand off is in San Jose).

Here's some console output.

I can't ping forum.mikrotik.com on its IPv6 address:

$ ping6 forum.mikrotik.com
PING6(56=40+8+8 bytes) 2001:1938:2d2:1:f4d0:bed6:d403:a936 --> 2a02:610:7501:1000::201
^C
--- forum.mikrotik.com ping6 statistics ---
8 packets transmitted, 0 packets received, 100.0% packet loss

Here's a traceroute by name, which works all the way through:

$ traceroute6 forum.mikrotik.com
traceroute6 to forum.mikrotik.com (2a02:610:7501:1000::201) from 2001:1938:2d2:1:f4d0:bed6:d403:a936, 64 hops max, 12 byte packets
 1  2001:1938:2d2:1::1  103.922 ms  1.075 ms  0.932 ms
 2  gw-626.phx-01.us.sixxs.net  24.829 ms  24.722 ms  26.560 ms
 3  2001:4de0:1000:a4::1  35.429 ms  28.663 ms  26.893 ms
 4  1-3.ipv6.r1.ph.hwng.net  27.586 ms  28.680 ms  26.396 ms
 5  2001:478:186::20  25.500 ms  26.789 ms  23.544 ms
 6  10gigabitethernet2-2.core1.lax1.he.net  41.509 ms  49.490 ms  37.460 ms
 7  10gigabitethernet7-4.core1.fmt2.he.net  53.102 ms  43.918 ms  44.672 ms
 8  10gigabitethernet1-1.core1.sjc2.he.net  45.912 ms  49.293 ms  49.999 ms
 9  sjo-eqx-s1-link.telia.net  47.162 ms  46.690 ms  58.478 ms
10  s-b3-v6.telia.net  570.424 ms  362.212 ms  220.187 ms
11  internetf-ic-142059-s-b3.c.telia.net  1008.557 ms  219.077 ms  385.949 ms
12  2a02:610:ffff::2  223.811 ms  562.953 ms  226.176 ms
13  2a02:610:ffff:800::2  388.245 ms  233.370 ms  371.579 ms
14  latnet.tv.riga.globalcom.lv  234.210 ms  530.019 ms  237.380 ms
15  titan-gw.v53.ls.lv  376.968 ms  230.274 ms  375.417 ms
16  2a02:610:7500:8::2  233.006 ms  232.150 ms  373.485 ms
17  2a02:610:7500:9::2  232.839 ms  235.868 ms  232.330 ms
18  2a02:610:7501:1000::1  443.899 ms  606.944 ms  251.256 ms
19  2a02:610:7501:1000::201  363.143 ms  262.169 ms  650.491 ms

Same traceroute by IP. Now it times out within 2a02:610:7501:1000::/64, which I presume belongs to MT as it's the same subnet as the forum server.

$ traceroute6 -n forum.mikrotik.com
traceroute6 to forum.mikrotik.com (2a02:610:7501:1000::201) from 2001:1938:2d2:1:f4d0:bed6:d403:a936, 64 hops max, 12 byte packets
 1  2001:1938:2d2:1::1  15.613 ms  0.978 ms  0.887 ms
 2  2001:1938:81:271::1  25.076 ms  23.659 ms  24.908 ms
 3  2001:4de0:1000:a4::1  23.982 ms  25.489 ms  25.915 ms
 4  2001:4de0:1000:27::2  32.168 ms  33.477 ms  25.959 ms
 5  2001:478:186::20  29.123 ms  29.140 ms  27.062 ms
 6  2001:470:0:159::1  39.221 ms  41.112 ms  37.214 ms
 7  2001:470:0:18d::1  44.757 ms  49.263 ms  46.422 ms
 8  2001:470:0:31::2  90.257 ms  42.918 ms  43.018 ms
 9  2001:2000:3080:1b7::1  44.515 ms  45.537 ms  43.594 ms
10  2001:2000:3018:9::1  435.451 ms  221.150 ms  393.340 ms
11  2001:2000:3080:1bf::2  220.500 ms  393.827 ms  221.502 ms
12  2a02:610:ffff::2  392.899 ms  225.325 ms  388.932 ms
13  2a02:610:ffff:800::2  233.166 ms  381.300 ms  232.706 ms
14  2a02:610:ffff:1003::2  381.661 ms  232.914 ms  233.698 ms
15  2a02:610:7500::1  454.757 ms  232.870 ms  381.570 ms
16  2a02:610:7500:8::2  239.187 ms  375.171 ms  235.660 ms
17  2a02:610:7500:9::2  379.206 ms  234.176 ms  379.692 ms
18  2a02:610:7501:1000::1  252.145 ms  669.444 ms  269.467 ms
19  * * *
20  * * *
21  * * *
22  * *^C

Same traceroute again, 30 seconds later. Now it goes through.

$ traceroute6 -n forum.mikrotik.com
traceroute6 to forum.mikrotik.com (2a02:610:7501:1000::201) from 2001:1938:2d2:1:f4d0:bed6:d403:a936, 64 hops max, 12 byte packets
 1  2001:1938:2d2:1::1  1.486 ms  0.944 ms  0.944 ms
 2  2001:1938:81:271::1  24.723 ms  27.685 ms  23.859 ms
 3  2001:4de0:1000:a4::1  35.441 ms  26.189 ms  35.552 ms
 4  2001:4de0:1000:27::2  30.324 ms  49.688 ms  25.495 ms
 5  2001:478:186::20  26.107 ms  23.827 ms  27.637 ms
 6  2001:470:0:159::1  36.873 ms  36.573 ms  35.450 ms
 7  2001:470:0:18d::1  44.238 ms  48.591 ms  57.892 ms
 8  2001:470:0:31::2  49.625 ms  59.549 ms  50.620 ms
 9  2001:2000:3080:1b7::1  47.365 ms  46.065 ms  43.072 ms
10  2001:2000:3018:9::1  534.894 ms  230.333 ms  220.342 ms
11  2001:2000:3080:1bf::2  470.746 ms  220.084 ms  394.271 ms
12  2a02:610:ffff::2  226.018 ms  388.272 ms  226.768 ms
13  2a02:610:ffff:800::2  387.863 ms  242.481 ms  371.838 ms
14  2a02:610:ffff:1003::2  230.373 ms *  529.351 ms
15  2a02:610:7500::1  230.807 ms  383.587 ms  233.762 ms
16  2a02:610:7500:8::2  380.830 ms  234.498 ms  379.632 ms
17  2a02:610:7500:9::2  232.599 ms  381.850 ms  234.937 ms
18  2a02:610:7501:1000::1  379.337 ms  268.271 ms  653.397 ms
19  2a02:610:7501:1000::201  258.893 ms  662.637 ms  245.033 ms

I can't ping past the hand off where IPs stop resolving to Telia:

$ ping6 2001:2000:3080:1bf::2
PING6(56=40+8+8 bytes) 2001:1938:2d2:1:f4d0:bed6:d403:a936 --> 2001:2000:3080:1bf::2
16 bytes from 2001:2000:3080:1bf::2, icmp_seq=0 hlim=55 time=571.446 ms
16 bytes from 2001:2000:3080:1bf::2, icmp_seq=1 hlim=55 time=491.772 ms
16 bytes from 2001:2000:3080:1bf::2, icmp_seq=2 hlim=55 time=222.008 ms
16 bytes from 2001:2000:3080:1bf::2, icmp_seq=3 hlim=55 time=643.290 ms
16 bytes from 2001:2000:3080:1bf::2, icmp_seq=4 hlim=55 time=564.041 ms
16 bytes from 2001:2000:3080:1bf::2, icmp_seq=5 hlim=55 time=227.589 ms
^C
--- 2001:2000:3080:1bf::2 ping6 statistics ---
6 packets transmitted, 6 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 222.008/453.358/643.290/167.451 ms


$ ping6 2a02:610:ffff::2
PING6(56=40+8+8 bytes) 2001:1938:2d2:1:f4d0:bed6:d403:a936 --> 2a02:610:ffff::2
^C
--- 2a02:610:ffff::2 ping6 statistics ---
4 packets transmitted, 0 packets received, 100.0% packet loss

$ ping6 forum.mikrotik.com
PING6(56=40+8+8 bytes) 2001:1938:2d2:1:f4d0:bed6:d403:a936 --> 2a02:610:7501:1000::201
^C
--- forum.mikrotik.com ping6 statistics ---
8 packets transmitted, 0 packets received, 100.0% packet loss

All this time I can't connect to tcp/80 on forum.mikrotik.com, regardless of whether a traceroute works.

$ telnet -6 forum.mikrotik.com 80
Trying 2a02:610:7501:1000::201...
telnet: connect to address 2a02:610:7501:1000::201: Operation timed out

So to summarize: I can now test via HE as well as SixXS networks. The results on both are the same at this time: can't get to forum.mikrotik.com's IPv6 address on tcp/80. I can't ping it, either. I can ping as far as Telia, and then ICMPv6 as a direct echo request dies. I can traceroute all the way through most of the time, though. I'm not sure what to make of that - ICMPv6 traffic in traceroutes is making it through fine, ICMPv6 for echo requests directly to the end host (the forum server) is not, and tcp/80 to the forum server is - right now - always down. The above is via SixXS, but HE shows exactly the same results, except for the first hops. That's not surprising given that both hand off to Telia - which is what fixed HE in the first place a couple of days ago. Now that path isn't working.

Sorry to be banging on about it.

bigguns · Sat Aug 13, 2011 5:26 pm

I'm having the same issues - but strangely enough, this issue only happens when I use Safari. When using Chrome the page loads as per normal.

fewi · Sat Aug 13, 2011 10:13 pm

Huh. I've tried Safari, Firefox, and Chrome - same issue in all of them. Telnet to tcp/80 doesn't work, either.

Are you sure Chrome isn't just falling back to IPv4, which then works?

fewi · Sun Aug 14, 2011 8:46 pm

Now it's working, through HE via Frankfurt:

$ traceroute6 forum.mikrotik.com
traceroute6 to forum.mikrotik.com (2a02:610:7501:1000::201) from 2001:1938:2d2:1:4d7b:8df1:4318:61ec, 64 hops max, 12 byte packets
 1  2001:1938:2d2:1::1  2.665 ms  1.141 ms  0.982 ms
 2  gw-626.phx-01.us.sixxs.net  26.075 ms  28.751 ms  24.066 ms
 3  2001:4de0:1000:a4::1  43.026 ms  31.257 ms  24.639 ms
 4  1-3.ipv6.r1.ph.hwng.net  30.013 ms  23.985 ms  44.078 ms
 5  2001:478:186::20  26.985 ms  25.480 ms  27.894 ms
 6  10gigabitethernet1-3.core1.dal1.he.net  50.277 ms  52.474 ms  52.420 ms
 7  10gigabitethernet5-4.core1.atl1.he.net  69.003 ms  78.713 ms  73.110 ms
 8  10gigabitethernet6-4.core1.ash1.he.net  105.664 ms  105.292 ms  119.062 ms
 9  10gigabitethernet1-2.core1.nyc4.he.net  99.651 ms  96.807 ms  97.202 ms
10  10gigabitethernet3-3.core1.lon1.he.net  171.602 ms  173.648 ms  171.726 ms
11  10gigabitethernet4-2.core1.fra1.he.net  198.864 ms  385.208 ms  409.522 ms
12  decix-te5-5.38.vln.globalcom.lv  222.926 ms  225.635 ms  379.307 ms
13  2a02:610:ffff:1800::2  232.744 ms  247.471 ms  357.603 ms
14  latnet.tv.riga.globalcom.lv  232.761 ms  231.096 ms  374.145 ms
15  titan-gw.v53.ls.lv  233.212 ms  233.579 ms  372.399 ms
16  2a02:610:7500:8::2  231.088 ms  234.508 ms  370.502 ms
17  2a02:610:7500:9::2  232.276 ms  506.716 ms  233.563 ms
18  2a02:610:7501:1000::1  380.805 ms  643.723 ms  233.606 ms
19  2a02:610:7501:1000::201  380.835 ms  263.298 ms *


$ ping6 -c 4 forum.mikrotik.com
PING6(56=40+8+8 bytes) 2001:1938:2d2:1:4d7b:8df1:4318:61ec --> 2a02:610:7501:1000::201
16 bytes from 2a02:610:7501:1000::201, icmp_seq=0 hlim=47 time=595.412 ms
16 bytes from 2a02:610:7501:1000::201, icmp_seq=1 hlim=47 time=516.979 ms
16 bytes from 2a02:610:7501:1000::201, icmp_seq=2 hlim=47 time=745.930 ms
16 bytes from 2a02:610:7501:1000::201, icmp_seq=3 hlim=47 time=360.393 ms
--- forum.mikrotik.com ping6 statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 360.393/554.678/745.930/139.108 ms


$ telnet -6 forum.mikrotik.com 80
Trying 2a02:610:7501:1000::201...
Connected to forum.mikrotik.com.
Escape character is '^]'.
GET / HTTP/1.0

HTTP/1.0 301 Moved Permanently
Connection: close
Location: http://forum.mikrotik.com/
Content-Length: 0
Date: Sun, 14 Aug 2011 17:45:37 GMT
Server: lighttpd/1.4.19

Connection closed by foreign host.

Let's see if it holds.

janisk · Tue Aug 16, 2011 8:14 am

it is gone. At 1:31 GMT+3 went down. Stops when entering telia/HE realm.

was up for a moment and then again it all went down.

Forum availability via IPv6

Forum availability via IPv6

Re: Forum availability via IPv6

Re: Forum availability via IPv6

Re: Forum availability via IPv6

Re: Forum availability via IPv6

Re: Forum availability via IPv6

Re: Forum availability via IPv6

Re: Forum availability via IPv6

Re: Forum availability via IPv6

Re: Forum availability via IPv6

Re: Forum availability via IPv6

Re: Forum availability via IPv6

Re: Forum availability via IPv6

Re: Forum availability via IPv6

Re: Forum availability via IPv6

Re: Forum availability via IPv6

Re: Forum availability via IPv6

Re: Forum availability via IPv6

Re: Forum availability via IPv6

Re: Forum availability via IPv6

Re: Forum availability via IPv6

Re: Forum availability via IPv6

Re: Forum availability via IPv6

Re: Forum availability via IPv6

Re: Forum availability via IPv6

Re: Forum availability via IPv6

Re: Forum availability via IPv6

Re: Forum availability via IPv6

Re: Forum availability via IPv6

Re: Forum availability via IPv6

Re: Forum availability via IPv6

Who is online