LowEndBox - Cheap VPS, Hosting and Dedicated Server Deals

Multacom Sued by Aon Center Landlord Over $401,128 in Alleged Unpaid Rent

MultacomLowEndBox readers may be familiar with the name Multacom. More likely, you’ve encountered them indirectly, because Multacom has long been one of those Los Angeles datacenter/provider names sitting behind other hosting companies.

In other words, you may not have bought anything from Multacom directly. But your host in Los Angeles may be a downstream customer of Multacom.

A complaint filed by the owners of 707 Wilshire Boulevard (known as the Aon Center in downtown Los Angeles) alleges that Multacom Corporation owes $401,128.25 in unpaid rent, utility charges, CAM charges, taxes, and other lease related amounts.

You can read the full complaint HERE.

Multacom is/was been used by downstream hosting companies over the years, such as RackNerd, CloudCone, and HostNamaste to name a few (more on that below).

Los Angeles has seen this kind of issue before. Last year, users on LowEndTalk discussed a major outage at QuadraNet’s Los Angeles datacenter, with services reportedly offline for over five days and little clarity at first as to the root cause or resolution timeline. It turns out they were over $600,000 in past due rent. QuadraNet ended up shutting down abruptly, and customers had one week to get their equipment out.

At this stage, this is only a complaint. Multacom may dispute the allegations, settle the matter, pay the amount claimed, or otherwise resolve it. There is no indication from the complaint alone that services are currently offline.

Multacom’s Downstream Customers

Speaking of downstream customers, RackNerd (a name you may be familiar with) was one of the larger community providers with equipment in Multacom’s Los Angeles facility. 

As covered on LowEndTalk, RackNerd recently completed a large migration out of Multacom’s LA footprint and into its new space at West 7 Center, 1200 W 7th St. Dustin Cisneros, CEO of RackNerd, stated:

“The provider/building situation at our Los Angeles DC-02 facility [Multacom] 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.”

At the time, some customers were not happy. That is not surprising. Datacenter migrations are disruptive, and IP changes can be annoying.

But in light of this complaint, the timing is notable. Did RackNerd see something coming that other downstreams did not, and just save their customers from a potentially much worse situation? Maybe. At minimum, it looks like they were paying attention to facility-level risk and decided to act before that risk could turn into a customer-impacting emergency.

If they saw long-term risk, moving out before end users were caught in the crossfire of a larger facility issue would make sense, because large migrations are rarely appreciated while they are happening. Customers see maintenance windows, IP changes, and support tickets. The risk being avoided is usually much less visible and more of an afterthought.

There may be other downstream movement as well, and this one is worth mentioning because it is not just a random downstream provider. Edge Centres acquired Multacom in 2023, and later acquired CloudCone in 2024, so there is common ownership in the background. CloudCone has recently also notified customers of an IPv4 renumbering process, stating:

“Our datacenter has informed us of an IPv4 re-numbering process that will result in a change of your VPS, SC2 and Dedicated server IPv4 addresses.”

That does not necessarily mean CloudCone is physically moving out of Multacom. It may only be an IPv4 renumbering event. But in context, it is another data point worth watching. When a facility/provider is involved in a lease dispute and downstream customers are also being told to renumber IPs, people are naturally going to connect those dots, even if the full explanation is not yet public.

CloudCone has also been the subject of recent LowEndTalk complaints around delayed affiliate payouts. In one thread, LowEndTalk user @NodeSuper wrote:

“About a month ago, I requested a withdrawal of the affiliate commissions I’d earned through hard work to my PayPal account. They promised payment within 7–14 days, but it’s been over a month now, and when I messaged them again, no one responded!”

He also claimed CloudCone told him to “continue waiting for service” and then closed the ticket.

Another LowEndTalk user, @walock, later posted:

“I am in the exact same boat here. I requested my affiliate withdrawal ($149.397 via PayPal) over a month ago. My support ticket hasn’t received any meaningful updates either and has been left sitting there.”

@NodeSuper later updated the thread to say CloudCone had responded and paid the commission, though a couple others reported still not receiving payment to this day.

So is this directly related to Multacom’s landlord dispute? Maybe not. But when Edge Centres owns both Multacom and CloudCone, CloudCone customers are receiving datacenter-driven IPv4 renumbering notices, and LET users are separately reporting delayed payout issues, that is at least something worth paying attention to.

This complaint does not prove that Multacom is going away, nor does it prove that customers are in immediate danger. But $400k+ in alleged unpaid rent is a significant amount, and always a good reminder to check on the status of your backups.

1 Comment

  1. Mitesh - HostNamaste.com's avatar

    We only had a few older servers with them in LA, mainly long-term deployments with legacy IP allocations.

    Back in March, Multacom had already informed us that they were restructuring operations around their 707 location and planned to move infrastructure to their 600 W. 7th Street datacenter space. We received a scheduled migration notice from them in advance and coordinated accordingly.

    During that period, we proactively migrated our servers and IP allocations as well, so currently we do not have any production dependency there. The migration itself was handled quite smoothly and involved only minimal downtime from our side.

    At the moment, the servers/IPs still continue operating under the same Multacom naming/routing, so technically things appeared stable during the transition.

    So when I saw the article today, it looked like some of the operational changes and restructuring activity had already been underway internally for some time earlier this year.

    May 28, 2026 @ 8:25 am | Reply

Leave a Reply

Some notes on commenting on LowEndBox:

  • Do not use LowEndBox for support issues. Go to your hosting provider and issue a ticket there. Coming here saying "my VPS is down, what do I do?!" will only have your comments removed.
  • Akismet is used for spam detection. Some comments may be held temporarily for manual approval.
  • Use <pre>...</pre> to quote the output from your terminal/console, or consider using a pastebin service.

Your email address will not be published. Required fields are marked *