Summary
- Hosted Advantage Services Ltd. is publicly visible as a Vancouver-area data-centre, colocation and managed-services provider. Its about page describes an enterprise data-centre, colocation and managed-services provider based in Vancouver, British Columbia, while its contact page lists a Vancouver office, phone number and
[email protected]. - The company claims a real physical service surface. Its data-centre services page describes colocation, remote hands, high-speed connectivity, inter-data-centre connectivity across Vancouver, Montreal, Ottawa and Toronto, and support for power, cooling and relocation tasks. Its hosted and managed services page describes servers, storage, firewalls, monitoring, patching, upgrades, remote backup and business continuance.
- Independent network evidence supports the infrastructure classification. ARIN's AS398362 RDAP record identifies
HOSTEDADV-001, and RIPEstat's AS overview marks AS398362 as announced. RIPEstat routing status shows four visible IPv4 announcements, 1,536 IPv4 addresses, full IPv4 RIS visibility in the checked view, two observed neighbours and no visible AS398362 IPv6 announcements on 12 July 2026. - The network evidence is not perfect. RIPEstat announced prefixes lists 38.88.73.0/24, 38.88.120.0/24, 38.22.68.0/22 and 38.22.68.0/24; RPKI validation for 38.22.68.0/22, 38.88.120.0/24 and 38.88.73.0/24 all return unknown in the checked public view.
- The evidence grade is Medium. Hosted Advantage has public service pages, a named Canadian office, ARIN-backed identity, active routing, two observed upstream neighbours and a data-centre operations job posting. The downgrade is for missing public rack ownership detail, no public PeeringDB profile, RPKI unknown on the visible IPv4 routes, no visible IPv6 routing, and limited public proof of tested failover, backup restores, data export or customer migration terms.
A real provider, but not a self-proving platform
Hosted Advantage Services Ltd. is not a shell-like name that appears only in routing databases. The company has a public site, a service menu, a Canadian contact page, named executives, an ARIN record and active BGP visibility. That is a much stronger starting point than the thin resource-holder profiles often found in the lower end of the hosting market. The company's own pages speak the language of data-centre operations: colocation, secure cabinets, remote hands, long-haul and metro fibre, high-speed internet, infrastructure hosting, managed support, backups, business continuance, rentals and consulting.
The article therefore should not ask whether Hosted Advantage exists. It should ask what dependency a customer accepts when it uses Hosted Advantage rather than buying space, network service and hardware directly. In practice, a Hosted Advantage customer may be moving some mix of servers, workstations, storage, firewall function, remote compute, backup or application support into a provider-managed environment. That moves risk out of the customer's own server room, but it does not erase the risk. It relocates the risk into Hosted Advantage's data-centre choices, upstream choices, vendor stack, support process and customer exit terms.
The Hosted Advantage data-centre services page makes the physical layer central. It describes colocation and connectivity for critical systems, support for power and cooling requirements, remote hands, high-speed connectivity, relocation support, infrastructure design and monitoring. It also says the company's data centres are located in Vancouver, Montreal, Ottawa and Toronto, with inter-data-centre connectivity across Canada. Those claims are useful because they move the discussion away from vague cloud language and toward physical service design.
The hosted and managed services page widens the product surface. It presents Hosted Advantage as a provider of scalable alternatives to on-premise infrastructure and says the company handles hosting, managing, monitoring, patching and upgrades for servers, storage, firewalls and related systems. It also describes remote cloud backup and business continuance. That is the kind of offer that creates deep customer reliance: the provider is not merely selling a cabinet; it is taking responsibility for keeping customer systems available.
The rentals page adds another practical dependency. It describes monthly hardware rentals across Canada, including workstations and physical servers, with custom configurations, shipping, delivery, installation and enterprise support. That is not only a sales line. It implies hardware stock, logistics, installation staff and replacement planning. A rental provider can look flexible in normal times, then become constrained by inventory and shipping lead times during a surge, campus buildout or hardware failure.
The consulting page adds migration and architecture support. It says the company helps with data and server migrations, system and storage reviews, network assessment and IT architecture design. That is important because migration is often where the customer learns whether a hosted environment is well documented. If the same provider designs, hosts, supports and later unwinds the environment, the customer needs clear ownership of diagrams, credentials, backup formats, licensing, IP addressing and rollback steps.
The public evidence is therefore strong enough to classify Hosted Advantage as an infrastructure company. The remaining question is assurance. Public pages say what the company sells. ARIN and RIPEstat show a routed network. DNS reveals some SaaS and web-provider dependencies. The public record does not fully show what happens during a rack failure, a route failure, a storage failure, an upstream outage, a staffing crunch or an emergency customer exit.
The company and support identity are public
The identity layer starts with Hosted Advantage's own site. The about page describes Hosted Advantage as an enterprise-level data-centre, colocation and managed-services provider based in Vancouver, British Columbia. It names founders Tony Schoemaker and Gavin Clark and describes network-infrastructure and solution-architecture experience. The contact page lists Hosted Advantage Services at #100, 112 East 6th Avenue, Vancouver, B.C., V5T 1J5, with phone number 1-866-688-3232 and [email protected].
The ARIN record adds a formal network identity. ARIN RDAP for AS398362 lists the AS handle and the name HOSTEDADV-001. ARIN whois identifies Hosted Advantage Services Ltd. as the organization, with an earlier North Vancouver mailing address and the organization ID HASL-22. The ARIN operations point of contact, OPERA643-ARIN, identifies an operations contact at Hosted Advantage Services Ltd., gives the Vancouver East 6th Avenue address and lists [email protected]. ARIN's whois response also notes that ARIN attempted to validate the point of contact and had not received a response since 8 August 2025.
That validation note should be handled carefully. It is not proof that Hosted Advantage is unresponsive to customers. It is a registry-contact hygiene signal: ARIN did not receive a response to its validation process for that point of contact. For a provider selling managed infrastructure, that matters because public contact hygiene is one part of operational assurance. A customer should not overread the note, but should ask whether NOC and abuse contacts are current and monitored.
The public contact surface has another split. The live hostedadvantage.com site is reachable through web-search cache and ordinary browser rendering, but direct curl from this environment hit a Cloudflare block page for wpenginepowered.com. DNS for hostedadvantage.com and www.hostedadvantage.com points the web surface at WP Engine addresses through wp.wpenginepowered.com, and the primary domain has Microsoft 365 mail protection. The company also has an Odoo subdomain, hostedadvantage.odoo.com, that resolves to a Google Cloud address and exposes a default Odoo contact-style site. These observations do not undermine the company's own AS. They show that the public website and mail layer are separate from the AS398362 routed service.
That separation is normal. Many providers host their public marketing site and business mail on third-party SaaS while operating customer infrastructure elsewhere. It becomes risky only if customers confuse website uptime with hosted platform uptime, or if support communications depend on the same services affected by an incident. For Hosted Advantage, the clean customer question is: which channels remain available when the hosted network or a data-centre room has a major incident?
The service pages make physical dependencies explicit
Hosted Advantage deserves a stronger evidence grade than providers that only advertise vague "cloud" capacity. Its service pages mention specific physical and operational functions. The data-centre services page describes colocation, power and cooling support, remote hands, fibre connectivity, high-speed internet, secure cabinets and workstation colocation. It also refers to facilities in Vancouver, Montreal, Ottawa and Toronto. Those are not merely digital claims; they imply space, access control, remote-hands staffing, provider contracts and a cross-country service design.
The same page claims inter-data-centre connectivity across Canada and says all solutions follow industry practices and compliance standards, including SOC2, ISO 27001 and TPN Gold references. Public pages do not show certificates, scope statements, audit periods or which facilities are covered. The customer should therefore treat those as claims to verify, not as self-authenticating proof. A certification can apply to a company, a facility, a specific service, a control environment or a supplier. Scope matters.
Remote hands are especially important. A small customer may not have staff in Vancouver, Montreal, Ottawa or Toronto. If a device needs a cable moved, a failed disk swapped, a server rebooted, a console session opened or a label verified, the customer depends on the provider's remote-hands team. Hosted Advantage's public claim that technicians can assist with rack-and-stack, cabling and troubleshooting is therefore a core service promise. The missing public evidence is the service-level detail: response windows, after-hours coverage, escalation paths, parts availability and what is included versus billed separately.
The hosted and managed services page shows why the service is more than colocation. It describes infrastructure hosting as a full-service approach for servers, storage, firewalls and more. It also describes hosted equipment rentals, remote cloud backup and business continuance. A customer using those services is likely to depend on Hosted Advantage for monitoring, patching, backup and continuity, not merely for power and space.
This matters because managed services can blur responsibility. If Hosted Advantage hosts a firewall, who owns the rule base? If it patches a server, who signs off on change windows? If it stores backups, who tests restores? If it provides GPU or CPU compute for temporary use, who confirms that data is wiped between customers? If it rents a physical server across Canada, who owns replacement stock and shipping risk? The public pages show a broad operating surface. They do not answer every handoff question.
The careers page gives a small but useful staff-surface signal. A Field Service Lead posting describes on-site IT and data-centre operations, incident and service-request resolution within SLAs, hardware installation, troubleshooting, maintenance, infrastructure monitoring, documentation and operational standards. A job posting is not proof that every control is mature. It does, however, support the view that Hosted Advantage's business involves hands-on field and data-centre operations rather than only resale of abstract cloud accounts.
AS398362 is live and visible
The strongest independent technical evidence is AS398362. RIPEstat's AS overview for AS398362 identifies HOSTEDADV-001 - Hosted Advantage Services Ltd. and marks the AS as announced on 12 July 2026. RIPEstat routing status reports first-seen public route evidence in November 2020, last-seen route evidence on 12 July 2026, full IPv4 visibility from the RIS peer set, four visible IPv4 prefixes, 1,536 IPv4 addresses and two observed neighbours.
RIPEstat announced prefixes for AS398362 lists 38.88.73.0/24, 38.88.120.0/24, 38.22.68.0/22 and 38.22.68.0/24. The 38.22.68.0/24 announcement is more specific inside the 38.22.68.0/22 route. That can be normal traffic engineering, a service isolation pattern or a temporary routing choice. It should not be counted as a completely separate address estate from the /22. The cleaner reading is that Hosted Advantage has a current IPv4 surface that includes a /22, two additional /24s and one more-specific /24.
The prefix sources require nuance because all three visible 38.x address areas sit inside Cogent's 38.0.0.0/8 address block in ARIN's public record. ARIN whois for 38.22.68.0, 38.88.120.0 and 38.88.73.0 returns the Cogent parent allocation. RIPEstat, however, sees the more specific routes originated by AS398362, and RIPEstat prefix overview for 38.22.68.0/22, 38.88.120.0/24 and 38.88.73.0/24 identifies AS398362 as the visible origin in the checked view.
For customers, this distinction matters. Provider-routed space can be useful and stable, but it is not the same as customer-owned portable space. If a customer uses a Hosted Advantage address and later needs to leave, portability depends on contract terms, upstream permission and routing arrangements. The public route table shows that the addresses are reachable through Hosted Advantage. It does not tell the customer whether the addresses can move with the application.
The route record also does not show where the servers sit. A prefix can originate from one AS and still front services in multiple facilities, one facility, rented cabinets or a managed overlay. Hosted Advantage's service pages claim Canadian locations and inter-data-centre connectivity. The AS data confirms a routed edge. It does not by itself prove which prefixes map to which city, which facility, which customer class or which disaster-recovery plan.
Two upstream neighbours help, but they are not the whole resilience story
RIPEstat's ASN neighbours view for AS398362 sees two left-side neighbours: AS174 and AS6939. RIPEstat's AS overview for AS174 identifies Cogent Communications, and RIPEstat's AS overview for AS6939 identifies Hurricane Electric. Two observed upstreams are a positive signal. They suggest Hosted Advantage is not relying on a single visible transit path in the public BGP view.
Even so, two AS neighbours are not the same as proven physical diversity. Cogent and Hurricane Electric can be commercially separate while still entering a room through similar building constraints, depending on the same power domain, terminating on the same router pair or being constrained by the same local meet-me room. A proper resilience review must ask whether the circuits have independent physical entrances, whether each upstream is sized for failover, whether both carry all important prefixes, whether routing changes are rehearsed, and whether support can reach both suppliers after hours.
RIPEstat AS-routing-consistency for AS398362 shows the current public route picture with additional detail. It lists 38.22.68.0/22, 38.88.73.0/24 and 38.88.120.0/24 as in BGP and in whois through RADB, a 2001:470:1b4::/48 IPv6 prefix as in whois but not BGP, and 38.22.68.0/24 as in BGP but not whois. It also lists AS174 and AS6939 as present in BGP imports and exports but not in whois policy. That is not unusual in every small network, but it is a transparency limit. Route policy that is visible in BGP but not documented in whois leaves outsiders with less context.
The RPKI picture is a second downgrade. RIPEstat RPKI validation for 38.22.68.0/22, 38.88.120.0/24 and 38.88.73.0/24 all returned unknown in the public view checked for this article. Unknown is not invalid. It does not say the routes are hijacked or broken. It means the route-origin validation service did not see a validating ROA for those origin-prefix pairs.
For hosted customers, RPKI unknown is a hygiene question, not a service verdict. The practical question is whether Hosted Advantage and its upstreams can publish and maintain route-origin authorization for production prefixes, whether route filters align with documented policy, and whether any planned migration would change origin validation. A provider can run reliable services without public RPKI validation, but the absence of validation reduces independent assurance in a routing incident.
The public PeeringDB API query for AS398362 returned no network profile during this review. Again, absence is not failure. Many legitimate enterprise and managed-service networks do not maintain PeeringDB records. But a profile could have helped verify facilities, exchanges, NOC contacts and policy. Without it, customers need to ask Hosted Advantage directly for the site, carrier and escalation map.
The web and mail surface is a separate dependency chain
Hosted Advantage's own customer-facing site is useful evidence, but it is not the same system as AS398362. DNS checks for hostedadvantage.com showed A records at 141.193.213.10, and www.hostedadvantage.com pointed through wp.wpenginepowered.com to WP Engine addresses. The web response from direct curl was a Cloudflare block page for the WP Engine-powered service, while web search and browser rendering still exposed the company's content pages. That split suggests the marketing site sits behind third-party web protection and hosting rather than directly on AS398362.
Mail also sits outside the visible AS. DNS checks found hostedadvantage-com.mail.protection.outlook.com as the MX target for hostedadvantage.com, which indicates Microsoft 365 mail protection. TXT records for the domain included Microsoft verification, SPF includes for Microsoft, Odoo, KnowBe4 and other senders, VMware cloud verification, Atlassian domain verification and other operational markers. These records show a real business SaaS surface. They also show that support, marketing, training, security-awareness, ticketing or collaboration functions may depend on third-party SaaS even if the company operates its own routed network.
The Odoo subdomain is another example. hostedadvantage.odoo.com resolved to 34.44.49.100 and had an Odoo MX record. The HTML exposed a default Odoo "My Website" contact-style page and a canonical path tied to hostedadvantage-com/contact. That is not evidence of a mature customer portal. It is evidence that an Odoo SaaS surface exists and may be used for contact, sales or business operations. In a resilience review, this matters because support tools and customer communications can fail separately from hosted infrastructure.
This separation is not a criticism. It is normal for infrastructure providers to use external services for public websites, mail, CRM, learning, security training, support or billing. The issue is continuity. If AS398362 has a major route or data-centre issue, can Hosted Advantage still communicate with customers through Microsoft 365, phone, SMS or an external status page? If Microsoft mail has a separate incident, can customers still open emergency tickets? If the WP Engine or Cloudflare edge blocks some users, does that affect access to service documentation or only public marketing pages?
Customers should ask for a status and support architecture that is deliberately outside the affected production environment. A provider that hosts its status page, support portal and customer console on the same infrastructure it is trying to repair can make an outage much harder to manage. Hosted Advantage's use of third-party web and mail services may be beneficial here, but the public record does not show the formal incident-communications design.
The multi-city claim needs a recovery map
Hosted Advantage's most valuable public claim is the Canadian site footprint: Vancouver, Montreal, Ottawa and Toronto. If true in operational terms, that can materially improve resilience. A provider with access to multiple Canadian metros can place production and recovery capacity in separate power markets, carrier markets and weather-risk zones. It can offer lower latency to different regions and keep some data inside Canada. It can also help media, education, public-sector or regulated customers who care about locality.
But multi-city marketing is not the same as recoverable capacity. Customers need to know whether each city has live customer-serving capacity, backup-only capacity, partner space, remote-hands access, rental inventory, network presence, or simply sales coverage. They also need to know whether inter-city connectivity is private, leased, internet VPN, carrier Ethernet, cloud interconnect or a mix. The data-centre services page says inter-data-centre connectivity exists, but it does not publish topology, capacity or failover rules.
The procurement value of that claim depends on a city-by-city map. A customer should ask which services are available in Vancouver, which are available in Montreal, which are available in Ottawa, and which are available in Toronto. The answer may differ by product: colocation in one city, managed backup in another, rental inventory in a third, and partner-hosted recovery capacity somewhere else. That is not necessarily a weakness. It becomes a weakness only if the customer assumes the same capability exists everywhere.
A practical schedule should name the facility class, the provider relationship, the network handoff, the remote-hands path, the backup copy and the restoration process for each metro named in the service conversation.
This is also where data-sovereignty language becomes operational. A Canadian footprint can help customers keep workloads close to users or inside a domestic legal environment, but only if primary systems, backup systems, monitoring data, ticket data and exported images are mapped. A workload that runs in Vancouver but backs up to another country is a different risk from a workload whose primary and secondary copies both remain in Canada. Hosted Advantage's public privacy and service pages create a useful starting frame; the buyer still needs a written placement statement for the actual order.
The same map should include communications. Hosted Advantage's public mail, web and SaaS surfaces are outside the visible AS398362 route stack, which may help customer contact survive a network incident. The buyer still needs to know which channel is authoritative during a facility event, which channel is monitored after hours, and whether a status page or emergency phone path exists outside the affected hosted environment.
The difference matters during a facility incident. If Vancouver fails, can a customer workload move to Toronto or Montreal? Are backups already replicated? Is the replacement capacity warm, cold or manual? Are firewall rules and IP addressing portable? Does the customer need to change DNS? How much data must be copied? Are restore targets tested? Are there service tiers with different recovery promises? These questions determine whether a multi-city footprint is a resilience feature or simply a placement option.
Physical access also matters. Hosted Advantage's field-service hiring language supports a hands-on operations model, but customers should still ask who is allowed into each facility, what remote-hands work is included, how parts are staged, how cross-connects are ordered, and how long it takes to complete emergency work outside normal business hours. A provider can have access in four cities and still be constrained by supplier access windows or spare-parts logistics.
The same concern applies to data residency. If a Canadian customer chooses Hosted Advantage for locality, the contract should say where primary data sits, where backups sit, where logs and support data sit, and which external SaaS providers process customer or support information. Hosted Advantage's privacy policy references British Columbia privacy law and PIPEDA, and it says the company uses administrative, technical and physical safeguards. That supports a privacy-aware posture. It does not by itself define the location of every backup, ticket, monitoring event or exported disk image.
Rentals and managed services shift inventory risk to the provider
The rentals page is unusually important for infrastructure risk. Hosted Advantage says it offers monthly hardware rentals across Canada, including workstations and physical servers, with custom configurations, delivery, installation and enterprise support. This is a useful service for studios, classrooms, project teams and customers that need temporary compute. It also makes the provider's inventory management part of the service.
In rental and remote-compute businesses, the first failure mode is not always a network outage. It may be a shortage of GPUs, workstations, storage, spare drives, memory, network cards or replacement servers. It may be shipping delay, customs friction, local installation staffing, licensing activation, image preparation or customer-site cabling. A provider can have a strong AS and still fail a customer if the needed hardware is not available when the project starts or when a unit fails.
The hosted and managed services offer has similar inventory and lifecycle risk. If Hosted Advantage manages servers, storage and firewalls, customers need to know how hardware refresh is handled, how old equipment is retired, whether firmware changes are coordinated, whether customer maintenance windows are formal, and whether emergency patching can be separated from routine service. These are not glamorous questions, but they shape uptime.
Backup and business continuance claims must be tested rather than assumed. A public page can say backups are fast and dependable; a recovery exercise shows whether the backup can restore the application, not just the files. Customers should ask for last successful restore tests, retention periods, encryption and key ownership, restore-time objectives, restore-point objectives, export formats and whether backups are logically separated from compromised customer accounts.
For project-based capacity, customers should also ask about data wiping and handback. If rented workstations or servers are reused across customers, the provider needs a clear sanitization process. If storage is shared or burstable, customers need to know how deleted data is isolated and destroyed. The public privacy page indicates attention to personal-information handling and destruction, but service-specific sanitization terms should be written into the order or master agreement.
A customer should buy the proof, not only the promise
Hosted Advantage's public record earns a Medium grade because the company is visible in several independent ways. It has service pages that describe real infrastructure functions. It has a Canadian office and contact details. It has ARIN-backed AS identity. It has active IPv4 routing with two observed upstream neighbours. It has public evidence of field and data-centre operations hiring. It has privacy and support contact surfaces. These are meaningful signals.
The missing proof is the part that customers most need during bad days. Public pages do not show which facilities are owned, leased or partner-operated. They do not show which site holds which customer class. They do not show whether all four named Canadian metros are live production points for hosted services. They do not publish RPKI route-origin validation, PeeringDB facility details, route policy, incident archives, restore-test evidence, service credits, remote-hands response times, spare-parts stock or data-export terms.
That does not mean Hosted Advantage is weak. It means the public evidence is not complete enough to treat the platform as self-certified. A serious buyer should ask for a network diagram, facility list, upstream list, support escalation matrix, backup design, recovery evidence, maintenance policy, customer data export process, route-origin policy and current compliance scope. The provider's public pages are a good starting point for that conversation.
The most important assurance exercise is operational. Ask Hosted Advantage to restore a sample system. Ask it to move a workload between facilities if that is part of the service. Ask it to demonstrate remote hands. Ask it to show how customer data is exported. Ask it to prove that incident communication remains available when the hosted edge is impaired. Ask whether each visible prefix is provider-assigned, customer-portable or tied to a particular upstream arrangement.
For customers in media, education, professional services and project-heavy businesses, Hosted Advantage may be attractive precisely because it combines physical capacity, remote access, consulting, rentals and managed services. That combination reduces the need to assemble vendors one by one. It also concentrates responsibility. The provider becomes the place where rack access, bandwidth, backup, equipment stock, support and migration knowledge meet. The contract and recovery exercise must be strong enough to carry that concentration.
The contract should separate four layers
The most useful Hosted Advantage contract would separate at least four layers: facility responsibility, network responsibility, managed-service responsibility and customer-controlled assets. Facility responsibility covers cabinets, power, cooling, physical access, cross-connects and remote hands. Network responsibility covers AS398362, upstreams, route-origin authorization, address assignment, firewall edge and DDoS or abuse handling. Managed-service responsibility covers monitoring, patching, backup, restore, operating-system support, application-adjacent tasks and ticket escalation.
Customer-controlled assets cover data, credentials, application configuration, license keys and decisions about when to migrate or fail over.
If those layers are not separated, customers can misread a service promise. A colocation customer may assume Hosted Advantage is responsible for the server operating system when the provider only guarantees space and power. A managed-service customer may assume backups are application-consistent when the provider only snapshots disks. A rental customer may assume replacement hardware is available in the same city when the provider's inventory is pooled nationally. A cloud customer may assume addresses can move with the workload when the address space is provider-routed and tied to upstream policy.
The same separation should apply to credits and remedies. A power failure, a route leak, a hardware-stock shortage, a missed patch, a failed backup restore and a customer-caused misconfiguration should not all be treated as the same incident class. Each has a different owner and a different repair clock. Hosted Advantage's broad service menu makes this especially important because a single customer can buy several layers at once: a cabinet, a managed firewall, backup, rented workstations and consulting help. The customer needs to know which layer has an enforceable target and which layer is advisory or best effort.
The public record does not show this contract map. That is normal for commercial terms, but it is a limit on public assurance. The right procurement request is not a generic service-level promise. It is a layer-by-layer statement of who controls what, what evidence proves it, how incident severity is assigned, how communications stay available, how data is returned and what happens when a supplier outside Hosted Advantage is the failing component. A provider that can answer those questions cleanly is more resilient than one that merely lists more services.
The operating read
Hosted Advantage Services Ltd. is a credible Canadian infrastructure provider with a visible routed network and a service catalogue that maps to real physical dependencies. The public record supports more confidence than a thin hosting shell: AS398362 is live, IPv4 reachability is broad, Cogent and Hurricane Electric appear as observed neighbours, the company publishes colocation and managed-service pages, and the careers page points to hands-on data-centre operations.
The caution is that recoverability is not public enough. The current route-origin validation state is unknown for the visible IPv4 prefixes. IPv6 appears in whois consistency data but not in public BGP visibility. PeeringDB does not provide a public facility map. The website and mail surface depend on WP Engine, Cloudflare, Microsoft 365, Odoo and other SaaS services, which is normal but must be separated from customer-infrastructure assurance. Facility ownership, backup restore evidence, spare inventory, support escalation and customer exit terms remain questions for due diligence.
The result is a Medium evidence grade with practical next steps. Hosted Advantage looks like a real operator, not merely a brand. But customers buying hosted capacity should ask for proof of site placement, carrier diversity, route hygiene, restore testing and data portability before putting critical systems on the platform. Hosted capacity becomes infrastructure only when the customer can see how it fails, how it is repaired and how it can be left without losing the business it was meant to protect.