Peering between tserv5 and gogo6 down?

[normanr]

$ mtr -w -c 2 -r --address 2001:470:1f08:ad6::2 gogonet.gogo6.com

HOST: darkflame                                Loss%   Snt   Last   Avg  Best  Wrst StDev
  1. normanr-1.tunnel.tserv5.lon1.ipv6.he.net  0.0%     2   46.9  46.2  45.5  46.9   1.0
  2. gige-g4-6.core1.lon1.he.net               0.0%     2   39.0  38.2  37.4  39.0   1.1
  3. 2001:7f8:4::1935:1                        0.0%     2   38.9  45.4  38.9  52.0   9.2
  4. ???                                      100.0     2    0.0   0.0   0.0   0.0   0.0

Traffic from SixXS to gogo6 is fine, so if traffic from tserv5 to google and kame.

[broquea]

Not really a tunnel-server issue, as it is that it isn't getting beyond the network advertising their space (/39 in this case). Oddly they announce it to us everywhere we peer but only London seems to have an issue. Looking into it, as for some reason in a traceroute6, it stops in TATA's network:

Code Select Expand

3  2001:5a0:c00:600::2  350.35 ms !N  31.98 ms !N  249.634 ms !N

*EDIT* - emailed TATA to have them take a look.

[normanr]

Yea, I couldn't find a forum category for reporting network issues :-( Is there a better place/way?

[broquea]

email ipv6@he.net and it will open a trouble ticket

[normanr]

Any update on this? My SmokePing graphs are showing the route is still down.  Should I email to create a ticket, or has a ticket been logged already (if so can you add me as a cc?)

[broquea]

TATA only just responded today that they opened an internal ticket to look into it.

[normanr]

Cool, thanks!

[normanr]

This seems to be fixed now.