SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #1189608
Ticket Status: User

PoP: plwaw01 - ICM (Warsaw)

Tunnel downtime for a working tunnel?
[pl] Shadow Hawkins on Monday, 31 August 2009 08:14:00
I've recently changed my IPv4 endpoint (on 27.08.2009) on my tunnel T14597. Since then, according to graphs on the "Tunnel information" page, packet losses for my IPv6 address (2001:6a0:200:6d::2) are high. Also, I received an e-mail about my tunnel downtime (and get -5 penalty ISK). The problem is that this tunnel was up for the whole time (and still is). I can ping PoP IPv6 (2001:6a0:200:6d::1) and other IPv6 addresses, like e.g. ipv6.google.com. I've also tried using your online traceroute tool on my IPv6 address - it also works without a problem. What can I do about it?
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Tuesday, 01 September 2009 21:57:01
Message is Locked
The state of this ticket has been changed to user
Tunnel downtime for a working tunnel?
[ch] Jeroen Massar SixXS Staff on Tuesday, 01 September 2009 21:57:43
Start by reading that big orange box which instructs you to read the FAQ, the contact page and of course that nice checklist.

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

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