Summary

  • Care Factor Computer Services Inc has substantial historical operating evidence: a federal corporate record, a Calgary business footprint, Alberta government payments, a documented security leadership role and the registration of AS16583.
  • The exact legal name ceased to be a standalone company after an amalgamation into Pivot Data Centres Inc in 2012. Current records attached to the old name therefore need successor and service-owner verification.
  • AS16583 remains active as an ARIN registration, while current routing aggregators report no announced IPv4 or IPv6 routes. That is evidence of a surviving identifier, not evidence of a live service platform.
  • Buyers and monitoring teams should separate historical identity, current legal accountability, network operation, data location and support ownership before treating the Care Factor name as operating assurance.

A name with more history than present tense

The first task is to establish what Care Factor was. The BTW directory entry supplies the name and a collection point for its public traces. Those traces do not describe a newly obscure startup. They describe a business that operated over decades, occupied commercial premises, appeared in public spending records and held an Internet number resource.

Corporations Canada's record for corporation 270355-6 says Care Factor Computer Services Inc was incorporated federally on March 28, 1991. It lists a Calgary registered office and shows annual returns filed through 2009. A Better Business Bureau profile gives an earlier business start date of February 1989, while a surviving company description says the business began that year as Computer Maintenance Corporation (Canada) Inc. The 1989 account is useful history, but it is not equivalent to the federal certificate. The defensible chronology is that an operating business claims roots in 1989 and the exact Care Factor federal corporation appears in 1991.

That distinction matters because infrastructure databases often collapse a brand, a legal corporation and a technical resource holder into one durable label. They are related, but they do not age at the same speed. A corporate name can disappear in an amalgamation while an autonomous system record, old customer inventory or procurement ledger continues to display it for years.

Public records establish a business, not just a label

Care Factor's service claims are broad. The company description preserved on a LinkedIn page now titled Roger's Data Centre calls Care Factor an IT infrastructure solutions provider headquartered in Calgary. It says the company delivered data-centre solutions to enterprise clients, mainly in western Canada, and extended its reach through partners in the United States, South America and Europe. This is promotional language rather than an audit. Even so, it tells us what the company said it sold and the customer segment it intended to serve.

Independent records make that description more credible. Alberta's detailed public accounts for the year ended March 31, 2010 list C$279,204 in payments to Care Factor Computer Services Inc. The total is distributed across several public bodies, including Finance and Enterprise, Housing and Urban Affairs, Agriculture and Rural Development, Energy, Environment, the Office of the Auditor General and Service Alberta. The document does not specify the products bought, the contract terms or the quality of delivery. It does establish that multiple provincial functions paid the company during the period.

A 2004 research report from Alberta's informatics research organisation iCORE identifies a Care Factor director responsible for e-security and business continuity planning. That single personnel listing cannot prove the maturity of the company's security programme. It does show that security and continuity existed as a named management responsibility, which is more meaningful than a generic claim to provide technology services.

The BBB profile places the business at 3015 5 Avenue NE in Calgary and classifies it across data systems consulting, computer repair, system design, data communications equipment, disaster recovery and computer-room equipment. BBB explicitly warns that profile information is not independently verified, so these categories should be treated as market-position evidence. They nevertheless align with the infrastructure, continuity and data-centre account found elsewhere.

There is also evidence of physical presence. Dundee REIT's 2010 annual report names Care Factor and Guest-Tek Interactive as significant tenants at Franklin Atrium in Calgary. It does not disclose Care Factor's exact leased area or prove that the building itself was a data centre. It does place the company in a named commercial property at the same moment that public accounts show provincial payments. Together, the records support the existence of an operating organisation, not merely a name copied between databases.

AS16583 is the strongest technical clue, and the easiest to misread

Care Factor's most concrete technical artefact is AS16583. An autonomous system number identifies a network that can present a routing policy to other networks. Possessing one is not the same as owning a data-centre campus, but it is a stronger signal of network responsibility than a marketing page.

ARIN's current registration for AS16583 names the autonomous system CFCS and records Care Factor Computer Services Inc as the registrant. The ASN was registered in August 2005. The registrant record carries the Calgary address also seen in the business profile. ARIN marks the registration active, while the ASN record itself was last changed in April 2016. Its current operations contact was refreshed in July 2026 and uses a different company domain and a Toronto address. ARIN also retains a comment pointing to a Rogers data-centre website.

Those details establish continuity of registry stewardship, but they do not tell a reader that Care Factor is currently announcing routes or answering customer incidents. Registry status and routing status describe different things. IPinfo's AS16583 page labels the network inactive and reports zero IPv4 addresses, zero IPv6 addresses and no current prefixes. IPGeolocation's current view likewise reports zero IPv4 and IPv6 routes. The apparent contradiction with ARIN's active label is therefore informative rather than fatal: the number remains a maintained registry entity, while the aggregators see no present routing footprint under that ASN.

A prefix page shows how legacy attribution becomes messy. IPinfo's record for 199.204.212.0/24 associates the range page with Care Factor and AS16583, yet its recent Calgary measurement identifies the responding address with Rogers Communications Canada. That observation does not prove ownership transfer, service continuity or a particular corporate transaction. It does demonstrate why a historical resource label should not be used as a shortcut to identify the current operator.

For asset discovery and vendor monitoring, the practical lesson is simple. "AS16583 exists" is a registry fact. "AS16583 carries Care Factor customer traffic" would be an operating claim requiring current route announcements, authorised resource records and service documentation. The frozen public evidence supports the first statement, not the second.

Corporate succession breaks naive identity matching

The legal record draws an even clearer boundary. The 1991 corporation is marked inactive because it amalgamated on December 1, 2009. Corporations Canada then created a second record, corporation 453914-1, under the upper-case Care Factor name. Its certificate states that the original Care Factor entity and 4517024 Canada Inc were combined in that transaction.

The second record is also inactive. Corporations Canada says CARE FACTOR COMPUTER SERVICES INC amalgamated into Pivot Data Centres Inc on August 1, 2012. This is the decisive identity fact. A document carrying the Care Factor name may be genuine and historically important, but it cannot by itself establish that a standalone company of that name is the present counterparty.

It is tempting to follow every later brand and domain reference and declare an unbroken chain of service. The evidence does not justify that leap. Corporate amalgamation establishes legal succession at a point in time. An ARIN comment pointing to Rogers and a present operations contact using another domain are clues to later stewardship. Neither tells us which organisation currently owes a particular customer a response, which contract survived, or which service estate remains in operation.

This is where automated entity resolution often goes wrong. A monitoring system sees the same company name in a 2010 payment ledger and a 2026 ARIN response, then reports a 16-year continuous vendor relationship. In reality, it has joined records across different legal and operational states. A sounder system keeps separate fields for observed name, evidence date, legal status, successor, resource identifier, current route origin and current operations contact. Mismatches should trigger review, not be silently normalised into a single "active company" flag.

A Calgary address does not settle data locality

Care Factor's Calgary roots are well supported. They do not establish where customer data sits today. A registered office is a legal address. A business address establishes presence. A tenancy record establishes occupation of commercial space. None, without a facility schedule or service contract, proves the location of servers, backups, support access or disaster-recovery copies.

The company's own description makes the question more important because it claimed reach beyond Canada through a partnership network. Partnerships can extend capacity and support, but they also expand the set of possible operators and jurisdictions. For a customer concerned with sovereignty, a historical Canadian headquarters should therefore begin the inquiry rather than end it.

Current assurance would require a named service provider, a facility and subprocessor list, data-flow and backup locations, rules for remote administrative access, and a contractual account of what happens during failover. It would also require dates. A 2010 building record cannot settle a 2026 workload-location question, however solid the old record may be.

Support is the missing operating layer

The public record contains people and functions from Care Factor's operating period. The BBB profile names historical business management. The iCORE report records a security and continuity role. The Alberta payments show that public bodies dealt with the company. These are useful signs that Care Factor once had a local organisational surface around its technology.

They do not provide a current escalation path. ARIN's operations contact shows that someone maintains the resource record, but a registry contact is not automatically a customer support desk. Nor does a Toronto address in that contact prove or disprove support capacity in Calgary. Support accountability has to be demonstrated at the service level.

For a buyer, auditor or incident responder encountering the Care Factor name, five checks would turn historical confidence into current assurance:

  1. Identify the legal counterparty and obtain the succession document that connects the old contract or asset to it.
  2. Confirm the live operations centre, support hours, incident channels and escalation owners through a current service document.
  3. Match any claimed network service to active prefixes, route origins and resource authorisations rather than relying on the ASN name.
  4. Verify facility locations, backup regions, subprocessors and remote-support jurisdictions for the specific service.
  5. Test the chain by opening a support case and recording who accepts responsibility, how quickly it is acknowledged and which organisation appears in the response.

These checks do not assume that a successor service is weak or that support has disappeared. They address a narrower problem: the surviving Care Factor records do not answer present-tense accountability questions on their own.

History is credible; operating assurance remains unproven

Care Factor Computer Services Inc deserves to be treated as more than a stray infrastructure label. The federal records, public payments, research-community role, business profile, premises and ASN collectively show an organisation with a real operating history in Calgary. In particular, AS16583 and the Alberta spending ledger provide independent technical and commercial weight.

But the same evidence also explains why the name must be handled carefully. The legal entity passed into Pivot Data Centres in 2012. The ASN survives in ARIN, yet current aggregators show no routes under it. Later operations and website references point beyond Care Factor without defining one current support owner for every legacy service.

The right conclusion is neither "fictional" nor "currently assured." It is that Care Factor is a credible historical infrastructure operator whose identifiers outlived its standalone corporate identity. Anyone relying on those identifiers today should demand the missing bridge from name to successor, from registry to live network, and from old local presence to current contractual support. Until that bridge is documented and tested, the public record is evidence of what operated, not a warranty of what operates now.