@Ganonk said:
is available to change ip with same location/node ?
Here you go. For some of you in NYC on NYCB011, NYCB045, NYCB046, and NYCB047
Dear VIrMach Customers,
For services on NYCB011, NYCB045, NYCB046, and NYCB047, there will be a change in IP address tomorrow, March 24th, starting at apporoximately 8AM PST. Any specific updates on progress will be posted on the network status page. We apologize for the short notice.
What does this mean?
If your service requires an IP change, you will first see your new IP(s) appear in addition to your existing
We will update the network status page once all new IP(s) have been assigned and when new IP(s) are activated
Later in the day, we will remove the old IP(s) and reconfigure your networking
Please note, after the IP change, make sure to utilize the new IP address for any important configuration within your operating system. If you run into issues, feel free to open a ticket afte maintenance is marked as complete as we will be actively monitoring tickets. Select the "Network Status" department. If there is no IP change and we mention in the network status page that they have been changed/completed, this means your service did not require one.
Why the change?
The existing IPv4 addresses are no longer being leased to us by a third party.
Additional Maintenance:
Services on NYCB011 will also be migrated. These will be processed first, and you will see your new IPv4 when it returns back online. More details will be provided on the status page a few hours after you receive this email.
Although unlikely, we may need to move some services to a more suitable node, in which case you will likely be notified (via ticket.) The effective end results will be the same (with an IP change and data moved over.)
We were unable to utilize a new system we've developed in time for this change, but should your service require a change in the future, it will hopefully be a more seamless process with better notifications and options when possible. If you have any additional questions or feedback, let us know by creating a ticket.
Wondering if the NYC work may have borked some network configuration. NYCB018 isn't in the list of hosts on the network status page, but networking is down. VNC appears to be working. The gateway at 141.11.235.1 appears down.
@Brayvin said:
Wondering if the NYC work may have borked some network configuration. NYCB018 isn't in the list of hosts on the network status page, but networking is down. VNC appears to be working. The gateway at 141.11.235.1 appears down.
141.11.235.1 looks up to me. Just saying.
4 ae-2.r22.nwrknj03.us.bb.gin.ntt.net (129.250.3.174) 3.512 ms 3.490 ms 3.462 ms
5 ae-0.a01.nwrknj03.us.bb.gin.ntt.net (129.250.2.97) 3.530 ms 3.510 ms 3.516 ms
6 e0-16.cr1.nyc2.us.unitasglobal.net (50.115.91.10) 4.064 ms 5.070 ms 5.275 ms
7 e0-40.cr1.nyc1.us.unitasglobal.net (50.115.90.134) 4.829 ms * *
8 inap.cust.nyc1.us.unitasglobal.net (198.232.115.146) 3.642 ms 3.780 ms 3.744 ms
9 border1-po2-bbnet2.nyj004.us.unitasglobal.net (216.52.95.109) 4.442 ms border1-po1-bbnet1.nyj004.us.unitasglobal.net (216.52.95.46) 4.667 ms 4.639 ms
10 74.201.136.182 (74.201.136.182) 4.517 ms 4.397 ms 4.364 ms
11 hosted-by.royalehosting.net (45.59.169.177) 23.207 ms 23.124 ms 83.339 ms
12 141.11.235.1 (141.11.235.1) 5.974 ms 5.930 ms 5.891 ms
@Brayvin said:
Wondering if the NYC work may have borked some network configuration. NYCB018 isn't in the list of hosts on the network status page, but networking is down. VNC appears to be working. The gateway at 141.11.235.1 appears down.
141.11.235.1 looks up to me. Just saying.
Yes, I neglected to mention that it seems down from the VPS point of view.
@Brayvin said:
Wondering if the NYC work may have borked some network configuration. NYCB018 isn't in the list of hosts on the network status page, but networking is down. VNC appears to be working. The gateway at 141.11.235.1 appears down.
141.11.235.1 looks up to me. Just saying.
Yes, I neglected to mention that it seems down from the VPS point of view.
Don't be afraid to make a ticket. We usually say to please not make one but this time around I went out of my way to insist on tickets being made and it was with good reason -- this was a huge mess to complete.
I've already located your issue by looking at some data reports, one moment.
(edit) Yours was one of these:
A few services ran into problems (approximately 12~) and need to be migrated again or moved to another server due to high IPv4 requirements
I made space for you to stay as you didn't have a high quantity of IPs and I wanted to avoid a second migration where possible, but then forgot to take you off the list to move, so when it was moved, the IP wasn't changed because it didn't match the subnet being processed for all the moves. Sorry about that, this took much longer than expected due to issues with the control panel and other (expected) complications and this was at the very end so I'm not firing on all cylinders right now. It's on NYCB018, with the right IP now.
Comments
Oh but he is as with all politicians it is on the backside!!!
Free Hosting at YetiNode | MicroNode | Cryptid Security | URL Shortener | LaunchVPS | ExtraVM | Host-C | In the Node, or Out of the Loop?
Does that mean you get VPS Escorts?
Just get me Tunnel Broker to work in LAX. Use your political voodoo!
is available to change ip with same location/node ?
@VirMach, would you at least respond to Ticket #401962? It's been sitting there for a month and a half.
I'll be happy if you clear that matter.
Here you go. For some of you in NYC on NYCB011, NYCB045, NYCB046, and NYCB047
@FrankZ convinced Virmach to make all the changes before April
Vacation time comes
blog | exploring visually |
nice
Wondering if the NYC work may have borked some network configuration. NYCB018 isn't in the list of hosts on the network status page, but networking is down. VNC appears to be working. The gateway at 141.11.235.1 appears down.
141.11.235.1 looks up to me. Just saying.
Yes, I neglected to mention that it seems down from the VPS point of view.
Don't be afraid to make a ticket. We usually say to please not make one but this time around I went out of my way to insist on tickets being made and it was with good reason -- this was a huge mess to complete.
I've already located your issue by looking at some data reports, one moment.
(edit) Yours was one of these:
I made space for you to stay as you didn't have a high quantity of IPs and I wanted to avoid a second migration where possible, but then forgot to take you off the list to move, so when it was moved, the IP wasn't changed because it didn't match the subnet being processed for all the moves. Sorry about that, this took much longer than expected due to issues with the control panel and other (expected) complications and this was at the very end so I'm not firing on all cylinders right now. It's on NYCB018, with the right IP now.