SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #8253730
Ticket Status: Remote Problem

PoP: usqas01 - OCCAID Inc. (Ashburn, Virginia)

No route to subnet. Unknown if SixXS issue or not.
[us] Shadow Hawkins on Tuesday, 20 November 2012 01:56:58
I'm unaware if this is a SixXS issue or not, but I'm unable to access 2607:f5a0:0:153::/64 from my sixxs tunnel. This was tested from my tunnel and a friends tunnel, both which are on usqas01. The subnet is however accessible from VPS on OVH's network. Have been unable to access since somewhere around 11/14/2012.
No route to subnet. Unknown if SixXS issue or not.
[ch] Jeroen Massar SixXS Staff on Tuesday, 20 November 2012 07:22:00
When reporting routing issues, please include traceroutes. In this case though it is obvious that the remote network is broken:
5 TenGE13-2.br02.ams01.pccwbtn.net (2001:7f8:1::a500:3491:1) 98.601 ms 98.419 ms 98.211 ms 6 2400:8800:7f02:5::2 (2400:8800:7f02:5::2) 143.116 ms 142.949 ms 143.008 ms 7 2607:f5a0:1:1::2 (2607:f5a0:1:1::2) 143.084 ms 143.345 ms 143.172 ms 8 2800:5d0:100:1::301 (2800:5d0:100:1::301) 144.389 ms 144.535 ms 144.248 ms 9 2800:5d0:100:1::301 (2800:5d0:100:1::301) 3144.181 ms !H * *
Please contact them to resolve their problem.
State change: remoteproblem Locked
[ch] Jeroen Massar SixXS Staff on Tuesday, 20 November 2012 07:22:04
Message is Locked
The state of this ticket has been changed to remoteproblem

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker