Faction Group Two, LLC and the capital recovery test behind local network control

Summary

• Faction Group Two, LLC is best understood from public evidence as a Faction-linked number-resource and cloud-infrastructure footprint rather than as a disclosed standalone regional ISP: RIPE NCC lists the Denver-addressed entity as a member serving Germany and the United Kingdom, IP lookup sources tie a UK-facing 89.47.2.0/24 footprint to Faction Group Two, and ARIN/BGP records connect adjacent Faction routing history to 11:11 Systems' post-consolidation infrastructure.
• The capital recovery test is demanding. Faction's historical proposition was not cheap bandwidth; it was low-latency, cloud-attached storage and managed VMware/cloud continuity. That model can create value when customers pay for data sovereignty, performance and recovery assurance, but the public record also shows supplier dependence, route visibility changes, cloud-platform concentration and consolidation pressure that make pricing power conditional rather than proven.

Geography Turns The Strategy Into A Cost Test

The first economic fact about Faction Group Two, LLC is geographic. RIPE NCC's member page lists the entity at 1660 Lincoln, Denver, Colorado, in the United States, with service areas in Germany and the United Kingdom. That is not the footprint of a local cable provider selling one town's broadband plan. It is a cross-border network-resource position: a U.S. company name using RIPE membership to support European number-resource context.

That geography can be an advantage only if it answers a paid customer problem. A Denver-based cloud or managed-infrastructure operator can use European presence to support enterprises that need data close to workloads, cloud regions, datacenters or regulatory boundaries. A London or Frankfurt footprint can matter when an application has latency sensitivity, when a VMware estate needs low-friction migration, when a disaster-recovery copy must sit in a credible jurisdiction, or when a customer wants a controlled path between private infrastructure and public cloud platforms.

But the same geography creates a cost problem. A U.S. company with UK and German service-area evidence has to maintain compliance, routing hygiene, supplier contracts, support coverage and commercial relevance outside its home market. The customer does not pay for the romance of international footprint. The customer pays for a measurable outcome: lower recovery risk, lower migration friction, better data access, latency near a cloud region, or continuity after a datacenter, provider or licensing shock.

This is why the analysis starts with capital recovery rather than brand description. Public records show a real resource-holder footprint. They do not show the standalone revenue, customer count, gross margin or renewal history of Faction Group Two, LLC. The question is therefore not whether the name appears in infrastructure records. It is whether the footprint can earn its cost in a market where the customer can also buy directly from AWS, Microsoft Azure, Google Cloud, a global managed platform such as 11:11 Systems, a colocation provider, a telecom carrier, or a local managed-service provider that resells somebody else's network.

The strongest version of the thesis is narrow. Local or regional control can be valuable when it reduces the operational distance between customer data, private-cloud tooling and the public cloud. The weakest version is familiar. If the footprint is merely address space, a dormant route, or a legacy service-area residue after consolidation, it becomes an overhead item rather than a source of pricing power.

Faction Group Two, LLC therefore has to be assessed as a control point. The buyer is not really buying "internet." The buyer is buying a promise that someone can own a specific local or cross-border infrastructure problem better than a larger, simpler substitute can. That promise has to be paid for before it can be valuable.

The Public Identity Is A Resource-Holder Footprint, Not A Full Operating P&L

The cleanest identity evidence is RIPE NCC's public member page. It names Faction Group Two, LLC, gives a Denver address, lists a Faction email domain contact, and records Germany and the United Kingdom as service areas. Those facts are useful because they place the legal name inside a Regional Internet Registry membership context. They are not enough to infer revenue, service catalogue, customer count or current operating scale.

That distinction matters. A network-resource record can support a public article about infrastructure economics, but it cannot carry more weight than it deserves. The record shows that Faction Group Two, LLC exists in RIPE's membership universe. It does not by itself prove that the entity currently sells access connectivity, IP transit, managed networking, hosting, storage, disaster recovery or cloud services to customers in Germany or the United Kingdom.

Other public signals link the footprint to the broader Faction infrastructure story. Faction's historical company materials describe a Denver cloud-infrastructure business, multi-cloud data services, VMware Cloud on AWS support, cloud-attached storage, disaster-recovery services and service delivery locations including London and Frankfurt. ARIN records for AS14701 and the 68.71.80.0/20 allocation show "Faction" as registrant and carry 11:11 Systems contact or comment fields after later updates.

IPinfo identifies a sample 89.47.2.128 address in London as associated with Faction Group Two, LLC, with a hostname under ilandcloud.com and an abuse contact at iland.com. 11:11 Systems' 2026 public release and transaction-advisory materials say 11:11 acquired several VMware-based businesses over the prior three years, including Faction and iland Cloud.

Those pieces form a coherent context: Faction Group Two appears in a cloud-infrastructure orbit rather than in a mass-access broadband orbit. The economic product is likely about controlled infrastructure placement, not household access. But the legal relationship among Faction Group Two, LLC, Faction's historical brand pages, AS14701, iland-related hostnames and 11:11's consolidated platform is not fully exposed in public filings available for this analysis. A prudent reading treats them as connected evidence, not as a license to collapse every name into one current operating company.

The absence of a public P&L is itself part of the judgment. There is no public Faction Group Two revenue line, capex budget, churn record, customer concentration disclosure, current price list, route engineering plan or standalone management commentary. There are strong infrastructure and history signals, but not enough to say that the standalone entity is winning commercially today.

That limitation does not make the company irrelevant. It makes the analysis conditional. A resource-holder footprint can be strategically valuable when it is embedded in a paid service. It can also become stranded when a larger platform absorbs the brand, centralizes routing, changes supplier contracts or retires old routes. The public evidence points to both possibilities.

The Commercial Problem Is Local Control Against Cloud Scale

Faction's historical commercial proposition was not a low-cost access line. Public Faction materials described a provider of private, hybrid and multi-cloud infrastructure, with customer data housed on Faction servers and managed use of cloud platforms such as Amazon Web Services, Microsoft Azure and Google. In 2018, a Denver Business Journal article mirrored on Faction's site said the company had raised $18 million, had about 50 employees, intended to hire more, and had servers in seven U.S. datacenter sites selected for low-latency links to nearby AWS locations.

That strategy is economically different from selling broadband. It tries to sit between enterprise infrastructure and hyperscale cloud. The buyer has existing VMware estates, storage-heavy workloads, recovery requirements, compliance demands or migration risk. The buyer wants public-cloud reach without surrendering every operating choice to a hyperscaler. Faction's job was to make local or cloud-adjacent infrastructure feel like a controlled bridge rather than another isolated datacenter.

That bridge has a clear value proposition. Enterprises often move to cloud in pieces. They may want to keep one copy of data accessible from multiple clouds, avoid repeated data migration, protect on-premises workloads, preserve VMware skills, and control recovery objectives. A provider with cloud-adjacent storage, low-latency links and managed services can reduce migration friction. It can also turn a capital-heavy local footprint into recurring revenue if customers pay for that reduced friction every month.

The risk is that hyperscale providers have their own gravity. Synergy Research Group reported that Amazon, Microsoft and Google together accounted for 63% of enterprise spending on cloud infrastructure services in the third quarter of 2025, with global quarterly cloud infrastructure revenue around USD 106.9 billion. The U.S. remained the largest cloud market, while the U.K. and Germany were the largest European cloud markets.

That is exactly the terrain where a Faction-linked UK/Germany footprint has relevance, but it is also where the largest platforms set customer expectations around product depth, pricing, procurement simplicity and ecosystem breadth.

A middle layer has to charge for something that the buyer cannot easily get directly from the large platform. In Faction's case, the argument was cloud-adjacent data control: storage close enough to public cloud to perform, separate enough to preserve flexibility, and managed enough to reduce customer burden. That is a plausible product. It is also an expensive product because it requires datacenter sites, cloud interconnection, storage infrastructure, routing, security, partner certifications and experienced operations.

The capital recovery question is whether customers pay for that middle layer as a strategic control point or treat it as a transitional convenience. If it is strategic, the footprint earns its cost. If it is transitional, the customer eventually migrates into AWS, Azure, Google, a carrier's managed service, or a consolidated provider that can amortize the same functions over a larger base.

Network Evidence Shows Useful Control, But Also A Retreated Route

The public network evidence is mixed in a commercially useful way. It shows control, but it also shows that not every historically visible route remains active.

For the European-facing footprint, Scamalytics identifies Faction Group Two as an ISP with 1,148 IP addresses, all of its observed country allocation on that page in the United Kingdom, a low fraud score, and a meaningful server component. IPinfo's page for 89.47.2.128 places the sample address in London, identifies the company behind the IP traffic as Faction Group Two, LLC, shows network 89.47.2.0/24, and displays an ilandcloud.com hostname pattern.

Hurricane Electric's BGP Toolkit page for 89.47.2.0/24 labels the prefix Faction Group Two, LLC, lists RIPE NCC allocation status and shows many reverse DNS names using the same ilandcloud.com pattern.

The route status is more cautionary. RIPEstat and Hurricane Electric both show 89.47.2.0/24 not visible in the global routing table at the time checked in July 2026. RIPEstat's routing status says the prefix was last seen on December 3, 2025, announced by AS14701. Its routing history shows a long period in which AS14701 originated that /24 from late 2019 onward, with substantial full-feed peer visibility during earlier windows.

AS14701 itself is part of the Faction story. RIPEstat identifies the holder string as "ELEMENTEK - Faction" and reports it was not announced as of the July 2026 observation. Hurricane Electric's AS14701 page says the AS has not been visible in the global routing table since June 10, 2026, identifies it as Faction, lists a Faction website, shows one originated IPv4 prefix in the last-visible data, and records an observed peer relationship with Iron Mountain Data Center. It also lists exchange presences at Any2 Denver and Digital Realty/Telx facilities in Atlanta and New York.

ARIN RDAP adds another layer. The autnum record for AS14701 has the name ELEMENTEK, with Faction as registrant and 11:11 Systems in current contact/comment fields. The ARIN record for the broader 68.71.80.0/20 direct allocation is named for 11:11 Systems and also shows Faction as registrant, with last-change evidence in January 2026. That is what a transition can look like in public registry data: old technical identity, current platform contact fields, and route visibility that no longer looks like a simple, active standalone Faction announcement.

For economics, the key point is not whether one prefix is active today. The point is that local network control has to remain useful after consolidation, migration and route rationalization. A dormant route can still reflect retained address assets or retired service. An active route can support paying workloads. The public record shows that Faction's footprint had real routing substance, but it does not prove that Faction Group Two's RIPE-linked European footprint is currently earning recurring revenue at a level that covers the cost of maintaining independent control.

Low-Latency Storage Was The Product, Not Generic Connectivity

Faction's own historical materials make the product logic clear. The company emphasized Cloud Control Volumes, VMware Cloud on AWS, disaster recovery, private cloud and multi-cloud data services. It described a single managed copy of enterprise data that could be accessed from cloud providers and services over high-speed, low-latency connections. It described proprietary and patented connectivity, Layer 2 integration and performance claims around sub-2 ms or sub-3 ms links in specific contexts.

That matters because the economics of low-latency cloud-adjacent storage are better than the economics of undifferentiated connectivity. A generic network reseller fights price compression. A storage and recovery platform can sell risk reduction, performance and operational convenience. The buyer is not only buying a pipe; it is buying fewer copies of data, less migration pain, faster recovery, predictable cloud-adjacent access and a team that understands VMware and hyperscale integration.

The Faction product story was strongest where the customer's cost of switching was high. A business with petabytes of data, VMware operations, disaster-recovery objectives and multiple clouds cannot simply move every workload overnight. Data gravity creates friction. Latency makes geography matter. Recovery objectives make architecture matter. Faction's Cloud Control Volumes and hybrid disaster recovery proposition tried to monetize that friction by placing storage near cloud services while keeping it under a managed, portable model.

The page-level evidence supports the claim. Faction's 2019 release said the company was a managed services provider for VMware Cloud on AWS, including disaster recovery and production deployments, and claimed to be the only provider of attached storage to VMware Cloud on AWS. It cited AWS Advanced Consulting Partner status, VMware Premier Service Provider status, more than 100 petabytes of storage under management, thousands of hosts, and a growing datacenter footprint including U.S. and European locations.

The 2021 VMware Cloud on AWS article described Faction as a VMware Premier Cloud Provider and VMware Principal Partner, with Cloud Control Volumes and hybrid disaster recovery offerings intended to keep costs predictable.

Those are company-controlled claims, not audited financial proof. But they reveal the intended margin engine. Faction wanted to be paid for solving a hard boundary between enterprise data and public cloud. That is a better business than selling a commodity route if customers trust the provider and if the product keeps enough differentiation after partners and platforms change.

The practical risk is that the same product depends on large suppliers. VMware, AWS, datacenter operators, storage vendors and connectivity providers all sit in the value chain. Faction could patent techniques, operate service locations and manage customers, but it could not control every upstream commercial term. When the supplier stack changes, the economics of the local control layer change with it.

Capital Recovery Depends On Density Around Cloud And Datacenter Hubs

Local control is expensive because it is not really local in one dimension. It combines physical sites, storage equipment, routers, switching, cross-connects, interconnection, licensing, security controls, support staff, monitoring, customer success and sales. The more specialized the service, the more density it needs around the facilities and cloud regions where customers actually place workloads.

Faction's cloud-location page makes that density strategy visible. It names U.S. locations including Portland, Denver, Santa Clara, Los Angeles, Chicago and Reston, and international locations including London, Frankfurt and Sydney. It says these service delivery sites were selected for proximity to major public clouds, security, compliance, reputation and low-latency connections between customer data and public-cloud applications and services. The page also claims high availability and low-latency connections.

The page's own wording is not perfectly consistent about the number of locations, but the location list is clear enough for the economic point: Faction was trying to build a hub strategy, not scattered incidental hosting.

A hub strategy can work when enough workloads concentrate around each site. More customers on the same storage, network and support base improve utilization. More data under management makes the platform stickier. More recovery and migration work spreads technical expertise over a larger revenue base. More partner relationships make each location easier to sell.

The same strategy can fail if utilization is thin. A low-latency cloud-adjacent footprint has fixed costs even when customers are slow to commit. Data-center capacity, interconnection, hardware refresh, software licensing, compliance and support are not free while the sales team waits for demand. If buyers choose direct hyperscale storage, a national carrier's managed service, or a larger consolidated VMware platform, the local footprint may carry the cost of specialization without enough volume to justify it.

The RIPE and ARIN evidence hints at that tension. Some Faction-linked routes and address assets are visible in historical records, but current public route visibility is weaker than the product story would imply for an actively marketed independent network. That does not prove the service is gone; consolidated providers often move addresses, aggregate routes or rationalize old infrastructure. It does mean the value of the footprint must be tested by current paying usage, not by past announcements.

The capex test is therefore simple but hard to observe publicly. Does the London and Frankfurt resource/service-area footprint support enough customers who pay for data placement, continuity and cloud adjacency? Does each site have enough storage and interconnect utilization to cover facility and platform cost? Do the routes and address assets remain operationally necessary, or are they residue from earlier deployments? Public sources cannot answer those questions, but they identify exactly where the margin is made or lost.

Supplier Dependence Limits Pricing Power

Faction's differentiation depended on partners. Its technology-partner page listed Dell and VMware as technology partners, AWS, Azure, Google Cloud and Oracle as cloud providers, and Equinix and CoreSite as datacenter providers. Its product materials referenced VMware Cloud on AWS, AWS Direct Connect, NetApp, Dell, cloud-adjacent storage and disaster recovery. Its BGP and registry evidence points to Iron Mountain, Digital Realty/Telx exchange locations, iland hostnames and 11:11 Systems contact fields in different parts of the footprint.

That web of suppliers is not a weakness by itself. Modern infrastructure is assembled. Customers do not expect every provider to own every datacenter, cloud region, fiber route, storage platform and virtualization stack. The economic issue is bargaining power. A middle-layer provider has to depend on large platform vendors while persuading customers that it is more than a reseller of those vendors.

VMware is the clearest example. Broadcom's VMware strategy changed the economics for cloud service providers. Broadcom's own program announcement said it would reduce the overall size of the VCSP program and realign providers around Pinnacle, Premier and Registered tiers. It emphasized a VMware Cloud Foundation subscription model, cloud commerce managers, and co-selling with Pinnacle partners. Ars Technica later reported that Broadcom moved toward a new invite-only program for cloud service providers in 2025, creating uncertainty for small and medium providers and ending a white-label path by October 31, 2025.

For a Faction-style business, that matters directly. If a provider's value proposition is deeply tied to VMware-based workloads, changes in VMware licensing, partner access and support rights can reshape the business model. A smaller provider may lose access or have to work through a larger partner. A larger provider may use its status to acquire customers and assets from smaller providers.

11:11 Systems' own January 2026 release describes the Ntirety acquisition in exactly that context: Broadcom's changes reduced the authorized partner universe, and 11:11 positioned itself as a platform for secure, compliant, high-performing cloud services. The release says 11:11 had acquired five major VMware-based businesses over the prior three years, including Faction, and had more than 6,000 customers.

Supplier dependence therefore cuts both ways. Faction's old model gained credibility from VMware, AWS and major datacenter relationships. But the more critical those relationships are, the less pricing power the middle layer keeps if the platform owner changes rules or if a larger managed provider can offer the same supplier access with more scale.

The operating judgment is not that local control is impossible. It is that local control must be tied to customer outcomes that survive supplier repricing. If Faction Group Two's footprint is useful because it provides jurisdictional placement, low latency, address continuity and operational knowledge, it may still have value inside a larger platform. If it is useful only because it had privileged access to a past VMware or cloud arrangement, that value can move upstream to the supplier or downstream to the consolidator.

Customers Buy Risk Transfer, Not Just Bandwidth

The customer case for a Faction-linked footprint is strongest when the buyer is purchasing risk transfer. The buyer may be an insurer, professional-services firm, software company, health provider, financial business or mid-market enterprise with VMware workloads and continuity requirements. It does not want to run every storage, routing and recovery decision itself. It wants a provider to reduce the risk of migration failure, prolonged outage, data unavailability and cloud lock-in.

Faction's public materials included a case-study reference to Pennsylvania Lumbermens Mutual using Faction's disaster-recovery services with VMware Cloud on AWS. That kind of customer story is important because it explains the buying motive. A customer does not wake up wanting a new ASN or another cloud-adjacent storage invoice. It wants recovery objectives, operational simplicity and confidence that the infrastructure will work during a failure.

That is why revenue growth and value creation must be separated. A provider can add customers and still destroy value if those customers require heavy engineering, hold large data sets at low margin, demand custom support, or churn after a migration is complete. Conversely, a smaller customer base can be valuable if it buys managed recovery, higher-touch support, storage tiers, compliance assurance and long-term continuity. The Faction model appears designed for the second category.

Public sources do not show Faction Group Two's current customer mix or contract terms. Faction's 2019 release said the company managed more than 100 petabytes of customer storage and thousands of hosts, and expected those numbers to more than double in 2019. The 2018 funding article said the company was targeting growth and international expansion. Those statements show ambition and demand signals, but they are historical and company-controlled. They do not prove present renewal quality, margin or customer concentration.

The customer concentration risk is real. A specialized cloud-adjacent footprint may depend on a narrow set of enterprises with VMware-heavy estates, large storage needs and specific recovery requirements. If those enterprises shift to direct hyperscale architectures, adopt SaaS, move to a larger VMware Cloud Service Provider, or rationalize vendors under a global managed-services contract, the local footprint can lose relevance quickly. If they stay because data gravity, compliance and recovery discipline matter, the same footprint can be sticky.

Pricing power comes from urgency before failure. Customers that buy disaster recovery only after an incident are hard to price well. Customers that fund continuity as a board-level operating requirement are better. The public evidence around Faction's product suggests it aimed at serious continuity buyers. The current evidence around route visibility and consolidation suggests the buyer relationship may now be mediated by a larger platform. That may improve customer confidence, but it can also shift the economics away from the standalone resource holder.

Larger Platforms And Carriers Define The Substitute Price

The substitute set is broad. A customer considering Faction-style local control can choose a hyperscaler, a carrier, a colocation provider, a managed IT provider, a large VMware Cloud Service Provider, or an internal rebuild. Each substitute affects pricing power.

Hyperscalers set the scale benchmark. Synergy's Q3 2025 data shows AWS, Microsoft and Google with 63% of enterprise cloud infrastructure spending, and third-placed Google far ahead of the long tail. These platforms offer global regions, native storage, disaster-recovery services, identity, security, analytics and procurement standardization. A middle-layer provider has to explain why its extra layer reduces cost or risk rather than adding complexity.

Large managed platforms set the convenience benchmark. 11:11 Systems now describes itself as a global platform for cloud, connectivity, backup, cyber, disaster recovery and security, with more than 6,000 customers. Its acquisitions of iland Cloud, Green Cloud Defense, Unitas Global, Sungard Availability Services, Faction and Ntirety create breadth that a smaller specialist cannot match alone. For customers affected by VMware provider consolidation, a larger platform may look safer than a small provider with uncertain program access.

Carriers and datacenter operators set the infrastructure benchmark. A customer that needs private connectivity, colocation, cloud on-ramps or managed networking can source many of those inputs from large telecom or datacenter providers. Equinix, CoreSite, Digital Realty, Iron Mountain and national carriers already have extensive facilities and cross-connect ecosystems. If Faction's value is only physical proximity, the larger infrastructure owner can compete. If Faction's value is software, storage orchestration and VMware-specific recovery expertise, it has more room.

Managed-service providers set the relationship benchmark. Many mid-market buyers prefer one practical partner for cloud, security, backup, networking and support. They may not care which legal entity holds the number resources if the service desk, recovery plan and monthly invoice work. That makes a standalone resource footprint less visible to the buyer unless it directly improves uptime, latency, compliance or recovery.

The capital recovery test is therefore a substitute test. Can Faction Group Two's footprint support a differentiated service that the buyer cannot get more simply from AWS, Azure, Google, 11:11, a carrier or a colocation provider? If yes, the footprint can command a premium. If not, it becomes a component inside someone else's product, and the economic rent moves to the larger platform.

The public record does not show a current public price list for Faction Group Two. That absence matters. In a market with powerful substitutes, pricing power is proven by renewals, expansion and margin, not by technical diagrams. The facts that would matter are contract duration, net revenue retention, storage utilization, recovery-test success, latency SLA performance, support cost per customer and the share of customers that buy higher-value managed services rather than one-off migration work.

Consolidation Changes The Value Of The Footprint

The Faction story has become a consolidation story. ARIN records show Faction-linked resources with 11:11 Systems contact fields. 11:11's public release says it acquired Faction as one of several VMware-based businesses. Houlihan Lokey's transaction page for Ntirety says 11:11 now supports more than 6,000 customers globally and has acquired Faction alongside iland Cloud, Green Cloud Defense, Unitas Global and Sungard Availability Services. CRN's 2026 coverage frames the Ntirety deal as part of a VMware provider acquisition spree after Broadcom's channel changes.

That can increase the value of Faction's footprint. A larger platform can spread support, security, compliance, procurement and product development over more customers. It can cross-sell backup, cyber recovery, managed public cloud, private cloud and connectivity. It can rationalize routes, combine datacenter contracts and make a Faction-originated control point part of a broader customer solution. If the Faction Group Two footprint is still operationally useful in the United Kingdom or Germany, 11:11's scale can help it earn its cost.

The same consolidation can reduce standalone relevance. Customers may buy 11:11's platform, not Faction Group Two's local control. Old Faction routes may be aggregated, retired or moved. The ilandcloud.com hostname evidence tied to a Faction Group Two IP could reflect integration, legacy infrastructure or current service dependency, but public sources do not disclose which. A route that is no longer visible may be a deliberate rationalization, not a failure.

But it still means the capital recovery story has shifted from "does Faction as a specialist win?" to "does this footprint create enough value inside a larger infrastructure platform?"

That shift matters for valuation. A standalone specialist must recover cost from its own sales funnel. A consolidated platform can justify an asset because it protects customers, fills a regional gap, supports a migration path or preserves acquired revenue. The cash-flow attribution changes. The local resource footprint may be valuable even if no customer ever hears the legal name Faction Group Two, LLC.

For public readers, the most disciplined judgment is that consolidation raises both confidence and opacity. It raises confidence because a larger provider may have more resources to maintain continuity, security and customer support. It raises opacity because the public cannot easily see which legal entity carries which customers, assets, contracts or routes after integration.

That is why the evidence that would prove value is operational, not cosmetic. If the U.K. and German service areas support active paid workloads, if Faction-originated storage technology remains in market, if customers renew under 11:11 rather than migrate away, and if route/address assets support measurable services, consolidation can turn local control into a better-funded platform asset. If the footprint is mainly legacy residue, consolidation may simply harvest customer relationships while retiring the expensive local pieces.

Unofficial Signals Are Useful Only As Friction Evidence

Unofficial signals are informative but must be handled carefully. Scamalytics gives Faction Group Two a low fraud score and says it operates 1,148 IP addresses, many running servers, with the observed footprint on that page in the United Kingdom. IPinfo identifies a London sample IP as Faction Group Two, LLC and shows an ilandcloud.com hostname. Hurricane Electric shows reverse DNS patterns and historical route visibility. These sources help triangulate the operational footprint, but they do not prove customer revenue, service quality or current product status.

The low fraud signal is still economically relevant. A cloud or hosting provider's address space can become a cost center if it is associated with abuse, spam, proxy traffic or fraud. Clean reputation supports customer trust and reduces operational friction. Scamalytics' caveat is important: it sees only the traffic visible to its network, and different traffic types may carry different risk. The score is therefore a market signal, not a compliance certification.

The hostname evidence is also useful but limited. The ilandcloud.com pattern on Faction Group Two-linked addresses fits the broader 11:11 acquisition context because 11:11 acquired both iland Cloud and Faction. But reverse DNS is not a contract. It may persist after an integration, represent an allocation naming convention, or point to a service path that is not visible publicly. It supports a hypothesis of shared or consolidated infrastructure. It does not prove which entity bills the customer or who owns the current service obligation.

Route visibility is similarly ambiguous. A prefix falling out of global BGP visibility may mean retirement, migration, consolidation, a change in upstream architecture, a temporary state or a deliberate move away from public announcement. It is not automatically a sign of distress. But for capital recovery it matters because active routes and address utilization are what turn network resources into services. A dormant route cannot by itself earn revenue unless it supports another internal or planned use not visible in public routing.

The unofficial signal that matters most is the pattern, not any single page. The pattern is a cloud-hosting and VMware-linked infrastructure footprint with UK-facing resources, Faction historical service claims, 11:11 consolidation, and some evidence of route rationalization. That pattern fits a market in which specialized providers either scale up, sell into larger platforms, or lose pricing power to hyperscalers and large managed providers.

What Would Prove The Local-Control Footprint Earns Its Cost

The judgment on Faction Group Two, LLC should change with evidence. The first evidence would be current utilization. If the United Kingdom and Germany service areas support active paying workloads, especially storage-heavy, VMware-dependent or disaster-recovery workloads, the RIPE footprint has operating value. If the footprint is mostly inactive address space, the case weakens.

The second evidence would be current route and address design. A clear explanation of which prefixes are active, which ASNs originate them, why AS14701 and 89.47.2.0/24 lost visibility, and whether the change reflects integration into 11:11 or service retirement would move the analysis from inference to fact. Active RPKI, abuse handling, route diversity and documented failover would strengthen the operating case.

The third evidence would be customer economics. The model works if customers renew because local or cloud-adjacent control reduces their risk and cost. The useful numbers would include revenue retention, gross margin by service line, storage utilization, disaster-recovery test performance, customer concentration, attach rate for managed services, and the share of customers buying ongoing continuity rather than one-time migration support.

The fourth evidence would be supplier economics. Faction's old proposition depended on VMware, AWS, storage vendors, datacenter providers and network interconnection. The facts that matter are partner status, licensing terms, cross-connect cost, storage hardware lifecycle, support obligations and whether 11:11's scale has lowered the cost of delivering the former Faction services. Broadcom's VMware program changes make this particularly important.

The fifth evidence would be competitive win data. If Faction-originated services inside 11:11 continue to win against direct AWS, Azure, Google, carrier and colocation alternatives, the footprint has defensible value. If customers are migrating away from the local-control layer toward direct hyperscale or broader managed-service bundles, the footprint's pricing power is weaker.

The current public record supports a cautious conclusion. Faction Group Two, LLC is not just a stray name in a resource record; it sits in a Faction-linked infrastructure context with UK/Germany service-area evidence, IP lookup corroboration, Faction cloud-service history, ARIN routing history and 11:11 consolidation. The old Faction proposition had a coherent economic logic: use local, low-latency, cloud-adjacent control to help enterprises move, protect and access data without surrendering every decision to one hyperscaler.

But coherent logic is not proof of current value creation. The visible route retreat, supplier dependence, lack of public standalone financials and shift into a larger consolidated platform all limit the judgment. The footprint can earn its cost if it supports sticky enterprise workloads that pay for continuity, data placement and operational accountability. It fails the test if customers see it as an expensive middle layer and choose the simpler alternative offered by hyperscalers, carriers or larger managed platforms.

The answer is therefore conditional rather than binary. Faction Group Two's local-control footprint is economically plausible, but only as a paid control surface. The evidence that would make it investable is not another address record. It is proof that customers pay enough, renew long enough and depend deeply enough on the footprint for the capital and operating burden to be worth carrying.