@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.
@Brayvin said: @VirMach How can I verify what my web host IP address is when the control panel is broken and not working?
just start going through them, you will find it eventually, its the one that works with your password.
TierHive - Hourly VPS - NAT Native - /24 per customer - DE, UK, SG, CA, USA x4, FR x2, AU, PL, NL, JP FREE tokens on sign up, try before you buy. | Static Hosting Free for life: https://tierhive.com/static-hosting/
@tulipyun said: Today marks six months since SJC went offline. Would you be willing to share any stories, information or future plans regarding SJC with everyone?
>
I am on the same server node SJCZ012 as you. I am also eagerly awaiting the official virmach announcement.
This whole IP renumbering looks to have killed my NY box; I think once a ticket reaches "Awaiting Technical Review", that means "sorry your box is gone"
The situation is complicated because crime is gaining ground and the government is stealing left and right. We are on our way to becoming an authoritarian country, if we aren't already.
The situation is complicated because crime is gaining ground and the government is stealing left and right. We are on our way to becoming an authoritarian country, if we aren't already.
Poor Paddington, he must be very angry.
Sounds like it's going the same way as the UK for similar and different reasons
TierHive - Hourly VPS - NAT Native - /24 per customer - DE, UK, SG, CA, USA x4, FR x2, AU, PL, NL, JP FREE tokens on sign up, try before you buy. | Static Hosting Free for life: https://tierhive.com/static-hosting/
The situation is complicated because crime is gaining ground and the government is stealing left and right. We are on our way to becoming an authoritarian country, if we aren't already.
Sorry to hear that things are so bad. What may be the worst part is when people lose the expectation that things will get better and instead expect it will get worse as time goes on.
@lesuser said:
My VPS in NYCB043 is not accessible ever since its IP was changed a month ago. It is up and I can connect via VNC though.
I've extended service duration by a month since we're still getting this node mentioned. I've already (2-3 weeks ago) resolved the initial problem affecting the node. I saw the reports here and took a look and could not find another issue. I have looked into it again, this time reading and responding to a few tickets and so far I have confirmed it appears that anyone left still having issues on NYCB043 needs to manually configure the networking within their operating system.
I'll update you guys here if I notice anything else. Given everything I have reviewed though, I am fairly confident in this assessment.
One quick way to verify this for yourself so you do not waste a long time fixing the configuration only to find out it was an issue on our end would be to mount an ISO, boot into it, and see if connectivity works there.
I'll give a quick example. Pick System Rescue CD, change boot order to CD ROM, reboot, then type in startx on VNC, open terminal, and add route: ip route add default via 185.213.18.1 as well as your IP address: ip addr add 185.213.18.xx/24 dev ens3 and make sure the link is up (ip link set ens3 up) and then open Chrome or ping 8.8.8.8; if you're able to do that, it means it's most definitely an issue with your operating system's network configuration and that the automatic reconfiguration is not working.
@ahnlak said:
This whole IP renumbering looks to have killed my NY box; I think once a ticket reaches "Awaiting Technical Review", that means "sorry your box is gone"
Which node is this on? I vaguely remember I spoke with you some time ago and you must have been on NYCB043, 44, or 45. And I addressed issues with those nodes at that time. So it's highly likely if you are still facing an issue, my comment above should also be helpful to you.
I'm here, I'm just not in a very "random walls of text" mood. There should have been one comment I made around June 12th which I don't see, so that means I wrote it out and didn't click post or though I did. That was in response to msatt and someone else. I definitely saw the comment about Amazon pay being broken after that, I saw the comment about LAX1Z020 being down, about Oklahoma. I saw Brayvin's comment asking about webhosting and did not have time to look into that (and saw Anthony's joke.) I saw tulipyun's 6 month anniversary post about SJC and the few comments after it and it's been kind of quiet other than that.
I will admit though I did not see your comment and the ones after it (so I've 100% been gone from LES around June 22nd to today.) I just haven't had time this past week to check.
My next reply will likely be about San Jose, hopefully this week.
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?
Magic!
just start going through them, you will find it eventually, its the one that works with your password.
TierHive - Hourly VPS - NAT Native - /24 per customer - DE, UK, SG, CA, USA x4, FR x2, AU, PL, NL, JP
FREE tokens on sign up, try before you buy. | Static Hosting Free for life: https://tierhive.com/static-hosting/
Hello, @VirMach
Today marks six months since SJC went offline. Would you be willing to share any stories, information or future plans regarding SJC with everyone?
May SJC will be reborn soon.
>
I am on the same server node SJCZ012 as you. I am also eagerly awaiting the official virmach announcement.
This whole IP renumbering looks to have killed my NY box; I think once a ticket reaches "Awaiting Technical Review", that means "sorry your box is gone"
VirMach has disappeared again.
And also @FrankZ
Someone called ?
Is @VirMach back too?
My VPS in NYCB043 is not accessible ever since its IP was changed a month ago. It is up and I can connect via VNC though.
Powerful AMD Ryzen VPS (aff)
Maybe
How is life in Peru these days ?
Difficult.
The situation is complicated because crime is gaining ground and the government is stealing left and right. We are on our way to becoming an authoritarian country, if we aren't already.
My NY VPS lost connectivity in the Great IP Change too; given we're back to radio silence and ignored tickets, I've just kind of written it off.
Poor Paddington, he must be very angry.
Sounds like it's going the same way as the UK for similar and different reasons
TierHive - Hourly VPS - NAT Native - /24 per customer - DE, UK, SG, CA, USA x4, FR x2, AU, PL, NL, JP
FREE tokens on sign up, try before you buy. | Static Hosting Free for life: https://tierhive.com/static-hosting/
Sorry to hear that things are so bad. What may be the worst part is when people lose the expectation that things will get better and instead expect it will get worse as time goes on.
Will @virmach save us?
Magic 8 ball says ....
I am at SF again and I miss @uptime
食之无味 弃之可惜 - Too arduous to relish, too wasteful to discard.
I've extended service duration by a month since we're still getting this node mentioned. I've already (2-3 weeks ago) resolved the initial problem affecting the node. I saw the reports here and took a look and could not find another issue. I have looked into it again, this time reading and responding to a few tickets and so far I have confirmed it appears that anyone left still having issues on NYCB043 needs to manually configure the networking within their operating system.
I'll update you guys here if I notice anything else. Given everything I have reviewed though, I am fairly confident in this assessment.
One quick way to verify this for yourself so you do not waste a long time fixing the configuration only to find out it was an issue on our end would be to mount an ISO, boot into it, and see if connectivity works there.
I'll give a quick example. Pick System Rescue CD, change boot order to CD ROM, reboot, then type in startx on VNC, open terminal, and add route: ip route add default via 185.213.18.1 as well as your IP address: ip addr add 185.213.18.xx/24 dev ens3 and make sure the link is up (ip link set ens3 up) and then open Chrome or ping 8.8.8.8; if you're able to do that, it means it's most definitely an issue with your operating system's network configuration and that the automatic reconfiguration is not working.
Which node is this on? I vaguely remember I spoke with you some time ago and you must have been on NYCB043, 44, or 45. And I addressed issues with those nodes at that time. So it's highly likely if you are still facing an issue, my comment above should also be helpful to you.
I'm here, I'm just not in a very "random walls of text" mood. There should have been one comment I made around June 12th which I don't see, so that means I wrote it out and didn't click post or though I did. That was in response to msatt and someone else. I definitely saw the comment about Amazon pay being broken after that, I saw the comment about LAX1Z020 being down, about Oklahoma. I saw Brayvin's comment asking about webhosting and did not have time to look into that (and saw Anthony's joke.) I saw tulipyun's 6 month anniversary post about SJC and the few comments after it and it's been kind of quiet other than that.
I will admit though I did not see your comment and the ones after it (so I've 100% been gone from LES around June 22nd to today.) I just haven't had time this past week to check.
My next reply will likely be about San Jose, hopefully this week.