Summary

  • hosting.com MEX1 is best understood as a hosting.com network and platform surface, not as a standalone company created by an ASN or a Mexico location label. The relevant commercial counterparty for customers is hosting.com, with public legal pages saying A2 Hosting, LLC trades as hosting.com, while UK company records and RIPE data show WHG Hosting Services Ltd in the wider group.
  • The service evidence supports Cloud Service and Cloud Service Dependency treatment: hosting.com sells recurring shared hosting, managed WordPress, VPS, reseller, server, email, domain and migration services, with renewal pricing, support terms, backup limits, automatic renewal rules and maintenance policy all affecting customer continuity.
  • The MEX1 network evidence is useful but bounded. PeeringDB lists hosting.com MEX1 as AS211126 with a KIO Mexico 2 facility entry, while bgp.tools shows WHG-MEX as an active RIPE ASN with five IPv4 /24s and Arelion/GTT upstreams. That proves a routed operating surface; it does not prove application uptime, ticket quality, migration success or customer retention.
  • The central risk is contract migration under consolidation. hosting.com's own Contract Migration FAQ says services will be provided by A2 Hosting LLC from the next renewal under the consolidated platform, with future invoices reflecting updated entity details, currency and tax treatment. That makes renewal a governance event for customers whose websites, email, DNS, backups and client obligations are tied to the account.

The renewal moment

The practical starting point is an ordinary hosting renewal notice. A customer who signed up with A2 Hosting for a discounted managed WordPress, cPanel, VPS or server account now meets the brand as hosting.com. The website may still work, the control panel may still be reachable, the nameservers may still answer and the invoice may still describe familiar hosting services. Yet the renewal decision has changed because the account now sits inside a larger consolidation story.

hosting.com says in its Contract Migration FAQs that, from the next service renewal date, services will be provided by A2 Hosting LLC, which operates the consolidated global platform at hosting.com. The same FAQ says existing services, pricing and support arrangements continue without change, while future invoices from the next renewal reflect updated entity details, currency and applicable tax treatment. It also says continued use after renewal constitutes acknowledgement and acceptance of the updated contracting arrangement.

That wording matters more than a map pin. Server location still affects latency, jurisdiction, support expectations and data movement. But for a small business, agency or developer with client sites on the account, the larger dependency is the bundle of contract, billing, support and operational promises around the hosted application. A renewal may keep the same WordPress site online, but it can also lock the customer into a changed set of terms, payment timing, cancellation assumptions and escalation routes.

The hosting.com MEX1 label should therefore not be read as a new company. MEX1 is a network and location marker tied to AS211126 and a Mexico facility record. It is not evidence that there is a separate Mexican hosting firm behind the public offer. The company-facing evidence points to hosting.com as the brand, A2 Hosting, LLC as the stated operating company for public policies, and WHG Hosting Services Ltd as a UK group entity appearing in Companies House and RIPE records. Those pieces must be kept distinct because a customer complaint, renewal dispute or migration incident will not be solved by knowing an ASN name alone.

The article's judgment is also deliberately narrower than a hosting review. Public offer pages establish what hosting.com sells and what obligations the bundle creates. Network databases establish a routed footprint and upstream dependencies. Review sites and forums reveal sentiment and possible friction. None of these sources prove uptime for a particular account, support quality for a particular incident, the actual speed of a customer's application, or the retention rate of legacy A2 Hosting customers.

What the customer is actually buying

hosting.com's public product surface is broad enough to support Cloud Service treatment. The main hosting page offers shared plans with cPanel, NVMe storage, LiteSpeed caching, unlimited MariaDB databases, malware protection, SSL and a 99.9 percent uptime SLA claim. Its plan comparison describes tiers from Starter through Max, with different website counts, disk space, memory, vCPU, IOPS, mailboxes and email limits. It also states that the company offers free website migration, a 30-day money-back guarantee for covered products, Monarx security, a free domain with select plans and managed WordPress plans powered by Cloudflare Enterprise.

That is not just brochure language. It defines the paid unit. The customer's recurring account is not simply "space on a server"; it is a managed bundle of storage, control-panel access, email, DNS, SSL, security tooling, backups, support and renewal rights. The dependency begins when a production website, client email or ecommerce process assumes those components will continue to operate together.

The managed WordPress page makes the same point more explicitly. It markets AMD EPYC CPUs, Cloudflare Enterprise, free SSL, CDN, malware protection, website firewall, plan-dependent WP Rocket and Object Cache Pro, 24/7 expert support and unlimited free migrations. It describes Cloudflare Enterprise CDN and WAF as included, and the FAQ says all plans provide 24/7/365 support through live chat and ticketing, with WordPress-specialist support engineers. For a WordPress customer, the purchased service is therefore a hosted application environment plus a support promise, not just a virtual machine.

VPS products split the dependency by responsibility. The VPS page distinguishes managed VPS hosting, where CloudLinux, cPanel, backups, security configuration and operating-system updates are handled for the customer, from unmanaged VPS hosting, where the customer controls the operating system, security and backup settings. The unmanaged VPS page says customers choose from Linux distributions, receive full root access, can add cPanel, CloudLinux, LiteSpeed and Imunify360, and get infrastructure support while managing server software and configuration themselves. It also says unmanaged VPS plans do not include backups and that VPS plans are not covered by the money-back guarantee.

That division is important for renewal analysis. A shared or managed WordPress account makes hosting.com responsible for more of the operational layer. An unmanaged VPS gives the customer more control but also shifts patching, application configuration, backups and restore testing to the customer. A managed VPS sits in the middle. It reduces sysadmin work but may deepen dependence on cPanel licensing, CloudLinux, hosting.com's support queue and the provider's maintenance windows.

Dedicated and managed server products add another step in commitment. The unmanaged VPS page routes heavier workloads toward managed VDS and dedicated servers, describing dedicated servers as raw hardware control without neighbours. Those products are not equivalent to commodity shared hosting. They are closer to a private operational surface where migration may require image planning, IP changes, licensing review, DNS cutover, backup restore tests and application-level acceptance testing.

The customer-facing evidence therefore supports a cloud-service profile because hosting.com sells hosted infrastructure and managed service bundles with continuing operational obligations. It does not support a Regional ISP profile. The first paid unit is not last-mile access, installation, voice, field response or connectivity tariff. The relevant customer buys hosting, platform management and support, while the network footprint helps explain how that service is delivered.

Introductory price is not the same as renewal economics

The commercial hinge is the gap between introductory and renewal pricing. hosting.com's renewal pricing page explains the model plainly: the company offers promotional prices throughout the year, including savings for customers who pay one, two or three years in advance, and after the prepaid period ends the website plans renew at regular pricing. The public plan pages have shown examples such as a low first-year shared-hosting price followed by a higher renewal amount, and the VPS pages state that promotional prices for 12-month terms renew at the regular rate at the end of the introductory term.

That does not make the pricing unusual in web hosting. It does make renewal the proper moment for comparison. A small site owner might have bought the account because the first term looked cheaper than alternatives. By the renewal date, the customer is comparing a higher recurring rate against the cost of migration, the value of support, the risk of email disruption and the time needed to retest the application somewhere else.

The refund and billing policy makes this sharper. It says hosting plans and domains are set to automatic renewal after the initial term and renewal terms to prevent service disruption. It also says the initial renewal date appears at checkout, later renewal dates appear in invoices and the client portal, and customers receive an invoice in advance with the duration and price of the upcoming renewal term. For package renewals, fees are due on the renewal date, and the policy says invoices are generated 14 days before renewal and may be charged three days before the due date for continuity.

The same billing policy says accounts with overdue invoices may be suspended at any time, and accounts more than three days overdue are considered abandoned and may be subject to termination, including removal of associated data. That is standard continuity logic for a hosting provider, but it means the customer has limited time to resolve billing or migration decisions once a renewal invoice is active.

Domain handling is another continuity point. The billing policy says domain names are set to automatically renew five days before their due date to avoid expiry disruption, and cancellation must occur more than five days before the due date if the payment method can be charged automatically. A customer who uses hosting.com for both hosting and domains therefore needs to separate website hosting renewal, domain renewal, DNS authority and email continuity before changing providers.

The money-back promise is narrower than the marketing line might suggest. The money-back guarantee page says the 30-day guarantee covers shared hosting, WordPress hosting, reseller hosting and some email hosting purchased directly from hosting.com. It excludes domain registrations, renewals and transfers, VPS plans, dedicated servers, SSL certificates and third-party products such as Microsoft 365. A customer renewing a VPS, dedicated server or domain-heavy bundle should not treat the 30-day policy as a universal escape hatch.

This is where hosting.com competes not only with other hosting brands but with different operating models. A customer can choose a low-touch shared plan, a managed WordPress specialist, a cloud VPS from DigitalOcean, Hetzner or OVHcloud, a managed layer such as Cloudways, a hyperscaler bundle such as AWS Lightsail, or self-managed infrastructure. The cheapest monthly figure rarely includes the same amount of support labour, migration help, backup retention, security tooling or control-panel licensing. The right comparison is total switching cost plus recurring run cost, not the home-page price alone.

Support labour is part of the product

For many customers, support labour is the product. A hosting account is tolerable when someone answers during an outage, helps with cPanel, explains DNS and moves a site without losing email. It becomes fragile when a customer must coordinate nameservers, MX records, control-panel migration, SSL issuance and backup restore without reliable escalation.

hosting.com's support policy states that technical support tickets, phone calls and LiveChat are included as part of the service, and that urgent service interruptions should be raised immediately through live chat. It also says the company may call back if the customer provides a number or use the phone number associated with the account. The policy asks customers to back up all data before troubleshooting and says hosting.com is not responsible for data loss or corruption caused by authorized actions, customer actions, hardware failures or software and technology failures.

The public site emphasizes that support is available around the clock. The UK home page says real people are ready 24/7/365 and lists an average chat response time and customer satisfaction metrics for Q3 2026. The managed WordPress page says support engineers are WordPress experts and that plans have live chat and ticketing. The main hosting page says in-house engineers are available through live chat, phone and tickets.

The migration page is more operationally specific. The free website migration page says hosting.com can copy website files, databases, emails and domains where included, set up the destination account, test before DNS switch and support WordPress, cPanel, custom CMS and HTML sites. It says most sites migrate within one to four hours after access is provided, larger or more complex setups may take one to two business days, and DNS propagation can take 48 to 72 hours after final switch. It also says compatible sites on shared and managed WordPress hosting can migrate free, while rare legacy site-builder cases may require custom services.

That evidence supports the "Local Support Labour" dimension in a practical sense, even if the support team is global rather than local to MEX1. The important labour is implementation, troubleshooting, escalation and migration support. A provider can advertise modern hardware and routed prefixes, but a small agency renewal decision often turns on whether the support team can move a WooCommerce site, preserve mailboxes, avoid DNS confusion and explain where cPanel lives after a platform change.

Unofficial signals show why that labour matters. On Reddit's r/webhosting rebrand thread, some users discussed cPanel confusion, changed plan details and slower ticket responses after the rebrand, while a hosting.com representative replied to some comments and described product changes and support efforts. On another Reddit renewal thread, a user described moving from a discounted managed WordPress plan to a much higher renewal and weighed whether the new annual price made sense relative to managed WordPress alternatives. These are anecdotes, not statistically reliable service measurements, but they show the customer problems that arise when renewal, rebrand and application continuity meet.

Trustpilot points in a different direction. The hosting.com Trustpilot profile showed a 4.7 score from more than 6,000 reviews on July 10, 2026, with a high proportion of five-star reviews and a company profile that says reviews were merged after rebranding or ownership changes. Trustpilot's own notice says it does not fact-check specific claims, and many reviews are invited. The profile is still relevant because it shows current customer sentiment and response behaviour, but it should not be used as proof that any particular migration, server or support queue performs well.

The balanced view is simple: support labour is visible, marketed and contractually described, but service quality remains account-specific. A customer should test the actual escalation path before renewal if the hosted workload is important. That means confirming backup access, control-panel access, emergency contacts, support ticket history, renewal dates, DNS authority and export options before the invoice forces a rushed decision.

The network evidence: useful, strong, but not decisive

The MEX1 label has meaningful network evidence. PeeringDB's AS211126 page lists "hosting.com MEX1" under the hosting.com organization, with ASN 211126, RIR status ok, IPv4 and IPv6 support flags, and an interconnection facility entry at KIO Mexico 2 (MEX2) in Cuajimalpa de Morelos, Mexico. It shows no public exchange rows in the unauthenticated view and marks the facility entry operational.

bgp.tools for AS211126 identifies the network as WHG Hosting Services Ltd, AS number 211126, registered under RIPE, active, allocated, and of type Content. It lists five originated IPv4 /24s and no IPv6 prefixes, with upstreams Arelion and GTT. Its embedded RIPE data shows the AS name WHG-MEX, the organisation ORG-WHSL1-RIPE, country GB, status assigned, creation in June 2021 and last modification in January 2025 for the aut-num object. The page was updated in July 2026.

This is strong network-resource evidence because the ASN is active, has visible announcements and is tied to a named hosting group and facility label. It supports operating-surface analysis: hosting.com has a network-facing point associated with Mexico infrastructure and upstream transit. It also supports entity-boundary analysis: the AS name and location label do not create a separate company.

The wider A2/hosting.com network is materially larger. PeeringDB's AS55293 page lists hosting.com, ASN 55293, IRR set AS-A2HOST, 50 IPv4 prefixes, three IPv6 prefixes, 10-20Gbps traffic, mostly outbound ratio, regional scope and an open peering policy. It shows exchange entries including DET-iX, Ninja-IX Phoenix and SGIX in the visible rows. bgp.tools for AS55293 lists A2 Hosting, Inc. as a long-running BGP network with numerous prefixes and upstreams Arelion, Cogent and Lumen. The embedded ARIN data on that page identifies A2 Hosting, Inc. with an Ann Arbor, Michigan postal record and an updated ARIN organisation date in 2026.

The contrast matters. AS55293 is the legacy A2 Hosting routed surface. AS211126 is the WHG-MEX surface associated with hosting.com MEX1. They are related through brand and group consolidation, but they should not be collapsed into one undifferentiated "network". A website hosted under a managed WordPress plan may use Cloudflare, a shared server, a cPanel host, a reseller layer, a Mexico point of presence, or none of the MEX1 prefixes at all. Public AS data can say that these networks exist and are routed. It cannot say where a specific customer's application is served or whether the application performs well.

The network supplier picture is also mixed. MEX1's public upstreams are Arelion and GTT. AS55293's visible upstreams include Arelion, Cogent and Lumen. The managed WordPress product depends on Cloudflare Enterprise for CDN and WAF functions. The shared and server stack mentions LiteSpeed, Monarx, CloudLinux, cPanel and Imunify360 in different product contexts. The facility evidence points to KIO Mexico 2 for MEX1. This is a layered supply chain: transit, facility, control panel, security services, CDN, backups, operating systems and support tooling all contribute to the customer experience.

That layering is why the network evidence should be graded as strong-service-provisional. Strong, because the routed resources and facility records are current and meaningful. Provisional, because a customer outcome depends on the application, account type, support response, data location, caching path, DNS setup, backup state and whether the migration was tested.

Consolidation changes the control surface

The ownership story explains why contract migration has become central. A2 Hosting was long associated with Ann Arbor and founder Bryan Muthig. The hosting.com about page says A2 Hosting was founded in Ann Arbor, Michigan, and that World Host Group later became part of the same story. A WordPress community profile described A2 Hosting as founded in 2003 by Bryan Muthig and as a developer-friendly hosting provider for WordPress professionals and businesses.

On January 29, 2025, World Host Group announced through PR Newswire that it had acquired A2 Hosting. The announcement described World Host Group as a fast-growing hosting leader with more than 25 brand acquisitions. hosting.com's own mergers and acquisitions page lists A2 Hosting as a 2025 acquisition and says it brought high-performance infrastructure and a loyal WordPress and developer customer base. It also lists FastComet as a 2025 acquisition.

The rebrand followed quickly. In April 2025, hosting.com published A new chapter begins, announcing that A2 Hosting was now hosting.com. Market coverage at the time noted the same move and discussed the reported domain purchase. The precise purchase price is less important to customers than the intent: a long-running A2 brand was being absorbed into a broader hosting.com platform.

The group structure has multiple public signals. Companies House lists WHG Hosting Services Ltd as an active private limited company in England, incorporated on February 6, 2023, with the nature of business "activities of head offices". Oakley Capital's hosting.com portfolio page says Oakley agreed a transformative merger of Webcentral and World Host Group in 2024, creating a leading hosting and domains platform, and says the business operates in 181 countries with more than 430,000 customers globally. hosting.com's own newer materials claim more than 3 million sites, and a 2026 product announcement described a global platform with more than 700,000 customers, 20-plus data centers, more than 900 team members and 11 offices.

These scale claims are not identical because they refer to different dates, measures and parts of the group: customers, sites, services, countries, locations and data centers are not interchangeable. The direction, however, is consistent. hosting.com is a consolidation platform. It has acquired, merged or rebranded assets and now seeks to present a global hosting brand across local markets.

Consolidation can improve a host. It can bring new hardware, a wider data-center footprint, better procurement, more security tooling, better product design and deeper support capacity. hosting.com's about page says the platform has 10 global locations and data centers with redundant power, cooling and connectivity, and its leadership profiles name executives for operations, infrastructure, product, finance and people. A behind-the-tech article said A2 previously had four global data centers and that customers gained access to a wider set of points of presence after joining the group.

Consolidation can also create friction. It can change client portals, billing systems, plan names, license allocations, product limits, support queues and renewal economics. In hosting, those frictions appear quickly because the customer depends on daily operational continuity. A changed login path, lost auto-renewal setting, delayed ticket or plan comparison ambiguity is not merely an annoyance when the account hosts client sites and email.

This is why the contract migration FAQ is the most consequential source for the article's thesis. It turns a brand story into a renewal event. A customer can like the old A2 service, accept the hosting.com brand and still need to review the new contracting arrangement before renewal.

Backups, maintenance and customer responsibility

The backup and maintenance language is where dependency becomes concrete. The service terms say hosting accounts are allocated bandwidth depending on the package selected, and that an account may be suspended, upgraded, terminated or charged for overage in the provider's discretion if bandwidth exceeds the purchased amount. They also say primary IP addresses are provided as part of the service cost and may be changed with email notice.

The same terms set resource limits. Shared web hosting accounts are allowed a maximum of 600,000 inodes and 35 concurrent HTTP connections to the server, while VPS hosting accounts are allowed a maximum of 2 million inodes. For shared, reseller, managed and core managed hosting accounts, backups older than 30 days may be removed from the server at the provider's discretion. That means a customer should not treat provider-side backups as an indefinite archive.

The server maintenance policy says hosting.com targets 99.9 percent uptime and uses commercially reasonable efforts to provide service 24/7, while also saying scheduled downtime, emergency maintenance and causes beyond the provider's control may make services unavailable. Routine maintenance does not require advance notice, scheduled maintenance is generally announced through the status page where possible, and emergency maintenance may occur without prior notice. The policy also says customers are solely responsible for maintaining adequate and up-to-date backups of their data.

These terms are not unusual for hosting. They are still operationally important because they set the boundaries of customer reliance. A customer who needs low recovery-point objectives, strict change windows or contractual service credits should not assume those needs are covered by a general shared hosting plan. A customer running ecommerce, client email or an agency portfolio should know whether they have independent backups, exportable mailboxes, DNS records outside the hosting account, a current database dump and a tested restore path.

The migration promise should also be read with application-specific caution. hosting.com says it can move compatible sites, test before DNS switch and keep sites live while copying data. That is reassuring for standard WordPress or cPanel moves. It does not remove the need to check custom plugins, cron jobs, PHP versions, external SMTP, payment callbacks, hard-coded paths, DNS TTLs, CDN rules, object cache, staging credentials and post-cutover mail delivery.

In practical terms, a renewal decision should start with a continuity inventory. List the domains, DNS zones, MX records, SSL certificates, databases, applications, mailboxes, backups, cron jobs, API integrations, control-panel users and billing contacts tied to the account. Then decide whether hosting.com's support and pricing justify keeping the bundle together, or whether the customer should separate domain registration, DNS, email and hosting before the next renewal.

Substitutes: cheaper hosting is not always cheaper continuity

The substitute set is wide. At the low-cost shared end, Hostinger's pricing page has advertised web hosting from $2.99 per month with a 48-month term and a higher renewal rate, plus websites, SSD storage, weekly backups, CDN, email boxes, global data centers and migration. OVHcloud's web hosting page has shown entry web hosting with low introductory prices, renewal prices disclosed beside the plans, included email, SSL, anti-DDoS, backups and 99.9 percent observed availability. GoDaddy's web hosting page has advertised managed WordPress and cPanel web-hosting tiers with long first-term discounts, 99.9 percent uptime language and included SSL.

Those are real substitutes for a price-sensitive shared customer. They may not be equivalent substitutes for an agency with many client sites, a cPanel routine, a support history and a need for migration help. A lower sticker price can become a higher project cost if it requires manual mail migration, DNS repair, plugin fixes or client downtime.

For self-managed infrastructure, DigitalOcean Droplets start at low monthly rates and moved to per-second billing from January 1, 2026. Amazon Lightsail pricing lists fixed monthly VPS-style bundles, including low-cost Linux instances with SSD storage and transfer allowance. Hetzner Cloud is a strong European cost alternative, although Hetzner also announced 2026 price adjustments for some server products. OVHcloud VPS offers VPS tiers with daily backup of the previous 24 hours and unlimited traffic language.

These options can be cheaper and more controllable for developers. They also shift responsibility. A customer leaving managed hosting for a raw VPS must handle patching, firewalling, backups, monitoring, mail deliverability, web server tuning, database security, restore tests and incident response. The real substitute for a managed cPanel or WordPress account may be a VPS plus paid admin time, not the VPS alone.

Managed cloud layers sit between those models. Cloudways pricing starts at managed cloud plans on underlying providers such as DigitalOcean, Vultr, Linode, AWS and Google Cloud, with pay-as-you-go pricing. Cloudways can appeal to customers who want managed application hosting without running a server directly, but it remains a management layer on top of another infrastructure provider, with its own portability and pricing questions.

Managed WordPress specialists are a different comparison. Kinsta's pricing page and WP Engine's plans start around the higher managed WordPress tier, usually with stronger WordPress-specific tooling, support claims and staging practices. They may be better substitutes for a revenue site than a low-cost shared plan, but they can be more expensive for hobby sites or small portfolios. They also use their own platform assumptions, caching layers and plugin restrictions.

The renewal question is therefore not "is hosting.com cheaper than every alternative?" It is "which part of the bundle does the customer actually value?" If the value is cPanel familiarity, live support, free migration and a single invoice, hosting.com can remain rational even after a higher renewal. If the value is predictable infrastructure cost and full control, DigitalOcean, Hetzner, OVHcloud or Lightsail may be better. If the value is WordPress-specialist operations and agency needs, Cloudways, Kinsta, WP Engine or Rocket.net-style managed platforms become the relevant comparison.

Market signals and what would change the judgment

The strongest public case for hosting.com is breadth. It has current hosting, WordPress, VPS, migration, support, billing, legal, maintenance and network evidence. It has a legacy A2 Hosting footprint, a larger hosting.com consolidation story and active routed resources. It also has visible customer-review volume and public staff responses on some forums. That is enough to treat the entity as an operating Cloud Service provider rather than a stale directory listing or a mere ASN record.

The strongest caution is transition risk. Public sources show a rapid sequence: World Host Group acquisition in January 2025, A2 Hosting rebrand in April 2025, contract migration language for renewal, product pages with plan and pricing changes, and wider group consolidation. That does not prove service decline. It does mean the user experience of legacy customers can be affected by changes outside their server: billing, portal, plan names, support routing, renewal amounts, invoice currency and product entitlements.

The unofficial signals reinforce the same watchpoint. Reddit comments are not audited customer data, but they identify the frictions customers care about: price rises, ticket delays, cPanel access, lost or changed auto-renewal settings and uncertainty about whether old plan features survive under new plan names. Hacker News had a small thread noting platform and pricing changes. Trustpilot is strongly positive overall, but its profile-merging note and invited-review mix mean it should be read as sentiment, not a service-level audit.

Several facts would change the judgement materially. The first is a clear public migration report from hosting.com showing how many A2 accounts moved, what incidents occurred, how ticket response times changed and what remediation was provided. The second is product-level renewal transparency showing all introductory and renewal rates in a stable table, including legacy plan mapping. The third is independent uptime and support data for shared, managed WordPress, VPS and dedicated segments separately. The fourth is clearer data-center mapping that tells customers where each plan can be placed and how Cloudflare, Anycast DNS, origin hosting and MEX1 relate to one another.

Another material change would be stronger account portability. If hosting.com offered clear export tooling for full cPanel backups, mailboxes, DNS zones, invoices, support history and site staging, contract migration would feel less like lock-in. If portability is uncertain, customers should reduce dependency by keeping domains, DNS, offsite backups and documentation under their own control.

The final judgement is measured. hosting.com MEX1 has enough public service and network evidence to be treated as a live hosting.com operating surface. The MEX1 label is useful for mapping the network, not for defining a separate business. For customers, the renewal after the A2-to-hosting.com transition is more consequential than the server-location label because it is the point where contract, price, support and portability all meet. A customer can choose to stay, but should do so deliberately: know the renewal price, know the billing entity, know what support covers, know what backups are independent, and know how the site would leave if the next migration had to happen under pressure.