Summary

  • Public records connect Mark Erskine to three dated operating decisions at Host Depot. In September 2006, he said the company had re-created its offer around a new brand, search services, e-commerce tools and a bandwidth-rollover program. In April 2007, he explained the choice of Ensim Pro X for a dedicated-server initiative that needed one control panel across Windows and Linux environments. In May 2011, he said Host Depot replaced a customer-service system because the earlier one was inflexible and limiting. These are attributable decisions recorded in company or vendor announcements. They do not independently prove customer adoption, revenue growth, cost savings, reliability or service quality.
  • A separate current record anchors that historical account in network identity. ARIN RDAP lists AS15114 as HOSTDEPOT-ASN, names Host Depot as the registrant and identifies Erskine as a validated individual technical contact. That record is not a biography and does not prove a current executive title. It does show that the hosting business described in the older records had an autonomous-system identity with a named technical relationship. The most defensible profile is therefore about operational interfaces: how an Internet-access and hosting provider packaged scarce resources, selected control systems and changed support tooling, and how a registry record preserves accountability after marketing claims have aged.

A Person Visible Through Operating Decisions

Many executive profiles begin with a current title and work backward. Mark Erskine's public evidence is better read in the opposite direction. The title evidence is historical. The operating decisions are dated. The current registry record is technical rather than corporate. Taken together, those differences create a profile that is more precise than a generic account of entrepreneurship.

A Host Depot announcement dated September 18, 2006 identifies Erskine as president and chief executive at that time. It quotes him saying the company had used the knowledge of its first decade to "re-create" itself for the market. The offer described in the announcement combined hosting, search-engine work, e-commerce tools and a program called Bandwidth Bank. The page also described Host Depot as providing Internet-access products and high-end e-commerce hosting.

The evidence does not show that Erskine personally built every component. A company announcement can link a senior executive to a choice without identifying the product managers, network staff, support staff, vendors or customers who shaped it. The useful person-level fact is narrower: he publicly explained the repositioning and the bundle of services through which Host Depot intended to compete.

In April 2007, another dated Host Depot record quotes Erskine on the selection of Ensim Pro X for a dedicated-server initiative. The announcement says the control panel supported Windows and Linux environments and was meant to centralize and automate hosting operations. Erskine's quoted explanation links him to the selection. It does not establish that he wrote the software, configured the servers or measured the result.

In September of that year, HostSearch reported that Host Depot joined the RatePoint partner program. The report identified Erskine as president and chief executive and quoted him describing a hosted customer-communication tool for smaller online merchants. HostSearch was independent of Host Depot, although the item closely followed announcement language. It corroborates the dated identity and decision while providing little independent measurement of outcome.

In May 2011, a Host Depot announcement about SmarterTrack again identifies Erskine by the same historical title. This time the quotation contains a direct operating constraint. He said the preceding customer-service solution had been inflexible and limiting. The company adopted a system that combined ticketing, knowledge-base and customer-communication functions.

The sequence is useful because each decision concerns an interface. The 2006 offer determined how customers would consume hosting, bandwidth and adjacent services. The 2007 Ensim selection determined how server functions would be exposed to operators, resellers and site owners. The RatePoint relationship addressed communication between hosted merchants and their customers. The 2011 support-system replacement addressed communication between Host Depot and its own users.

These records show a person through choices about boundaries rather than through personality labels. They do not reveal private emotions, ambitions or conduct inside meetings. They show what Erskine was quoted as choosing and why one of the existing systems was considered inadequate. That is enough to analyse a pattern without inventing a private life.

The Business Before the Automation Layers

Host Depot's own 2006 and 2007 descriptions say the company was founded in 1997 and focused on hosting and integrated e-commerce solutions. They also say it expanded into Internet-access products, site development, promotional services and high-end e-commerce hosting. Those are company descriptions, not audited classifications, but they establish the range of activities the later decisions were designed to support.

Hosting in that period joined several distinct constraints. The provider needed physical or leased infrastructure, server capacity, network reachability, addressing, domain and application support, billing, customer service and tools that allowed users or resellers to manage services. A failure at one layer could make the entire offer unattractive even if the other layers continued to run.

Internet access and hosting were related but not identical. Access connected users or businesses to networks. Hosting made applications, sites, mail or e-commerce systems reachable from those networks. A provider operating in both areas had to manage the boundary between customer-facing packages and the technical resources behind them. The public records do not map Host Depot's complete topology, but the later AS15114 record confirms that network identity was part of the operating structure.

The company's 2006 repositioning can be read against that complexity. Host Depot was not announcing one new server. It was changing how multiple capabilities were packaged and described. Search-engine services addressed visibility. Google Checkout and other e-commerce tools addressed transactions. Hosting supplied the persistent online environment. Bandwidth Bank addressed how data-transfer allowance would be accounted for over time.

That mix created organizational dependencies. Search work depended on skills and external platforms. E-commerce tools depended on payment and software partners. Hosting depended on servers, networks and support. A bandwidth-rollover policy depended on accurate usage measurement and billing. The provider could present the bundle as one offer, but the operating system behind it remained a collection of interfaces.

Erskine's quoted role in the repositioning does not establish sole authorship. The same 2006 record quotes a sales and marketing executive on the packaging. A customer is quoted on search work. Vendors and partners appear elsewhere in the record. The public evidence therefore points to an organizational decision with Erskine as one named executive voice, not to a single-person invention.

The inherited condition also matters. By 2006, the company said it had nearly a decade of operating history. Existing users, plans, servers, staff practices and supplier relationships would have constrained any redesign. A new brand could be announced quickly. Changing the service and support systems behind it required a longer sequence.

The later records show parts of that sequence. Ensim addressed dedicated-server administration in 2007. RatePoint added a customer-feedback layer for hosted merchants that year. SmarterTrack addressed Host Depot's own support process in 2011. The evidence does not say these projects followed one master plan. It does show that the company repeatedly selected external systems to organize work around its hosting offer.

Re-Creating the Offer in 2006

The strongest phrase in the 2006 record is Erskine's statement that Host Depot had "re-created" the company to serve the market better. The wording is promotional, but the record specifies what changed. Host Depot announced a new brand position and logo, search-engine plans, e-commerce options and Bandwidth Bank. That specificity allows the repositioning to be evaluated as a set of product and policy choices.

The search-engine plans moved the provider beyond storage and connectivity. Host Depot was offering to help customers attract traffic, not merely keep a site online. The announcement also connected the offer to e-commerce tools. The business logic was that a hosted site would be more valuable if it could be found and used to complete transactions.

Public evidence does not show how many customers purchased those services or whether the work produced durable results. The announcement contains positive claims and a customer quotation, but no independent cohort, methodology or financial disclosure. The article therefore treats the products as parts of the offer, not as proven engines of growth.

Bandwidth Bank was a more direct hosting policy. The program allowed shared-hosting users to carry unused bandwidth allowance from one month into the next. In the language of the announcement, customers would not lose what they had purchased merely because it was unused during a billing period.

The policy transformed an operational measurement into a customer entitlement. Data transfer had to be counted. Unused allowance had to be recorded. The balance had to be associated with the correct account and carried into the next period. Billing and hosting systems had to agree about the available amount. A marketing promise therefore depended on accurate technical and commercial records.

The public announcement claimed savings and substantial use. Those claims are not independently verified here. There is no archive of account-level balances, overage charges or customer retention. What can be established is the policy mechanism and Erskine's public association with the package in which it appeared.

The policy also allocated risk differently. Under a simple monthly allowance, unused capacity has no future claim attached to it. Under rollover, the provider accepts a future obligation to recognize an accumulated balance. Customers gain flexibility, while the provider must maintain accounting continuity and capacity planning that can absorb changing use.

That does not mean every carried unit of bandwidth produced a matching future network cost. Hosting plans often aggregate usage across many customers. The operational significance lies in the record, not in a one-to-one reserve. Host Depot had to preserve a credible account of what each user had acquired and what remained available.

This is one reason the 2006 decision fits a broader network-identity story. Internet services depend on records that remain accurate across time: account balances, allocations, server permissions, domain relationships and network-resource contacts. None of those records is the service itself. Each is a control surface through which the service can continue.

The announcement does not explain how Host Depot implemented the policy or whether the program remained unchanged. It gives no software architecture and no reconciliation process. Those absences should remain visible. The decision can be analysed as a resource-accounting choice without pretending to know the internal code.

Ensim Pro X and the Dedicated-Server Control Plane

The April 2007 Ensim record concerns a different kind of continuity. Host Depot selected Ensim Pro X as the control panel for a dedicated-server initiative. The announcement describes support for Windows and Linux and a hierarchy in which providers, resellers and site owners could manage hosting functions.

A control panel is not merely a visual convenience. It defines which actions are available, who may perform them and how changes are translated into server configuration. It can reduce repetitive manual work, but it also concentrates authority in software. If the interface is incomplete, unstable or poorly secured, automation can reproduce mistakes at scale.

Erskine's quotation says Host Depot chose Ensim to create a more comprehensive package. That explanation places the decision at the product boundary: the company wanted dedicated servers to include an administrative environment that resellers and smaller businesses could use. The record does not show the procurement process, competing products, implementation cost or deployment schedule.

The announcement calls the technology carrier-class and emphasizes scalability, stability and security. Those descriptions came from Host Depot and Ensim, parties with a commercial interest in the selection. They are not independent test results. The defensible fact is that the product was selected and publicly described as the control panel for the initiative.

The Windows-and-Linux scope was organizationally important because it promised one management layer across different operating environments. Customers and resellers could encounter a more consistent commercial interface even when the underlying systems differed. For Host Depot, that could reduce the number of separate workflows staff had to support.

The same abstraction introduced dependency on the vendor. Features, security updates, compatibility and licensing would affect Host Depot's offer. A provider that uses third-party control software gains speed and a standardized interface but gives part of its operating roadmap to another organization.

The record does not show how Host Depot managed that dependency. It does not say whether the company customized the system, how long it remained deployed or what replaced it. It also does not show whether every dedicated-server customer used the panel. These are unresolved operational questions, not reasons to erase the decision.

The choice can be understood as a move from individually managed infrastructure toward a repeatable service. A server becomes easier to sell to resellers or smaller organizations when common tasks can be delegated through permissions and a consistent interface. The control plane converts specialized operational work into a product surface.

That conversion changes responsibility. Customers gain the ability to act, but the provider still controls the environment in which those actions take effect. Resellers may control their own branding and users while depending on Host Depot for the underlying servers and network. Host Depot depends on Ensim for the software layer. The resulting service is a chain of bounded control rather than one organization exercising total authority.

Erskine's role is visible at the selection point. The public record does not identify who tested, integrated or operated Ensim Pro X. A fair account credits the attributable choice while leaving technical execution with the unnamed teams and vendor whose work the service required.

RatePoint and the Hosted Merchant Interface

The September 2007 HostSearch item adds another layer to the sequence. It reports that Host Depot joined the RatePoint partner program and would make a customer-feedback and quality-assurance platform available to hosted merchants. Erskine's quotation describes a hosted communication tool intended to help smaller online businesses respond to customers.

Unlike the Ensim control panel, RatePoint sat closer to the merchant's public relationship with buyers. It addressed ratings, reviews, feedback and responses. Host Depot's role was to make that capability available through a hosting relationship rather than to build the whole system itself.

The decision extended the meaning of hosting. A provider was no longer selling only network reachability, server resources and account management. It was assembling external services that affected how a merchant communicated and established reputation. That broadened the value proposition but also increased dependency on third-party policy and software.

HostSearch is useful because it is a separate publication, but its report should not be overstated. The wording closely resembles an announcement. It contains Erskine's promotional explanation and product claims. It does not present adoption data, merchant interviews or an independent assessment of RatePoint's effectiveness.

The supported conclusion is therefore about the decision and its intended mechanism. Host Depot joined the program. Erskine was identified in a dated role. He described the gap as the absence of an affordable, interactive hosted communication tool for smaller online businesses. The program was intended to supply that interface.

The organizational allocation is clear. RatePoint controlled the feedback platform. Host Depot controlled how it was offered to hosting customers. Merchants controlled whether and how they used it. Consumers supplied reviews or feedback. No single entity controlled the entire result.

That allocation also created questions about authenticity, moderation and response. The report says the system checked reviews for authenticity and allowed businesses to respond. It does not disclose the checking method or the distribution of favorable and unfavorable feedback. The article does not treat the platform's own descriptions as proven outcomes.

For Erskine's profile, the decision matters because it repeats a pattern. Host Depot selected an external system to make a complex function available through its own customer relationship. Ensim exposed server operations. RatePoint exposed merchant communication. Both choices used hosted software to turn specialist processes into accessible service components.

The pattern should not be rewritten as a claim that Erskine anticipated every later software-service model. The evidence is local and dated. It shows what Host Depot publicly chose in 2007. It does not establish industry leadership, originality or long-term competitive impact.

Still, the decision reveals how a hosting provider could seek differentiation when raw storage and connectivity were becoming easier to compare. The company packaged tools around the hosted application. The value shifted from keeping a site reachable toward helping the customer operate an online business. Whether that strategy worked financially remains unknown.

Replacing an Inflexible Support System

The 2011 SmarterTrack announcement provides the clearest documented constraint in the source set. Erskine said Host Depot's previous customer-service solution was very inflexible and limiting. The company selected SmarterTrack for functions including ticketing, a knowledge base and web-based customer communication.

This decision concerned Host Depot's own service boundary rather than a tool delivered primarily to merchants. Hosting customers needed a way to ask questions, report problems and receive support. Staff needed a way to assign, preserve and retrieve those interactions. The earlier system, according to Erskine, constrained that work.

The replacement bundled several functions in one system. A ticket system preserved requests and status. A knowledge base could capture recurring answers. Live communication could handle immediate questions. Reporting could make patterns visible to managers. The announcement also described automation and external-database integration.

Those are product descriptions, not proof that Host Depot used every function or achieved every claimed saving. The announcement offers no response-time series, staffing data, customer-satisfaction measure or cost comparison. The article therefore does not claim that the change improved support performance.

The attributable sequence remains significant. A running support system was judged inadequate. A replacement was chosen. The stated reason was operational inflexibility. Unlike a brand announcement, this record names a constraint inside the service organization.

Support systems are part of operational continuity because incidents and account questions outlive individual conversations. A request needs an identifier. Its history needs to remain available when staff change shifts. Knowledge needs to move from individual memory into shared records. Escalation and resolution need to be visible.

A more integrated tool can improve those conditions, but it can also centralize failure. If the system is unavailable or incorrectly configured, staff may lose access to the history they need. If automation routes a request incorrectly, the mistake can be repeated. The public record does not show how Host Depot managed those risks.

The decision also affects authority. A ticketing system determines who can see, modify, assign or close a request. A knowledge base determines which answers are standardized. Reporting determines which categories become visible to management. Tool selection is therefore partly an organizational-design decision.

Erskine's quotation links him to the replacement rationale. It does not mean he personally designed support workflows or evaluated every technical feature. The work would have involved support staff, administrators, vendor personnel and customers whose requests exposed the earlier limitations.

The 2011 record completes a visible arc from external packaging to internal operations. In 2006, Host Depot changed what it offered and how bandwidth entitlement was described. In 2007, it selected systems for dedicated-server management and merchant communication. In 2011, it changed the system through which its own service obligations were recorded and fulfilled.

AS15114 and the Durable Network Record

The current RDAP record for AS15114 is not an evaluation of any of those decisions. It identifies an autonomous system, HOSTDEPOT-ASN, and lists Host Depot as the registrant. It also identifies Mark Erskine as one validated individual technical contact.

That record performs a different function from the announcements. It helps make an Internet number resource and its operational contacts visible. It does not say whether Host Depot's marketing worked, whether Ensim was successful or whether SmarterTrack improved support. It records network identity and responsibility.

The distinction matters because registry evidence is often misused as a substitute for biography. A technical contact entry does not prove ownership, current executive authority or personal authorship of network changes. It is one operational relationship. In this case, its value is that it independently connects Erskine's name, Host Depot and AS15114.

An autonomous-system number is used to identify a routing domain in interdomain routing. The number does not own the traffic, the organization or the people associated with it. It provides a unique identifier through which routing policy and relationships can be expressed. Accurate registration supports coordination when networks change or problems occur.

The current record therefore supplies continuity without supplying a complete history. It shows that the Host Depot network identity remains represented in RDAP. It does not reconstruct the network's prefixes, upstreams, traffic or physical facilities during 2006, 2007 or 2011.

The private contact fields in the record are not reproduced here. Their presence in a registry does not make them necessary for a public profile. The supported public facts are the ASN, the network name, the registrant organization, Erskine's name, the technical role and validated status.

The record also sets a boundary on claims about the person. Erskine is not included merely because his name appears in a contact field. The dated source set independently links him to operating decisions. The RDAP entry then anchors those decisions in a continuing network identity. Without the decision records, the contact alone would be too weak for a long-form profile.

Conversely, the announcements would be easier to dismiss as aged promotional material without the registry anchor. The ASN record does not validate their outcome claims, but it confirms that Host Depot was associated with an identifiable Internet routing domain and that Erskine had a technical relationship to it.

This is the reality layer in the profile. The durable record is not a claim of sovereignty or institutional prestige. It is a practical identifier and contact relationship inside the running Internet. Its value depends on uniqueness, accuracy and continuity rather than on promotional language.

The unresolved question is how the record and operating responsibility evolved. RDAP supplies a current snapshot, not a complete change history for Erskine's role. Public evidence used here does not show when he became the technical contact, how responsibilities are distributed today or what succession arrangements exist.

Resource Accounting, Permissions and Continuity

The four visible decisions can be read as variations on one operating problem: how to turn technical resources into stable customer services while preserving an accurate record of rights and responsibility.

Bandwidth Bank concerned a measured allowance over time. The customer needed a credible account of unused transfer. Host Depot needed a system that could carry the balance forward and reconcile it with later use. The promise depended on continuity between measurement, billing and service enforcement.

Ensim Pro X concerned permissions over server functions. Providers, resellers and site owners occupied different levels of authority. A control panel had to expose appropriate actions without giving every user unrestricted control of the underlying system. The service depended on a hierarchy that was both usable and technically enforced.

RatePoint concerned a merchant's relationship with customer feedback. The platform had to associate reviews, responses and identity with the correct business. Host Depot acted as a distribution channel for the capability, while RatePoint controlled the underlying service.

SmarterTrack concerned continuity of support obligations. Tickets, answers and status needed to persist beyond one conversation. Access to the record had to follow staff roles. The system was meant to make support work less constrained by the earlier tool.

AS15114 concerned network identity. A unique number, registrant and technical contact made one routing domain identifiable to other operators. The record did not operate the network, but it supported the coordination on which continued operation depends.

Each layer demonstrates the limit of a record. A bandwidth balance does not transmit data. A permission does not administer a server by itself. A ticket does not solve a problem. An ASN entry does not route traffic. The record becomes valuable when it accurately corresponds to running systems and responsible organizations.

That correspondence can fail. Usage records can be wrong. Permissions can be too broad or too narrow. Support histories can be incomplete. Registry contacts can become stale. The public evidence does not identify failures of this kind at Host Depot, but the operating choices were designed around systems in which accuracy mattered.

Erskine's visible decisions repeatedly favored packaged systems and external platforms. That approach can reduce development time and provide specialized functionality. It also makes the provider dependent on vendor behavior, data models, updates and commercial continuity.

The alternative would have been to build more functions internally or retain manual processes. Public records do not show a formal comparison of those options. The observed choices suggest that Host Depot valued standardization and accessible interfaces, but that conclusion should remain tied to the selected systems rather than expanded into a psychological claim.

Operational continuity is the connecting result. The company wanted bandwidth entitlements to persist, server administration to be repeatable, merchant communication to be available and support history to be less constrained. The ASN record is the separate public trace showing that network identity also had to persist.

Allocation: Who Gained, Who Carried Risk

The 2006 repositioning potentially benefited customers by combining hosting with additional services and by allowing unused bandwidth allowance to carry forward. Host Depot potentially benefited by differentiating its offer and retaining more of the customer's online operations. Vendors and partners gained a route to Host Depot's customer base.

Those benefits remain potential because the accepted records do not supply independent adoption or financial evidence. The announcements describe what was offered. They do not show whether customers used every component, whether margins improved or whether the company retained users at a higher rate.

Bandwidth rollover shifted part of the timing risk to Host Depot. Customers gained flexibility across billing periods. The provider accepted the obligation to preserve balances and serve later usage within plan terms. The actual capacity effect would depend on aggregate customer behavior, which is not disclosed.

Ensim redistributed administrative work. Resellers and site owners gained access to common tasks through a control panel. Host Depot could standardize parts of provisioning and support. Ensim gained a customer and influence over a layer of Host Depot's service. Host Depot carried integration and vendor-dependency risk.

RatePoint redistributed reputation work. Merchants gained a tool for collecting and responding to feedback. RatePoint controlled the platform. Host Depot made the service part of its customer relationship. Consumers participated through reviews. The record does not show how disputes, false submissions or unfavorable feedback were handled in practice.

SmarterTrack redistributed support knowledge. A shared ticket and knowledge system could reduce dependence on one staff member's memory. Management could obtain reports. Customers could access a web interface. Host Depot carried migration, configuration and continuity risk during the replacement.

The ASN record reflects another allocation. Host Depot is the registrant organization. Erskine is the named technical contact. Other operators can use the registry to identify a responsible relationship. That visibility creates accountability, but it does not grant the contact unlimited control or make the registry the owner of the underlying business.

Across the decisions, employees and technical staff carried much of the execution burden. Product selection and executive explanation are visible because announcements name senior figures. Installation, migration, support and daily operation are largely invisible. It would be inaccurate to convert public visibility into total personal credit.

Customers carried transition risk as well. New panels, policies or support systems can require changed workflows. A tool intended to simplify service can create confusion if interfaces or records do not migrate cleanly. No accepted source reports such problems at Host Depot, so the risk remains structural rather than an allegation.

The balanced conclusion is that Erskine was publicly linked to choices that changed how capabilities and responsibilities were distributed. The records support analysis of those choices. They do not establish which entity captured the greatest economic gain or bore the largest realized cost.

Reputation and the Limits of Announcement Evidence

Host Depot's announcements describe the company in favorable terms. They refer to leadership, comprehensive solutions, quality, reliability, scalability and customer benefit. Vendor quotations reinforce that presentation. Those statements reveal the reputation the organizations sought to create. They are not independent measures of performance.

The profile does not use longevity alone as proof of success. A 2006 announcement says the company was entering its tenth year. The current RDAP record still shows HOSTDEPOT-ASN. Those facts establish persistence of names and records. They do not disclose revenue, profitability, market share, customer count or service availability.

The HostSearch item adds some independent publication context but not a full independent evaluation. It reports the RatePoint partnership and reproduces Erskine's explanation. There is no merchant survey or comparative review. Its strongest use is corroborating the date, role and existence of the decision.

The accepted evidence also lacks public failure records. That absence cannot be converted into a claim that every project succeeded. The records do not show how long Bandwidth Bank remained available, whether Ensim was later replaced, how RatePoint performed for merchants or whether SmarterTrack met the stated need.

An honest account therefore separates implementation from outcome. The decisions were announced. The systems or programs were selected or offered. The public evidence does not provide a complete post-implementation assessment.

This distinction protects both the subject and the reader. It avoids inflating marketing claims, but it also avoids inventing failures. The article can ask what evidence would be needed without treating missing data as adverse evidence.

For Bandwidth Bank, useful evidence would include archived plan terms, account-system documentation or customer records showing how balances were handled. For Ensim, useful evidence would include deployment duration, customer usage and later migration. For RatePoint, merchant adoption and response data would matter. For SmarterTrack, support response, resolution and migration evidence would test the stated rationale.

For AS15114, routing observations and historical registry changes could clarify how network responsibility evolved. The current RDAP entry alone does not show operational scale or topology. It remains a strong identity anchor and a weak performance source.

Erskine's public reputation in this source set is therefore attached to practical choices rather than broad acclaim. He explained a repositioning, a server-control selection and a support-system replacement. An independent trade outlet quoted him on a customer-communication partnership. A registry identifies him in a technical relationship to the company's ASN.

That is sufficient for a profile because the decisions connect to real operating surfaces. It is not sufficient for a verdict on his overall career. The profile remains deliberately narrower than the person.

What Cannot Be Attributed

The evidence does not establish that Mark Erskine founded Host Depot. Company descriptions say Host Depot was founded in 1997, but the accepted records do not provide a founding document or identify every founder. The article therefore does not assign him sole founder status.

It does not establish his current executive title. The president and chief-executive descriptions are dated 2006, 2007 and 2011. The RDAP record supplies a current technical contact relationship, not a current corporate office.

It does not establish current ownership or control. Registrant and technical-contact records are not equity records. A named executive in an old announcement may no longer hold the same authority.

It does not establish that Erskine personally designed Bandwidth Bank, configured Ensim, integrated RatePoint or migrated SmarterTrack. The source set links him to public explanations and choices. Technical and organizational execution belongs to a wider group that the records do not fully identify.

It does not establish the number of Host Depot customers, servers, employees or network sites. Promotional references to broad service or substantial use are not substituted for audited counts.

It does not establish measured cost savings from any system. Bandwidth Bank was described as saving overage charges, Ensim as cost-effective and SmarterTrack as capable of saving time or integration expense. No accepted source supplies a controlled comparison or financial result.

It does not establish reliability, security, uptime, latency or service quality. Those terms appear in commercial descriptions. They are not independently measured in the evidence used here.

It does not establish the current routing scale of AS15114. The RDAP record identifies the number and registrant. It does not show traffic, upstream diversity, prefixes, incidents or capacity.

It does not establish that all four decisions were parts of one deliberate long-term strategy. The sequence is visible in retrospect. The accepted records do not contain a master plan connecting them.

It does not establish that customers preferred the combined offer or the new tools. A customer quotation appears in the 2006 announcement, but one quoted experience does not establish a representative outcome.

It does not establish that vendor relationships remained stable. Ensim, RatePoint and SmarterTools controlled products or services on which Host Depot depended. Public records used here do not show renewal, replacement or exit.

These limits leave a useful core. Erskine was publicly linked to a set of dated operating choices. Those choices concerned packaging, resource accounting, administrative permissions, customer communication and support records. A current registry record links him and Host Depot to an autonomous-system identity. The evidence supports that chain and no larger claim.

Sources