Summary

  • NKtelecom INC is recorded as a Florida Profit Corporation filed on 3 May 2022, and the network two routing directories attribute to it, AS216475, is registered under RIPE and originates 36 IPv4 and 6 IPv6 prefixes.
  • RIPE NCC's published eligibility test turns on where an organisation provides services rather than where it is incorporated, so a company that sells servers in Amsterdam and Frankfurt sits inside the rule; what governs its holding is an agreement, not a nationality.
  • CAIDA counts a customer cone of one ASN against three transit relationships and zero customers, which makes this a leaf that buys all of its reach from three other networks.

What the registry prints

Read on 17 November 2026, the BGP.tools record for AS216475 is short and unusually specific. The network was registered on 14 August 2023. It is registered to organisation handle ORG-NI123-RIPE under RIPE, its status is Active, its allocation sits under RIPE, and BGP.tools classifies its network type as Eyeball. It originates 36 IPv4 prefixes and 6 IPv6 prefixes. It reaches the rest of the internet through exactly three upstreams: AS48729 ServerKing B.V., AS19318 Interserver, Inc and AS56630 Melbikomas UAB (BGP.tools).

The company behind that handle keeps its papers in Florida. The business-entity record lists NKTELECOM INC as a Florida Profit Corporation in St. Petersburg, filed on 3 May 2022 under document number P22000037722 (business-entity record). The filing predates the AS registration by about fifteen months, which is the ordinary order of events: incorporate first, apply for numbers once there is a network to justify them.

One gap matters. The BGP.tools passage prints the organisation handle, not the company name. That link is supplied by two routing directories, IPinfo and Hurricane Electric's BGP toolkit, both of which carry NKtelecom INC as the organisation for AS216475 (IPinfo; Hurricane Electric BGP toolkit). Two independent directories agreeing is solid corroboration and it is not the registry's own object. The distinction is worth keeping because the rest of this piece turns on which document actually binds.

Where it sells

The company's own site answers the geography question without being asked. Its front page is titled "NKtelecom: Cloud VPS & Dedicated Servers in the US & Europe" and states that NKtelecom offers servers in New York, Amsterdam and Frankfurt (nktele.com). Three cities, two continents, one product line.

That matters because of what RIPE NCC publishes about who may join. Its service-region page says the region "is made up of over 75 countries", that "[o]rganisations that provide services in any of those countries can become members of the RIPE NCC in order to receive Internet resources", and that organisations providing services outside the region "are advised to contact the RIR responsible for their country if they want to receive Internet resources" (RIPE NCC service region).

The test is written around service provision. Amsterdam and Frankfurt are inside that region by the company's own account. A Florida corporation selling capacity in the Netherlands and Germany therefore did not need an exception, a waiver or a special reading of the rules. It met the rule as drafted.

That corrects a tempting story. A US-incorporated holder in a European registry looks like a jurisdictional seam — the wrong company in the wrong rulebook. On this evidence it is nothing of the kind. The published eligibility language is not a residency requirement and not a nationality test.

What actually binds the allocation

Strip out the geography and something more consequential is left. RIPE NCC's own description of its number-resource framework separates resources held by members from resources that can be held by non-members, such as Independent Resources, which may require a sponsoring LIR. It describes policy implementation, assisted registry checks and compliance procedures, and ties the specific non-renewal or revocation route to the type of resource and to the agreement in force — the Standard Service Agreement or a Sponsoring LIR Agreement (RIPE NCC number resources).

Read that as an operating mechanism rather than a policy page. Whatever NKtelecom holds, it holds through a contract with a counterparty that can review the holding and, in the right circumstances, end it. The exposure is contractual and procedural. It is not that the company filed in the wrong country.

Which of the two instruments applies here was not established from the documents read. Membership and sponsoring-LIR status are different arrangements with different obligations, and nothing in the material this piece rests on says which one attaches to ORG-NI123-RIPE. That single unanswered fact decides which agreement a customer, a lender or an acquirer would need to inspect.

Three upstreams and nothing below

CAIDA's AS Rank view of the same network is the second half of the story, and it is less flattering than a 42-prefix origination count. The customer cone is one ASN, 29 prefixes and 8,192 addresses. The degree is 3: three transit, zero provider, zero peer, zero customer (CAIDA AS Rank).

8,192 addresses is exactly one /19. Three transit relationships and no customers is a leaf: a network that announces its own space and hands every packet to somebody else to carry. The three upstreams named by BGP.tools are the same three relationships CAIDA counts. Origination is presence. It is not reach, and it is not market power.

Two details sit awkwardly beside each other and neither is resolved here. BGP.tools labels the network type Eyeball, a category usually attached to access networks serving end users, while the company's shop window sells cloud VPS and dedicated servers. And the 36 IPv4 prefixes this network originates are not the same measurement as the 29 prefixes inside its cone; the first counts what it announces, the second counts what sits downstream of it. Both numbers are reported by their sources. Neither is quietly dropped to make the arithmetic tidier.

The awkwardness is itself informative. A registry record describes a holder; a routing record describes a footprint; a sales page describes an offer. Here the three line up on identity and diverge on characterisation, which is exactly what a market made of small hosting operators looks like from the outside.

The record I could not read

Two attempts to read the registry's own aut-num object for AS216475 and its organisation object for ORG-NI123-RIPE returned no quotable passage on 17 November 2026. Neither the RDAP endpoint nor the database web query produced text that could be reproduced here. Those objects were not obtained from the material read. That is a limit of this reading, not a finding about the registry, and it is not evidence that the registry declines to name a holder.

The consequence is precise. The registered name, the stated address, the object creation and last-modification dates, and the administrative and technical contacts for ORG-NI123-RIPE remain outside this piece. Anyone who needs them should read the objects directly rather than infer them from a routing directory.

What the numbers are worth

This desk has already treated NKtelecom's prefix announcements and upstream relationships as watchpoints. What those watchpoints hang on had not been established: not a passport, and not a European address, but an agreement with a registry and a dependency on three carriers.

Both halves point the same way for anyone buying from a company like this one. Continuity of addresses is a contractual question before it is a technical one, and reach is somebody else's engineering. NKtelecom originates its own space, serves three cities across two continents, and owns almost none of the path between them. If you want to know what could take its addresses away, the incorporation papers are the wrong document. Ask for the agreement. What this desk tracks on the company sits in the NKtelecom directory entry.