All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Racknerd shutting down Los Angeles DC02 (Multacom) location
Got this email a little while back
MOD EDIT: "Non-TL;DR" version further down below.
Our upstream colocation provider at our Los Angeles DC-02 location will be exiting their presence at the 707 Wilshire Blvd (Aon Center) building. As a result, RackNerd will be physically migrating our equipment, including all VPS hypervisors/nodes, from Los Angeles DC-02 to our Los Angeles DC-03 location at 1200 W 7th St.
Is remaining in Los Angeles DC-02 possible?
No. Our colocation provider for DC-02 is completely exiting their presence at 707 Wilshire Blvd, along with restructuring their organization. Because of this, the physical move is required.
Will my IP address change?
Yes. Since Los Angeles DC-03 uses a different upstream provider at 1200 W 7th St, IP network renumbering is unavoidable. Once the physical migration is completed and your VPS is brought back online, you will receive an email containing your new VPS IP address.
Can I keep the same IP address?
Unfortunately, no. Because the services are moving to a different facility and upstream network, keeping the existing DC-02 IP address is not possible.
Personally gonna miss that Asia optimized network and peering at Any2West.
Comments
It's migration season, isn't it?
@dustinc where is appeal process?
We need more DC. Not less!
That, and I'm going to miss native IPv6.
O no
Will Someone think of the MJJs......
i wonder how their offerings will change in terms of bandwidth and ipv6. should be interesting to map out the routing changes.
Hi All,
What was shared is correct, and the email we sent out does go into more detail than what was originally posted by OP for customers who are curious.
The provider/building situation at our Los Angeles DC-02 facility has created circumstances outside of our control, and continuing to operate infrastructure there is no longer a viable long-term option. As such, the physical move to Los Angeles DC-03 is required, though service will still be delivered and maintained within Los Angeles.
By physically migrating the existing hardware, this also allows customers to continue receiving the same hardware/resources they were originally allocated. We obviously understand the impact that any downtime can have, and this is something we have taken into account throughout the planning process. To help make this as smooth as possible, we have coordinated teams on both ends -- one at the current facility to assist with the unracking/loading process, and another at Los Angeles DC-03 ready to receive, rack, and bring services back online as quickly as possible.
While we are providing an estimated downtime window for the day, we do anticipate the actual outage to be much less than the full window. Of course, we appreciate everyone’s understanding, and our goal is to minimize downtime as much as possible for our valued customers.
Expansion has always been a focus of ours, but so has sustainable growth, customer happiness, and continuing to improve the overall experience. Feedback is always appreciated, and we do take it seriously. Personally I have been part of many physical migrations throughout my career in this industry, including multi-state migrations, and have learned a lot along the way in making these types of moves as seamless as possible. This migration should be no different, and the team and myself are approaching it with that same level of care and preparation.
Also, just to clarify, IPv6 is natively supported in our Los Angeles DC-03 location.
No pricing changes are being made as part of this migration, and our goal is to complete this as smoothly as possible for everyone involved. Since services will remain in the Los Angeles area, with the new facility being less than a mile away, most customers should not notice a difference in terms of network performance -- especially with Los Angeles DC-03 continuing to improve, including the recent addition of Lumen/Crown Castle into the network blend. That said, we are constantly looking for ways to further improve as well.
There are lots of providers with Any2West peering. The DC comparable to 707 Wilshire is One Wilshire/CoreSite LA1. CoreSite LA2 is pretty big too.
/64 and BGP session when?
One more thing I noticed in my email that wasn't shared that I think might be interesting for folks that haven't read the email yet.
Did you post an incomplete email without indicating that? Wtf for?
Good thing I don't use a known felon for hosting
He didn't miss out much of consequence tbh. But the full e-mail was:
Hello,
We are writing to provide notice of an upcoming physical migration involving services currently located in our Los Angeles DC-02 datacenter location.
This particular message is relating to your VPS service with current hostname/service label: racknerd-xxxxxx currently with the main IP address of xxx.xxx.xxx.xxx.
Our upstream colocation provider at our Los Angeles DC-02 location will be exiting their presence at the 707 Wilshire Blvd (Aon Center) building. As a result, RackNerd will be physically migrating our equipment, including all VPS hypervisors/nodes, from Los Angeles DC-02 to our Los Angeles DC-03 location at 1200 W 7th St.
This particular email is in relation to service with hostname/IP: racknerd-xxxxxx / xxx.xxx.xxx.xxx only. If you have other VPS services with RackNerd hosted on other Los Angeles DC-02 nodes that are not listed within this email, you will receive a separate notice like this one once those nodes are scheduled for migration later this month.
Maintenance Window / Expected Downtime:
Date: Thursday, May 21, 2026
Power-off begins: Approximately 6:45 AM PDT
Physical unracking begins: Approximately 7:00 AM PDT
During this maintenance, our team will safely power down the affected nodes, unrack the equipment from 707 Wilshire Blvd, transport the equipment to our Los Angeles DC-03 facility, and then rack, cable, power on, and complete the required network/IP renumbering work.
While we will be working to complete this migration as quickly and smoothly as possible, there are several physical logistics involved, including transportation, racking, cabling - along with IP address renumbering, which make an exact completion time difficult to state. We realistically expect the work to be completed before the end of the business day, but for planning purposes, please prepare for the possibility of an outage lasting the full day.
No action is required from your end, other than planning accordingly for the downtime window.
Our team has prepared the necessary staff and logistics on the ground to make this process as smooth as possible.
Frequently Asked Questions:
Is remaining in Los Angeles DC-02 possible?
No. Our colocation provider for DC-02 is completely exiting their presence at 707 Wilshire Blvd, along with restructuring their organization. Because of this, the physical move is required.
Will any data be lost?
No. This is a physical migration of our existing infrastructure from one facility to another. Your VPS data will remain on the same underlying server hardware, which is being powered down, transported, and brought back online at the new facility.
Should I take backups before the migration?
While this is a physical equipment move and we do not expect data loss, we always recommend maintaining your own off-server backups as a best practice for any production service, especially before scheduled maintenance involving physical infrastructure.
Will my VPS resources change?
No. Your VPS plan, disk, RAM, CPU allocation, and other service resources will remain the same. This is strictly a physical facility move and IP address renumbering event.
Will my IP address change?
Yes. Since Los Angeles DC-03 uses a different upstream provider at 1200 W 7th St, IP network renumbering is unavoidable. Once the physical migration is completed and your VPS is brought back online, you will receive an email containing your new VPS IP address.
Can I keep the same IP address?
Unfortunately, no. Because the services are moving to a different facility and upstream network, keeping the existing DC-02 IP address is not possible.
How can I follow live updates?
Once the maintenance begins, we will open an incident on our status page and post updates there throughout the process: https://status.racknerd.com
Please note that the status page incident is not live yet, as the maintenance has not started. It will be created once the event is actively underway.
Do I need to open a support ticket before the migration?
No action or ticket is required from your end before the migration. Our team will handle the safe shut down, physical move, power-up, and network renumbering process. We recommend only planning accordingly for the downtime window. You will receive a follow up email once your VPS is back online and ready for use.
Will my VPS password or login details change?
No. Your VPS login credentials will remain the same. Only the assigned IP address will change.
Can I receive my new IP address before the migration starts?
Unfortunately, no. Due to the nature of the renumbering process and IP allocation being finalized automatically by the system during the move, the new IP address will be provided to you via email once the VPS has been brought online at Los Angeles DC-03.
If I have multiple/additional IPv4 addresses will I receive additional replacement IPs too?
Yes. Our system will automatically detect the total number of IPv4 addresses currently assigned to your VPS, and allocate the same quantity of replacement IPv4 addresses accordingly.
Will the VPS location still be Los Angeles?
Yes, your VPS will remain in Los Angeles. The move is from our Los Angeles DC-02 location at 707 Wilshire Blvd to our new Los Angeles DC-03 location at 1200 W 7th St.
—--
We appreciate your patience and understanding as we complete this required facility migration. Our goal is to perform the work safely, carefully, and as efficiently as possible.
Regards,
RackNerd Engineering Team
[email protected]
So... No drama?
Wouldn't the IPv6 remain the same?
Hi @jcn50 -- IPv6 address(es) will also be changing as part of this process, due to the use of a different upstream allocation in Los Angeles DC-03.
Does this mean that the building where racknerd dc02 is located and the building where cloudclone la are located are not the same?
Without indicating what exactly?
TLDR version was posted, pretty sure no one at LET wants to read a wall of text
Can we manage RDNS ourselves in DC03? It’s a bit of a hassle to have to submit a ticket every time
dc03 has more better network.
The big advantage of dc02 is the Any2West routing. My isp has direct routing through any2ix.coresite.com. dc03 doesn't have that, unless something has changed recently.
+1
This is what I'm going to miss too. Any2West has tons of ISPs present.
MJJs are also going to miss the direct AS4134 connectivity
exactly that it was a tldr version, come on man.
Updated the OP to include/mention the "TL;DR" part ✌️
i hold several website on DC02, the migration will make it into trouble, and need to migrate to another server first, then move back. it's terrible
Sounds like you have a plan of attack during the downtime.
I'm curious how long ago the initial announcement email was sent to impacted clients. Someone help define with a date, "got this email a little while back."
Hi @fadedmaple -- that is certainly the goal, and something we are actively working toward. We are doing our best to get all of our ducks in a row so this process can be as smooth as possible for the upcoming transition.
That said, depending on the size of the parent block and how the IP ranges are delegated, some ranges may still need to be handled manually for now. We’ll continue working through this and improve the process where possible
I received it about 24 hours ago.
Hi @david -- we appreciate the feedback, and you are correct that different Los Angeles facilities and upstreams will naturally have different routing/network characteristics.
The good news is that 1200 W 7th St / Los Angeles DC-03 is ready to support our continued growth. As many who have followed us for some time know, our growth ability in Los Angeles DC-02 had become quite limited due to facility power constraints, and that location had already been sold out for a very long time. We have also been deploying new Los Angeles orders/nodes in DC-03 for quite a while now, so this allows us to fully focus on growth and expansion there moving forward.
With that said, we are continuously working to improve the network blend in Los Angeles DC-03 as well. Lumen/Crown Castle was recently added to the blend, and we will continue looking for ways to further improve things as we grow there too.
Only onwards and upwards from here
Hi @jasonma2026 -- we understand, and we do apologize for the inconvenience this may cause.
The good news is that our support team is very receptive and willing to help, and we are already working with customers on a case by case basis where possible. If you would prefer to be migrated to another location before the physical migration window, please reach out to our support team and we can review available options for you, stock permitting.
In short, if the goal is to avoid the physical downtime window, we may be able to migrate your VPS ahead of time to another available datacenter location. The IP address would still change as part of that process, though it would allow the migration to be completed in a more controlled manner ahead of the scheduled physical move.
That said, we are very experienced with physical migrations, and we do expect this to go smoothly. Of course, it never hurts to plan ahead, and we completely understand customers wanting to prepare on their end. On our side, we will be coordinating closely throughout the process and will work to bring services back online as quickly as possible.
We appreciate your understanding as we work through this.