Connectivity has been restored in my case.

I received the following reply from the ticket I submitted earlier

"It wasn't taking updates earlier, but should be fine now."

Also seeing issues with tserv4.nyc4 as well. was working fine this morning but as soon as I rebooted my router which gave a new ipv4 address I lost all ipv6 connectivity. Oddly enough I have another site still connected to that pop which has not lost connectivity.

so far I checked that ddns updated my ipv4 endpoint ok or at least the tunnel config page says it's been updated.
first wireshark capture shows 209.51.161.14 is replying with icmp type 3 code 3 port unreachable.

have you already submitted a ticket?

Something up with tserv1.nyc4.he.net today? I don't see it on the tunnel stats page at all, and my tunnel isn't receiving anything from HE. I've had this tunnel up and running since 2013 so I'm sure I've got it configured properly. I went ahead and set up my own 6in4/protocol 41 from the office to one of my colocated servers just to verify that the ISP hadn't decided to block 6in4 tunnels or something, and that worked fine.

My tunnel just started working.

Will we need to do anything at our ends to access the tunnels via London?

 :'(Downtime now 20h30m

Tunnels have temporarily been migrated to a London tunnel server until the primary Amsterdam server is back in service.  Part of the migration process temporarily disables the server migrated from, which is why it dropped off the status page briefly.

I'm also affected, I also no longer see tserv11.ams1 on the status page?

The tserv11.ams1 is still down. When will this be resolved?

Also affected and keep on checking status. Shall I move to another tunnel server or better keep on waiting?

I haven't found any news from HE.net about tserv11.ams1, so next option place it on the forum.

Hopefully somebody can explain what is wrong...

Sfxdana