@toor said:
Yay! The networking on NYC metro node NYCB044 on subnet 185.213.19.0/24 just started working!
Sadly it's still not working on NYCB045; can't even ping the gateway from the VPS. Is this a known issue @VirMach or should I just accept that it's especially cursed and give up / reinstall / sacrifice a goat?
This should've been fixed but there's so much going on right now it's possible I missed it. This should have been fixed with NYCB044 though which people said works above your comment so I'm leaning toward I made some error in fixing it.
@Sahu1990 said: @VirMach
Hello, my VPS on TYO037 went offline after the new IP assigned, I didn't ask for an early assignment before the maintenance, and I can't do anything about it now. Anything wrong?
@toor said:
Yay! The networking on NYC metro node NYCB044 on subnet 185.213.19.0/24 just started working!
Sadly it's still not working on NYCB045; can't even ping the gateway from the VPS. Is this a known issue @VirMach or should I just accept that it's especially cursed and give up / reinstall / sacrifice a goat?
This should've been fixed but there's so much going on right now it's possible I missed it. This should have been fixed with NYCB044 though which people said works above your comment so I'm leaning toward I made some error in fixing it.
Would a ticket help keep it on your radar, or would that just go into the huge bin of "tickets I'm never gonna get to" that you must be facing right now? :-)
NYC Networking Outage Reported
Opened 2026-05-29 23:32:31
New subnets on NYC do not have global reachability. This is an upstream issue that we are waiting on to get resolved.
Ny SJCZ003 is also still down
RYZE.LAX-A026.VMS is also unreachable. Will try to reconfigure.
@VirMach Received two emails (for two vps) giving new IPs originally on AMSD018.
One Ticket ID shows originally 2 v4 IPs and now only one is allocated (Ticket ID: 163985).
Interesting that there are 3 v6 addresses?
Just wanted to flag before you get inundated
I've been locked out of my account for a bit of time, right when the IPs change. I can't even open a support ticket anymore. Bummer, I typically like virmach.
@taizi said:
is tokyo still exist?i see the whole ip range are not announced at all
I have three VMs in Tokyo that seem to be working on nodes TYOC007, TYOC035, and TYOC039. IPv4 only, no native IPv6.
The RPKI Chain for the three IP ranges show as valid.
@taizi said:
is tokyo still exist?i see the whole ip range are not announced at all
I have three VMs in Tokyo that seem to be working on nodes TYOC007, TYOC035, and TYOC039. IPv4 only, no native IPv6.
The RPKI Chain for the three IP ranges show as valid.
@VirMach said: This is Miami, right? Your server's in Oklahoma, since that project stalled out I never finished re-assigning IP addresses and bringing it back online. You'll just get a service extension and it'll be brought back when it's ready.
Only like half a dozen people or so are affected so I'm not spending any time on that issue right now, sorry.
If the data doesn't matter, you'll likely see some new system get activated and contact you about being able to redeploy automatically elsewhere once it's ready. This also applies to anyone else stuck on a dead server right now. That system's almost ready too.
Comments
Looks like both of the services where I'd need it indeed are. Thanks for the heads up!
This should've been fixed but there's so much going on right now it's possible I missed it. This should have been fixed with NYCB044 though which people said works above your comment so I'm leaning toward I made some error in fixing it.
Not fully down, being looked into already (I'm waiting on DC request.)
TYOC038 was never ON.
Would a ticket help keep it on your radar, or would that just go into the huge bin of "tickets I'm never gonna get to" that you must be facing right now? :-)
This has been fixed, and VPS is now on AMSD037 and is working fine with new IPv4.
@VirMach
My NYCB013 network unreachable
Ny SJCZ003 is also still down
RYZE.LAX-A026.VMS is also unreachable. Will try to reconfigure.
https://microlxc.net/
Where is @AuroraZero
@imok Talked with him a few days ago. He seems to be doing okay. I'm still hosting MetalVPS.com on YetiNode free.
Send my greetings to him. Hopefully he's still having a good time with his gay neighbor.
Why are @AuroraZero and @FrankZ never online at the same time and @FrankZ and @VirMach always online and offline together?
That was a good one
@VirMach Received two emails (for two vps) giving new IPs originally on AMSD018.
One Ticket ID shows originally 2 v4 IPs and now only one is allocated (Ticket ID: 163985).
Interesting that there are 3 v6 addresses?
Just wanted to flag before you get inundated
Get your FREE VPS if you develop Open Source software
is tokyo still exist?i see the whole ip range are not announced at all
I've been locked out of my account for a bit of time, right when the IPs change. I can't even open a support ticket anymore. Bummer, I typically like virmach.
I have three VMs in Tokyo that seem to be working on nodes TYOC007, TYOC035, and TYOC039. IPv4 only, no native IPv6.
The RPKI Chain for the three IP ranges show as valid.
What node or IP range are you speaking of ?
Does IPv6 work at all?
I'm not sure on which (host) node I'm on but my IPv6 is not working (was working before the IPv4 migration).
@nullnothere Will get back to you unless someone else replies before me.
Get your FREE VPS if you develop Open Source software
tyoc040 176.119.148.0/24
yep, that range does seem to have BGP issues.
@VirMach
Probably super low priority issue, but amazon pay seems to be broken.
@VirMach
LAX1Z020has been down since 3 JUN 2026...💩 VirCrap 💩
Nothing so far
@VirMach How can I verify what my web host IP address is when the control panel is broken and not working?