TierHive - Hourly VPS - NAT Native - /24 per customer - DE, UK, SG, CA, USA x3, FR, AU, PL, NL FREE tokens on sign up, try before you buy. | Join us on Reddit
@flips said:
I've got a VPS that was originally in Denver, now the panel says it's on LAXA024. (Probably moved a long time ago.) It doesn't seem to have gotten any new IP assigned, the panel and the VM inside has the same IP configured … But it says: Multiple issues — 4 related events cluster Scheduled
Opened 2026-05-06 14:10:13
This is a grouped incident covering 4 related issues. Expand for per-event details.
I'm not sure how to expand the issues from there, though … The host is up, I can login through the console. But inside the VM I can't ping default gateway. If the system tries network autoconfig, I'm pretty sure it will fail, as it thinks the VM runs Debian, while it's actually running OpenBSD …
On the network status page I found this affecting my node there:
Ongoing scheduled maintenance at LAX #787
… But it's listed as resolved … 🤷♂️😅
The automatic network issue are not perfect right now when it comes to things flying around. I haven't focused on fixing that right now. In your case though, it being "resolved" is correct. Just your specific VM is not, which would potentially show up in the future, I just haven't hooked up individual/partial outages as automatic in the system yet.
There was a bug on this and/or human error that caused some to be skipped over. I'm still cleaning everything up now.
Ticket #147394
Last November, I was double-charged by PayPal for a payment I made.
My support ticket has been pending for quite some time now; could you please assist me with this? A refund is not necessary; simply converting the duplicate payment amount into account credit would suffice.
Last November, I was double-charged by PayPal for a payment I made.
My support ticket has been pending for quite some time now; could you please assist me with this? A refund is not necessary; simply converting the duplicate payment amount into account credit would suffice.
strange that this did not happen automatically.
usually when you set up a paypal subscription and paypal automatically sends the money and you also manually pay it goes against the same original invoice number and the system updates your credit balance, have you checked your credit balance?
TierHive - Hourly VPS - NAT Native - /24 per customer - DE, UK, SG, CA, USA x3, FR, AU, PL, NL FREE tokens on sign up, try before you buy. | Join us on Reddit
TierHive - Hourly VPS - NAT Native - /24 per customer - DE, UK, SG, CA, USA x3, FR, AU, PL, NL FREE tokens on sign up, try before you buy. | Join us on Reddit
I seem to be encountering much the same issue as @flips .
The server (LAX1Z013) is online—I can access it via VNC—but in reality, it is unable to establish any external network connectivity.
(...)
Well. I just found the server's IP is changed to a new one and it is working now. seem back "real online" 7 hours ago.
My VPS still has the same IP listed, so I guess we had different issues ... 😅
Mine is still without contact with the network ... I'm loosing millions (of pesos pr decade of downtime) on this ...
Either way, I belive in second chances. If he was away for a reason and is back now, he deserves a second chance. And that's not a sarcasm.
I suspect @VirMach is a bear; he just needs time to hibernate.
That's fine, as long as they have someone else covering support during the hibernation period. The issue arose because they did not have anyone fixing client issues.
I speak fluent sarcasm and broken logic. | I would agree with you, but thæn we’d both be wrong.
@flips said:
I've got a VPS that was originally in Denver, now the panel says it's on LAXA024. (Probably moved a long time ago.) It doesn't seem to have gotten any new IP assigned, the panel and the VM inside has the same IP configured … But it says: Multiple issues — 4 related events cluster Scheduled
Opened 2026-05-06 14:10:13
This is a grouped incident covering 4 related issues. Expand for per-event details.
I'm not sure how to expand the issues from there, though … The host is up, I can login through the console. But inside the VM I can't ping default gateway. If the system tries network autoconfig, I'm pretty sure it will fail, as it thinks the VM runs Debian, while it's actually running OpenBSD …
On the network status page I found this affecting my node there:
Ongoing scheduled maintenance at LAX #787
… But it's listed as resolved … 🤷♂️😅
The automatic network issue are not perfect right now when it comes to things flying around. I haven't focused on fixing that right now. In your case though, it being "resolved" is correct. Just your specific VM is not, which would potentially show up in the future, I just haven't hooked up individual/partial outages as automatic in the system yet.
There was a bug on this and/or human error that caused some to be skipped over. I'm still cleaning everything up now.
Hello, all Tokyo nodes are experiencing issues with IPv6, specifically the IPv6 gateway being unable to connect to the public network.
Last November, I was double-charged by PayPal for a payment I made.
My support ticket has been pending for quite some time now; could you please assist me with this? A refund is not necessary; simply converting the duplicate payment amount into account credit would suffice.
strange that this did not happen automatically.
usually when you set up a paypal subscription and paypal automatically sends the money and you also manually pay it goes against the same original invoice number and the system updates your credit balance, have you checked your credit balance?
You have no notifications at this time.
already check ,none credit balance
Last November, I was double-charged by PayPal for a payment I made.
My support ticket has been pending for quite some time now; could you please assist me with this? A refund is not necessary; simply converting the duplicate payment amount into account credit would suffice.
strange that this did not happen automatically.
usually when you set up a paypal subscription and paypal automatically sends the money and you also manually pay it goes against the same original invoice number and the system updates your credit balance, have you checked your credit balance?
You have no notifications at this time.
already check ,none credit balance
That's tough... Hopefully they sort it out for you @VirMach
TierHive - Hourly VPS - NAT Native - /24 per customer - DE, UK, SG, CA, USA x3, FR, AU, PL, NL FREE tokens on sign up, try before you buy. | Join us on Reddit
Heh, this one VPS had been down so long, that I forgot about a script in cron pulling in a huge backup file every night … All of a sudden my VPS had a full root fs … (Back when I set it up, the backup required 30 GB, now it requires >40 GB …) I since bought a replacement with a larger drive, so … not sure what I should use this one for … (I do have some ideas, of course …)
@VirMach said: Good chance for all the remaining issues to be resolved today. Most have them been worked through, a few servers giving me issues in terms of being finicky with migrations and such.
It's been some time and my server on LAXA017 still has no connectivity. Already sent a ticket but only got AI response.
@VirMach said: Good chance for all the remaining issues to be resolved today. Most have them been worked through, a few servers giving me issues in terms of being finicky with migrations and such.
It's been some time and my server on LAXA017 still has no connectivity. Already sent a ticket but only got AI response.
I’m not sure if this will lighten your workload, but if you could migrate my server to Japan, I don’t need to retain any data; you can simply set up a blank VPS for me.
@VirMach said: Good chance for all the remaining issues to be resolved today. Most have them been worked through, a few servers giving me issues in terms of being finicky with migrations and such.
It's been some time and my server on LAXA017 still has no connectivity. Already sent a ticket but only got AI response.
There's up to 2 services on LAXA026, 2 on LAXA025, 1 on LAXA023, 3 on LAXA021, 5 on LAXA017, 1 on LAXA016, 1 on LAXA014, 1 on LAXA012, 12 on LAXA011, 2 on LAXA010, 2 on LAX1Z020, and 2 on LAXA006 that still need a change.
Most of these just show up because I need to rework the conflict detection system to better handle some outlier cases. I thought all of these remaining ones were bogus but after your comment I had a look and there's a very small number still incorrect. I'll go through these, credit everyone and correct them.
Is yours having this issue with the new IP or is the IP still the old IP?
@tulipyun said:
The progress of the SJC restoration/migration is no longer displayed on the network status page.
I hope @VirMach can provide some updates, given that the service has been offline for five months and the last update was several weeks ago.
Thanks.
There's one of them that was moving to TYOC038. In the process, it knocked out TYOC038. So I started moving TYOC038 to a new node, TYOC032. That one ran into problems. I feel like that's a good example to point to on why it's not done. Many of the others were slated to be moved to other nodes that also ran into issues. I've had to rework what's happening several times. LAX just went through renumbering in a way that did not assume we'd shift migrations for SJC, so that's been difficult to fit in. I'm definitely spending time on it every day, it's just not going well.
As for it not being on the network status page, I have no idea what happened. I can confirm it's no longer on the network status page, but on my end admin side, it is. I have a few guesses based on what's changed since then, but it's not actively being looked at right now.
@tulipyun said:
The feature for migrating instances appears to have been removed.
Its been sunset
Never to return
Long like VirBot migration
You will be remembered well
Turned off to avoid potential issues as I reworked parts of the shared system for migrations. It's working better now for mass migrations, but I have to spend some time to re-test individual migration feature before turning it back on.
@tuc said: Did you update your vps network interfaces?
It's on DHCP on the same network interface and still receiving a response, so I don't need to change those.
@VirMach said: Is yours having this issue with the new IP or is the IP still the old IP?
It is on the same IP, I did not received any IP migration of some sort, only the node migration was show up ~a week ago. See ticket #688091 for the AI-assisted ticket.
@tuc said: Did you update your vps network interfaces?
It's on DHCP on the same network interface and still receiving a response, so I don't need to change those.
@VirMach said: Is yours having this issue with the new IP or is the IP still the old IP?
It is on the same IP, I did not received any IP migration of some sort, only the node migration was show up ~a week ago. See ticket #688091 for the AI-assisted ticket.
I can confirm you are 1 of 5 virtual servers affected on LAXA017. That's good, it means nothing weird going on that isn't already accounted/detected.
I went ahead and corrected yours using the conflict scanner tool instead of "officially" and extended the due date manually. This just means you won't get communication for it and it won't appear in your history.
Comments
At this rate, Virmach is going to get a provider tag back and start posting offers again.
TierHive - Hourly VPS - NAT Native - /24 per customer - DE, UK, SG, CA, USA x3, FR, AU, PL, NL
FREE tokens on sign up, try before you buy. | Join us on Reddit
He seems to be back for real and putting in real effort to recover the reputation. I support his comeback with open arms.
Ticket #147394
Last November, I was double-charged by PayPal for a payment I made.
My support ticket has been pending for quite some time now; could you please assist me with this? A refund is not necessary; simply converting the duplicate payment amount into account credit would suffice.
strange that this did not happen automatically.
usually when you set up a paypal subscription and paypal automatically sends the money and you also manually pay it goes against the same original invoice number and the system updates your credit balance, have you checked your credit balance?
TierHive - Hourly VPS - NAT Native - /24 per customer - DE, UK, SG, CA, USA x3, FR, AU, PL, NL
FREE tokens on sign up, try before you buy. | Join us on Reddit
I wish I knew how to interpret your comments
Get your FREE VPS if you develop Open Source software
yes.
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
https://lowendspirit.com/uploads/editor/gi/ippw0lcmqowk.png
what has 5 toes and is not your foot?
My foot
TierHive - Hourly VPS - NAT Native - /24 per customer - DE, UK, SG, CA, USA x3, FR, AU, PL, NL
FREE tokens on sign up, try before you buy. | Join us on Reddit
My VPS still has the same IP listed, so I guess we had different issues ... 😅
Mine is still without contact with the network ... I'm loosing millions (of pesos pr decade of downtime) on this ...
Let's just say my comment has dual meaning. Open arms can mean a hug but can also be used to slap depending on the situation
Either way, I belive in second chances. If he was away for a reason and is back now, he deserves a second chance. And that's not a sarcasm.
I suspect @VirMach is a bear; he just needs time to hibernate.
That's fine, as long as they have someone else covering support during the hibernation period. The issue arose because they did not have anyone fixing client issues.
I got a new IP assigned and VPS back online now …
The feature for migrating instances appears to have been removed.
The feature is under migration
Virmach Deals
Its been sunset
Never to return
Long like VirBot migration
You will be remembered well
Hello, all Tokyo nodes are experiencing issues with IPv6, specifically the IPv6 gateway being unable to connect to the public network.
You have no notifications at this time.
already check ,none credit balance
Will VirBot come back soon? @VirMach
Virmach Deals
If you scrape LES for all @VirMach responses in the last 446 pages, you can use a base LLM to create your own VirBot
That's tough... Hopefully they sort it out for you @VirMach
TierHive - Hourly VPS - NAT Native - /24 per customer - DE, UK, SG, CA, USA x3, FR, AU, PL, NL
FREE tokens on sign up, try before you buy. | Join us on Reddit
Heh, this one VPS had been down so long, that I forgot about a script in
cronpulling in a huge backup file every night … All of a sudden my VPS had a full root fs … (Back when I set it up, the backup required 30 GB, now it requires >40 GB …) I since bought a replacement with a larger drive, so … not sure what I should use this one for … (I do have some ideas, of course …)Migration queued
Queued for the next worker tick. This usually starts within a minute.
But it's been spinning hours...
It's been some time and my server on LAXA017 still has no connectivity. Already sent a ticket but only got AI response.
You probably saw me somewhere...
Did you update your vps network interfaces?
Virmach Deals
My server ID: https://billing.virmach.com/clientarea.php?action=productdetails&id=689285
Main IP Address: 83.147.242.217
Last Node: SJCZ012
Main Server IP: Online
Node Server: Online
Service Status: Active
I’m not sure if this will lighten your workload, but if you could migrate my server to Japan, I don’t need to retain any data; you can simply set up a blank VPS for me.
Hope to receive your reply to my message.
It’s great to see @VirMach back.
The progress of the SJC restoration/migration is no longer displayed on the network status page.
I hope @VirMach can provide some updates, given that the service has been offline for five months and the last update was several weeks ago.
Thanks.
There's up to 2 services on LAXA026, 2 on LAXA025, 1 on LAXA023, 3 on LAXA021, 5 on LAXA017, 1 on LAXA016, 1 on LAXA014, 1 on LAXA012, 12 on LAXA011, 2 on LAXA010, 2 on LAX1Z020, and 2 on LAXA006 that still need a change.
Most of these just show up because I need to rework the conflict detection system to better handle some outlier cases. I thought all of these remaining ones were bogus but after your comment I had a look and there's a very small number still incorrect. I'll go through these, credit everyone and correct them.
Is yours having this issue with the new IP or is the IP still the old IP?
There's one of them that was moving to TYOC038. In the process, it knocked out TYOC038. So I started moving TYOC038 to a new node, TYOC032. That one ran into problems. I feel like that's a good example to point to on why it's not done. Many of the others were slated to be moved to other nodes that also ran into issues. I've had to rework what's happening several times. LAX just went through renumbering in a way that did not assume we'd shift migrations for SJC, so that's been difficult to fit in. I'm definitely spending time on it every day, it's just not going well.
As for it not being on the network status page, I have no idea what happened. I can confirm it's no longer on the network status page, but on my end admin side, it is. I have a few guesses based on what's changed since then, but it's not actively being looked at right now.
Turned off to avoid potential issues as I reworked parts of the shared system for migrations. It's working better now for mass migrations, but I have to spend some time to re-test individual migration feature before turning it back on.
It's on DHCP on the same network interface and still receiving a response, so I don't need to change those.
It is on the same IP, I did not received any IP migration of some sort, only the node migration was show up ~a week ago. See ticket #688091 for the AI-assisted ticket.
You probably saw me somewhere...
@VirMach seems to have launched a feature allowing users to change their IP address.
However, as I don’t have the $3 credit
and I don’t really need it either,
I do hope the new feature works well.
I can confirm you are 1 of 5 virtual servers affected on LAXA017. That's good, it means nothing weird going on that isn't already accounted/detected.
I went ahead and corrected yours using the conflict scanner tool instead of "officially" and extended the due date manually. This just means you won't get communication for it and it won't appear in your history.