How to Verify a Canadian ASN: ARIN Records, BGP and Hosting Evidence

What a Canadian ASN Can Actually Tell You

When I check a Canadian web host, I rarely start with its “Canadian servers” badge. I start with the network records. An autonomous system number, or ASN, can identify the organization responsible for an Internet routing system. It gives me a way to compare a hosting company's claims with a public technical record.

That doesn't make an ASN a certificate of Canadian ownership. The record tells me who registered a network resource. I still need to check the business behind it, whether the network is currently visible in BGP, and where the actual hosting equipment operates.

You can follow along with my ARIN Whois and ASN lookup tool. I'll use real records from the HostScout hosting reviews, including a Cloudflare example where the public-facing ASN gives the wrong impression about the origin infrastructure.

Canadian ASN Quick Facts

A number of old websites quote around 1,600 “active Canadian ASNs.” That figure is not a reliable 2026 count without a named BGP dataset, a measurement date and a definition of active. I prefer IANA's published country allocation summary for an attributable registry figure, while keeping it distinct from networks visible in the global routing table.

What an ASN Is, Without the Networking Jargon

Think of a website's IP address as a street address. An ASN is closer to the identifier for the road network that advertises how to reach a collection of addresses. Internet operators exchange these routing announcements through the Border Gateway Protocol (BGP).

A company might operate its own ASN and connect to several carriers. Another company might rent servers and IP addresses from a larger network without having an ASN at all. Both can sell hosting. Their infrastructure control, however, is not the same.

There are two ASN number formats, but they are part of the same global numbering system. A classic 2-byte ASN fits inside the 0 to 65,535 range. A 4-byte ASN extends the space through 4,294,967,295. For example, AS271 is in the old range, while AS401665 requires the expanded range. The number's length is not a ranking, a Canadian status flag or a measure of how advanced a provider is.

The important evidence comes from the relationships around that number: resource-holder registration, advertised IP prefixes, upstream connectivity, peering exchanges and the provider's legal and physical footprint.

ARIN vs. CIRA: Who Verifies Canadian Networks?

CIRA operates Canada's .ca domain registry. It does not issue Canadian ASNs or IP address allocations. That work generally falls to ARIN, the American Registry for Internet Numbers, one of the world's five regional Internet registries.

ARIN has served Canada since December 1997. Its published Org ID requirements contain a detail I think every Canadian hosting buyer should know: Canadian applicants must provide a tax identification number, for example a Canada Revenue Agency Business Number (CRA BN) or Quebec Enterprise Number (NEQ). ARIN also requires a signed Registration Services Agreement before approving the Org ID and may ask for documentation showing the entity is legally registered.

That difference is critical. Supplying a CRA BN or NEQ is not the same as ARIN publicly certifying a company's ownership structure. The number is also not normally displayed in public ASN lookup results, so readers cannot treat the public Org ID alone as evidence that a CRA database cross-check succeeded.

There is another point that surprises people: ARIN's current policy allows one ASN per organization on request. Requesting additional ASNs requires an appropriate technical reason or unique routing-policy justification. It is not an elite badge reserved only for the largest providers.

How a Canadian Company Gets Its Own ASN, and What ARIN Charges

Most small websites don't need their own ASN. Their hosting provider already manages the IP addresses and routing. The picture changes when a business runs a network with an independent routing policy, operates multiple carrier connections or wants to control how its own prefixes are announced.

ARIN's resource request guide allows an eligible organization to request one ASN. Extra ASNs need a specific routing-policy or technical justification. The process is to create an ARIN Online account, establish an Org ID and authorized contact, submit a request, respond to any verification questions, pay the applicable fees and sign the RSA.

The old US$550 ASN issuance fee disappeared in January 2024, when ASN-only holders moved into ARIN's annual Registration Services Plan. This means “an ASN costs $550 upfront plus $150 every year” is outdated. The right amount depends on the combined IPv4, IPv6 and ASN holdings attached to the Org ID. I used ARIN's 2026 fee schedule and its published 2027 schedule for these figures.

From BCNET's AS271 to Modern Canadian Hosting Networks

Canadian networks were using autonomous system numbers long before most small businesses had websites. One early example is BCNET's AS271, registered on February 24, 1989. Its role in British Columbia's research and education connectivity is a useful reminder that Canada's Internet infrastructure did not begin with the commercial hosting boom.

I would not use a low ASN as proof of a better company. Nor would I consider a six-digit ASN suspicious. Some of Canada's longest-running networks have short numbers simply because of when they were allocated.

How to Check if an ASN Is Canadian in Five Steps

Here's the workflow I use when an IT buyer asks whether a hosting company is genuinely operating a Canadian network.

These checks answer different questions. A good audit keeps each piece of evidence separate until the claims line up.

Read a Real ARIN Record: WHC's AS400262

WHC is a useful case study because the company has a registered network identity, while its public website also uses a CDN. ARIN lists AS400262 to WHC Online Solutions Inc., under organization ID WOS-29, with a Montréal registration address. That is a specific, checkable Canadian network record.

This is a simplified summary using identifiers checked against ARIN. It is not a live WHOIS transcript. Recheck the current record before using it in an audit.

ASNumber:   400262
ASName:     WHC
OrgName:    WHC Online Solutions Inc.
OrgID:      WOS-29
City:       Montréal
StateProv:  QC
Country:    CA
RegDate:    2021-11-29

# Registry identity, not a data-centre certificate.

For a developer who wants the underlying data, ARIN exposes a structured RDAP endpoint. This is the modern machine-readable counterpart to older text WHOIS lookups.

curl -L -H 'Accept: application/rdap+json' \
  https://rdap.arin.net/registry/autnum/400262

RDAP can confirm the registered ASN and related entities. It does not prove that AS400262 is currently originating a particular IP prefix. For that, I check a routing collector or a live BGP tool separately.

Find an ASN from the Command Line

My ARIN lookup is easier when you just want to check a provider. If I need a result in a terminal or troubleshooting notes, I use these read-only commands. The first looks up the registered ASN. The second starts with an IP address and returns a BGP-derived origin ASN.

whois -h whois.arin.net "a 400262"

whois -h whois.cymru.com " -v 1.1.1.1"

The IP above is a public resolver address used as a demonstration, not evidence about a Canadian host. Replace it with the IP you are investigating. Team Cymru documents that its country code comes from registry data, not proof of where the server is physically located. See the IP-to-ASN service instructions.

On systems without the whois command, install an appropriate WHOIS client first. On Windows, the built-in browser-based lookup or ARIN RDAP can be simpler than adding terminal utilities.

Six Free Tools for ASN and BGP Investigations

I don't use one website for every part of an audit. Different tools answer different questions. These are the resources I would bookmark alongside HostScout's own network checker.

The Cloudflare CDN Illusion: AS13335 vs. AS400262

Consider whc.ca. The website's public DNS can resolve to Cloudflare addresses, whose network is AS13335. Cloudflare's own documentation explains that its proxied DNS records return Cloudflare IP addresses rather than the real origin IP. That is exactly what a CDN is designed to do.

Meanwhile, WHC has a separate ARIN record for AS400262. Those two facts can both be true. A public Cloudflare lookup doesn't tell us where WHC's origin is located, and WHC's registered ASN does not prove the proxied website's hidden origin uses that ASN.

Cloudflare explains this proxy behaviour in its official IP-address documentation. It is why I never label a Canadian website “US hosted” solely because the edge ASN is registered to a US company.

Three Traps That Distort Canadian ASN Lookups

When I need a stronger conclusion, I check the public registry records, provider statements, traceroutes and physical facility evidence together. I explain those layers in my hosting verification methodology.

Canadian Web Host ASNs: A Reference Table

These ten examples link to my HostScout review library. Most are Canadian-registered network operators; HostPapa AS23273 is a US-registered counterexample. I have kept the registry location separate from the server location, and flagged InCentre’s recent transfer so readers do not confuse a historical Org ID with the current operator.

Registry names and Org IDs can change after mergers, transfers and record updates. Treat the table as a dated research index, not as a live feed. Use the ARIN lookup to recheck the ASN before using it in procurement or compliance documentation.

What TorIX and ONIX Add to a Network Audit

ARIN tells me a registered network identity. An Internet exchange adds a different kind of evidence: whether a network participates in a place where networks exchange traffic with each other.

For example, the Toronto Internet Exchange's public peer list includes HostBilby Inc. under AS401665. PeeringDB also lists a connection at ONIX. Those records help document Canadian network interconnection, but they don't show the whereabouts of every customer server or guarantee that all routes stay inside Canada.

One last technical trap: peering and transit are not the same thing. An exchange membership can establish a local interconnection point, while upstream providers carry reachability to the rest of the Internet. Both relationships can appear in network tools, and neither is a physical server inventory.

Advanced Check: ASN Registration Is Not RPKI Validation

Once I've found an ASN in ARIN, I sometimes add a routing-security check. Resource Public Key Infrastructure (RPKI) allows an address-space holder to authorize an ASN to originate specific IP prefixes through a Route Origin Authorization, commonly called a ROA.

ARIN's ROA documentation defines the authorization as an origin ASN, a prefix and a maximum permitted prefix length. A valid ROA supports routing security; it still doesn't certify that the company is Canadian-owned or owns the physical building.

For a practical check, look at a route's RPKI status in a BGP viewer such as bgp.tools. The values you see are a snapshot and should be rechecked when investigating a current incident.

A Short Checklist for Canadian Hosting Buyers

If I had to audit a new hosting provider quickly, this is what I would record before reaching a conclusion.

For this work, my hosting verification tools are a useful starting point. They reduce the amount of manual registry searching, but they don't replace the other evidence. You can also browse Canadian-owned web hosting companies on HostScout and open each review to see how the same checks apply to a real provider.

Canadian ASN FAQs

ASNs in Canada: IPv4 Address Footprint

Large access networks such as Bell, Rogers and TELUS announce far more IPv4 addresses than a typical independent web host. This view helps put Canadian routing into perspective. The numbers represent addresses associated with an ASN in the selected dataset. They do not measure how many servers a company owns or how many IP addresses are physically in Canada.

Sorted by the number-of-IPs column in the supplied October 24, 2026 CSV. Duplicate ASNs are counted once. Rankings and address totals depend on the data provider’s coverage and can change over time.

As with the 2,616 ASN figure visible in that screenshot, country totals vary among IPinfo, ARIN allocation reports and BGP collectors because each uses a different methodology. For a hosting audit, I care more about the specific resource holder and its currently advertised routes than a national league table.

What I Look for Beyond the ASN

I like ARIN records because they give hosting research a paper trail. They connect a network number to an organization and provide a starting point that a buyer can reproduce. When that name matches corporate filings, current BGP data and a credible Canadian facility record, the case becomes much stronger.

Still, an ASN is one part of an infrastructure audit. It is not a passport for a server, a share-ownership register or proof that traffic never crosses the border. Using it properly means knowing both what it proves and where it stops.

Research reviewed October 24, 2026. Counts, routing paths and company records can change. This guide is technical background for due diligence, not a legal certification of any company or data-residency arrangement.