On 14th July after an OS update I rebooted the server which manages our SixXS tunnel. It would appear that (after two years of inaction) a launch script started working which resulted in the TIC server getting hammered. We received an auto-email alerting us to this and the server was blocked from issuing TIC requests. When you do this sort of thing, an alert box appears on one's SixXS home page alerting you to your error: Having received the email from SixXS, immediately we made some changes to config files to correct the error. On the 19th I tried to manually start up the tunnel. I received a "TIC server not responding" error and the alert box on my SixXS' home page incremented the TIC requests count to 206. (Which to my mind shows that the alert box is updated in near real time which in turn suggests that we have fixed the core problem as the TIC request count has not materially moved since the 14th and has not changed at all since the 19th. We're now just waiting for the TIC block to time out). So on to the main point of this post: Does anyone have any idea how long it takes TIC blocks to time out? We're now a week on from the initial cock up but still no IPv6. I dare not try to fire things up manually as it'll simply increment the TIC requests count perhaps delaying the removal of the block yet further. I have sent an email to info@ detailing the steps taken to fix the issue. This seems to have fallen on stoney ground as the somewhat curt response (to the second email) was to stop hammering on the TIC server and "fix your setup". As both of these conditions had been fulfilled prior to sending the email (and were detailed in the email), I'm unsure as to next steps. Comments / advice as to how to deal with this welcome. TIA Simon