Since one hour, Smokeping was complaing my Storage VPS is down. Rebooted it, IPv4 is up again, but IPv6 still down. Interestingly the controlpanel shows 2 /64 prefixes for the server now, bot none of them work. Even the default gw fe80::1 is not pingable.
Comments
Same here.
Same here.
That too.
Old GleSYS AB /64 and new Prinode AB /64 subnet.
confirmed. 25min downtime according to hetrixtools. ping google from putty no response, but nextcloud is normal
Sultan Muda - Amazon Store
Old /64 seems up again OBE.
Not here. Still down.
What does it mean "OBE"?
The upstream maybe - Obenetwork AB.
EDIT: Or maybe not, since that would be Portlane/GleSYS
It's both?
From Netcup:
And from my FTTH:
And the "new" address from Netcup:
And from FTTH (really strange as my ISP (AS50629) also peers at Amsix:
Not sure if this is related, but sharing since it's Stockholm.
It is related. When network came back after the maintenance, IPv6 didn't work anymore.
btw. nice vps name.
Well, it's still 21.08.23 CEST, not 22.08. The maintenance according to the announcement should be tomorrow.
ah, crap... you're correct
And the outage began around 15:30 CEST or so, maybe @hosthatch srambled the dates and timezones?
Or this upcoming maintenance is to address the issue(s).
I did not have any issues before.
Ipv6 working for me now.
Anyone tryed new one too?
My old is still down and I am wondering if I should switch to the new one.
For me both are working, but the gateway is from the old prefix.
Now down again since 22.12h CEST, within the announced timeslot.
"boot it back online" did not happen. Started it via control panel, IPv4 works, IPv6 are broken. IPv6-gateway is still 2a00:1a28:1157::1.
Edit: Both up again.
In my case IPv6 never came back since first outage from 2 days ago.
Before I opened ticket I've redone everything from the beginning. No luck.
Can you post
ip -6 route
output please (blank out part of your subnet).I didn't configure network, it auto switched to the new ipv6.
Can you post "ip -6 route" output please (blank out part of your subnet).
Got a reply to my ticket from the first outage which asked me to reconfigure according to https://docs.hosthatch.com/networking/#ipv6-configuration
Does fe80::1 reply on your box?
How? The docs says
Yes, that's my IPv6 setup on every HH vps (and it worked also on .se until this outage from 2days ago)
Reply?
"If you choose to enable IPv6 when you first create your server, it will automatically be configured via cloud-init. However, manual configuration is needed if you choose to enable it after your server has been created, or if you install your OS via ISO."
I tryed it also with clean reinstall from the template. It show initial ::1 IP in interface set by template, but still no luck.
I've deleted the old one now and activated the new one from 2a0e:dc0:2::/48
I tryed both, no luck and I am out of ideas as everything seems in order at my end.
I will reinstall it once again via ISO (that's template now) once I come home and this is it ...at the mercy of their support.
I don't see the new prefix in your output.
Because it makes no difference. I tryed all combinations.
I just tried and both, old and new subnet works.