They have updated the original alert on the website and did reply to my email from this morning

They've replied to me, too, but not with any substantive information, merely that the issue has been passed on and that they haven't yet updated the service alert. It's disappointing that Zen can't be more open about what's happening and that they still apparently regard IPv6 as a niche protocol beyond the knowledge of their first-line support staff.

I haven't noticed any IPv6 issues up until last night, and indeed this morning I found no IPv6 connectivity. Fired off an email to Zen and it's been dead all morning, but just as I logged in and started writing this reply my pings are coming back in, so it looks like I'm back online.

My IPv6 connectivity is now working again, so the outage was reasonably short today. I'd still welcome some technical detail about what happened.

Edited by ashdown (Tue 15-Oct-24 11:52:06)

Indeed - I got the same useless reply.
Looks like things came back around 11:30 looking at some long running processes.

It did highlight an odd issue though with one of my apps - it kept trying to connect out via v6 even though it was ending in a failure and would never try the v4 addresses (which was working) (Ruby net:http)

In reply to a post by IamQ:

Indeed - I got the same useless reply.
Looks like things came back around 11:30 looking at some long running processes.

It did highlight an odd issue though with one of my apps - it kept trying to connect out via v6 even though it was ending in a failure and would never try the v4 addresses (which was working) (Ruby net:http)

There is an algorithm called "Happy Eyeballs" that's supposed to fix that. Web browsers all implement it and I think the networking stack in Android and iOS does too but command line apps like Ruby typically don't, they are very dumb and try the first address given to them and if that times out then it times out.