Summary

  • APNIC's public member listing prints the exact string 'Telstra International Limited' against the membership category VERY LARGE and the economy HK; APNIC-121 defines that category by chargeable address space held at the anniversary of joining and converts it into 32 votes at Member Meetings.
  • The registry objects that carry the entity's authority are older and narrower than the label: the AS4637 aut-num prints the registrant and no address blocks at all, the registrant organisation was registered nine years after the AS number, and APNIC's transfer policy hands the power to move a resource to the currently registered holder — who initiates — with the recipient left to acknowledge within 30 days.

The row as printed

APNIC publishes a member directory in which each member occupies a row with three printed values. The columns are headed 'Name', 'Membership category' and 'Economy' (APNIC Members, listing page). The same page states what the category means operationally: membership tiers correspond to the number of IP address resources each organisation holds rights over.

One paginated segment of that listing, anchored after the entry for Telikom PNG LTD, contains the exact string 'Telstra International Limited', printed against the membership category 'VERY LARGE' and the economy code 'HK'. A neighbouring row in the same segment reads 'Telstra Limited EXTRA LARGE AU' (APNIC Members, segment read 21 November 2026).

Two rows, two name strings, two categories, two economies. Nothing in the listing segment read states that these two rows relate to one another as companies. A registry row is a member account with a printed name; corporate parentage is not a field of the listing. Anyone who wants to argue that the Telstra group's registry presence is one thing will have to argue it from documents that are not this table.

The segment is one page of a dynamic, paginated directory, and that is the first boundary of this piece: what is quoted here is a dated observation of one page, not an extract of the whole directory. The company also has a standing entry in our own directory, which records the card as APNIC prints it rather than the documents behind it (Telstra International Limited in the BTW directory).

What the label is a measure of

The governing document is APNIC-121, 'Membership: Tiers and voting rights', Version 002, dated 28 March 2024, status ACTIVE, effective from 1 January 2010 (APNIC-121, Version 002). It does not describe a company. It describes an assessment.

APNIC membership comes in seven tiers: Associate, Very Small, Small, Medium, Large, Very Large and Extra Large. A Member's tier is determined by the amount of chargeable address space that Member holds as of the anniversary of its date of joining APNIC as a Member. Total chargeable IPv4 and IPv6 holdings are assessed, and the document is explicit that resources which are not charged — some historical resources and experimental allocations — are not counted when the tier is set.

Very Large covers IPv4 greater than a /13 up to and including a /10, or IPv6 greater than a /26 up to and including /23, and where both families are held the larger resulting tier is effective.

Read that twice, because it disposes of the most common misreading. The label is not revenue, headcount, market share, customer count or network reach. It is a band in a prefix table, sampled once a year at a date fixed by the member's own joining anniversary, from the subset of holdings APNIC actually charges for. An organisation can lose money all year and keep the label. An organisation can shrink its network and keep the label, provided the chargeable holdings still land in the band on the day of assessment.

APNIC's explanatory membership page says the same thing in plainer words and slightly looser ones: address space holdings are reviewed at membership renewal each year to determine the member's tier, and where a member holds both families the higher of the two resulting tiers is effective (APNIC, how the membership structure works). The looser wording matters for precision: the public explainer drops the formal document's repeated qualifier 'chargeable' and frames the assessment as renewal-based rather than anniversary-based. When the two disagree, the document governs, and the difference is worth knowing if a due-diligence file ever turns on which holdings counted.

The second consequence is the one nobody quotes. If the label is set once a year, then every day between assessment dates is a day when the printed category is a fact about the past. A row read today reports a measurement taken at the last assessment, not a measurement taken today.

The vote ladder behind the badge

The category is not decorative. APNIC-121 attaches votes to it. The Very Large tier carries an entitlement to 32 votes at APNIC Member Meetings; Associate carries 1, Very Small 2, Small 4, Medium 8, Large 16, and Extra Large 64. The same document states that all Members have equal access to the core services of APNIC, and that voting entitlements are determined based on the tier structure.

That is a clean split, and it is the heart of this story. On services, the registry says equality. On governance, it says a ladder. The organisation printed as VERY LARGE in Hong Kong sits one rung below the top of that ladder and thirty-one votes above the bottom, and it holds those votes because of a prefix band rather than because of anything a customer, a regulator or a shareholder did.

An address-space measurement converting into a governance right is not a scandal. It is a design choice with a long pedigree: those who hold the most of a shared resource carry the most weight in decisions about it. But it does mean that a member category printed beside a company name is simultaneously a resource classification and a political fact, and that the same row answers two completely different questions depending on which column you are reading.

Three dates, one entity

Now go to the records that carry the entity's authority, and the single row splits into several objects with separate clocks.

APNIC's RDAP service returns an aut-num object for AS4637 with the registry name ASN-TELSTRA-GLOBAL, country HK, status active, and a description remark reading 'Telstra Global'. Its registrant is the entity handle ORG-TIL3-AP, whose formatted name is 'Telstra International Limited'. The object's own events are a registration at 2008-09-04T06:40:31Z and a last change at 2020-05-26T20:29:57Z (APNIC RDAP, autnum AS4637).

Read the registrant organisation in its own right and the clock jumps. ORG-TIL3-AP records a registration at 2017-08-08T23:24:09Z and a last change at 2023-09-05T02:15:55Z (APNIC RDAP, entity ORG-TIL3-AP). The plain-text registry rendering of the same object gives the field set: org-name Telstra International Limited, org-type LIR, country HK, maintained by APNIC's home master, last modified 2023-09-05T02:15:55Z (APNIC WHOIS, ORG-TIL3-AP).

So the AS number was registered in 2008 and the organisation that now stands as its registrant was registered in 2017. Neither date is an allocation date, and neither is the date the company was formed. They are the birthdays of two database objects that happen to reference each other. An inference that the network is nine years younger than its AS number, or that the company is nine years younger than its routing, would be an artefact of reading one object's history as another's.

The third layer sits lower still. In the inspected portion of the entity response, a networks array lists IPv4 networks whose own events carry their own dates: 203.120.164.32/27, economy SG, status ASSIGNED NON-PORTABLE, registration 2008-09-04T06:50:50Z; 203.152.38.0/25, SG, ALLOCATED PORTABLE; 42.99.128.0/17, JP, ALLOCATED PORTABLE, registration 2011-03-15T06:56:59Z; 58.145.192.0/19, JP (APNIC RDAP, entity ORG-TIL3-AP, networks array). Network remarks in that response read 'Telstra Global Internet Services Network Blocks' and 'Service Provider Block'.

Three clocks, then: an AS number registered in 2008, an organisation registered in 2017, and individual network objects registered in 2008 and 2011. A registry does not keep one biography of a company. It keeps a set of objects that reference one another, each with its own creation date, and the only way to read it honestly is to keep the objects apart.

One limit belongs here rather than in a footnote. The entity response as retrieved was truncated after the networks array, so trailing fields were not inspected, and no parent-company, group or ownership field appeared anywhere in the portion that was read. That is a statement about a truncated document, not a finding that the registry has no such concept.

The AS number that lists no addresses

Here is the detail that makes the whole piece worth writing. The aut-num object for AS4637 contains no IPv4 or IPv6 address-block list, no CIDR prefix list and no route objects. The only numeric range it prints is the single-ASN range 4637 to 4637 (APNIC RDAP, autnum AS4637).

An autonomous system number is an identifier, not a container. It says who is authorised to originate routes under that number. It does not enumerate the prefixes that will be originated. A reader who wants an address inventory has to go to network objects, route objects or routing data, and each of those is a different ledger with a different authority. Confusing the identifier with the inventory is the single most common error in registry-based due diligence, and the APNIC record is laid out in a way that punishes it: the object that most looks like a network profile contains no network.

That distinction has an operational consequence. Registration, authorisation and announcement are three separate facts. A registry entry records who holds a resource. A routing table records what is being announced right now. Neither one proves the other, and a company can hold a registration for years while announcing nothing, or announce space it does not hold until somebody notices. The APNIC aut-num tells you about authority over a number. It tells you nothing about what that number currently carries.

Where the record stops

The same discipline applies to what the label is asked to prove in commercial conversation. The row establishes that a member account named Telstra International Limited is printed in APNIC's public directory with the category VERY LARGE and the economy HK, and that the tier is computed from chargeable address space at an assessment date. Full stop.

It does not establish what the company sells, whom it serves, where its network runs, how many people it employs, what it earns, or whether the brand on its invoices matches the name in the register. No chargeable-holdings total appears in the material read for this piece, no address count, and no recomputation of the tier from an outside aggregate — which is why none is printed here. Any figure of that kind would be an arithmetic guess wearing a registry citation, and the tier's own definition excludes non-charged historical and experimental space, so an outside total would not even be measuring the right quantity.

What the record does establish is one very specific and rather useful thing: which legal entity the registry will treat as the holder when something needs to move.

Who can move a registration

That question is answered by APNIC's resource policy, not by the member listing. APNIC-127, Version 015, dated 20 February 2025 and marked Active, sets conditions on the source of a transfer. For IPv4 within the APNIC region, the source entity must be the currently registered holder of the IPv4 address resources, and must not be involved in any dispute as to the status of those resources. For ASNs, the source entity must be the currently registered holder of the ASN, and likewise free of dispute as to the resource's status. Intra-APNIC IPv4 transfers run between current APNIC account holders, and a recipient already holding IPv4 resources must demonstrate a 24-month use plan, show its past usage rate and provide evidence of compliance with APNIC policies on past delegations (APNIC Internet Number Resource Policies).

The definitions section is where the unit of account becomes unambiguous. The source in a resource transfer is 'the organization which, prior to the transfer, is the legitimate holder of the resources to be transferred', and where that source is in the APNIC region it must be a current APNIC account holder (APNIC-127 v015, plain text).

An organisation. An account holder. Not a group, not a brand, not a beneficial owner sitting two holding companies above the register. APNIC's own operational page says it in one sentence: a transfer occurs when internet number resources are moved from one legal entity to another, and a transfer is different from an organisational legal entity name change (APNIC, transfers).

That single distinction is worth a paragraph of its own, because it is where deals go wrong. Renaming the company that already holds the resources is not a transfer. Moving the resources to a differently named company is. The registry does not care what the group calls the business; it cares which account holds the object.

Two routes, two evidentiary thresholds

The procedure has a shape, and the shape is asymmetric. For a transfer between APNIC accounts, the source account must initiate in MyAPNIC, and the recipient account must then acknowledge (APNIC, transfer of unused IPv4 and/or AS numbers between APNIC accounts). The guide repeats the rule and adds the eligibility condition — both parties in the APNIC region must be APNIC account holders — and the clock: the recipient acknowledges within 30 days or the request is cancelled (APNIC IPv4 Transfer Guide).

Note who holds the initiative. The source initiates. Not the buyer, not the parent, not the party with the commercial interest in the space. The party that already holds the registration is the party that must start the process, which means a would-be acquirer of an operating business cannot move a registration unilaterally no matter how much it has paid for the company around it.

The merger, acquisition and reorganisation route looks different in exactly the place you would expect. The source account still initiates. But now relevant legal documents must support the transfer — for example a Sales/Transfer Agreement — and those documents must be issued by the governing authorities in the economies where the entities reside. The organisation taking over must have its own APNIC account, and APNIC will update the WHOIS records to reflect the new organisation's management (APNIC, transfer due to merger, acquisition or reorganization).

Compare that with the ordinary route's paperwork. APNIC's help-centre walkthrough of the standard transfer form has the source select the resources, choose how WHOIS objects will be handled, give a short reason for the transfer and name the recipient account; the recipient supplies need information or a pre-approval (APNIC Help, submit and accept a transfer). No signed-agreement upload appears as a step in that walkthrough. The absence of a step in a help article is not proof that APNIC never asks for documents case by case — but it is enough to say that the two published routes are not equivalently documented, and that the heavier evidentiary gate is the one attached to a change of the holder itself.

What a buyer actually inherits

Put the pieces together and the commercial reading is uncomfortable but clean.

A buyer of an operating company acquires contracts, plant, people and customers. It does not automatically acquire the registry registrations, because those belong to whichever legal entity is the account holder. If the holder is Telstra International Limited and the buyer's vehicle is a different company, the space moves only by transfer, and a transfer needs the source to initiate. The heavier route exists for exactly this case, and it ends with the registry rewriting the WHOIS to name the acquiring organisation's management.

That is what makes the label beside the row less interesting than the row's identity. The VERY LARGE category is a band that follows the chargeable holdings on an assessment date; it can change without anyone buying anything, and it can survive any number of corporate events. The holder string is the part with consequences. It determines who must press the button, whose account must acknowledge, and which name the registry then publishes as the manager of the resources.

Which also explains why this row is a poor proxy for size and a good proxy for authorisation. If the question is how big the business is, the member listing answers nothing. If the question is who can lawfully move a registration tomorrow morning, the listing plus the organisation object plus the policy answers it precisely: an organisation, with an account, currently registered as the holder, not in dispute, which must start the process itself while its counterparty has thirty days to accept.

What the row cannot be made to say

Six months of due-diligence decks have taught a generation of analysts to treat a registry lookup as a substitute for a disclosure document. It is not, and the discipline that keeps this piece honest is worth stating plainly, once.

A registry is a record of authorisations, not a record of business performance. The member category is a prefix band sampled annually. The aut-num is an identifier without an inventory. The organisation object is a name, a type, an economy and a maintainer, with its own creation and change dates. The transfer policy is a procedure for changing the holder. None of these four things will tell you the revenue of a Hong Kong connectivity business, the size of its network on the ground, or whether the brand on its website matches the entity in the register.

What they will tell you, with a precision that no marketing page can match, is who the registry considers responsible for a number, and what has to happen before that changes. In a market where address space is scarce, that is not a small thing to know.