Summary
- Four hkix.net documents act on four different nouns: a port available at HKIX1b, HKIX1c and Satellite Sites; a connection carrying at most one IPv4 and/or one IPv6 address; a participant that must already be an autonomous system with its own data links; and an Internet Access Provider with an AS Number.
- The instrument is dated and the population is not. The charge table is v1.6, updated 2 Jan 2025 and printed twice in two currencies with no rate stated anywhere; the participant page's closing line is the literal string “Number of participants=” with no numeral in its retrievable text on three passes.
A port at HKIX1b is priced. A connection may carry one IPv4 and/or one IPv6 address. A participant must be an autonomous system with a globally unique AS number, its own data links and its own way out to the world. A participant list counts Internet Access Providers. Four instruments, four nouns, one site — and across the twelve first-party pages I read on 21 November 2026, not one sentence equates any two of them.
A correction first, and it is a change in what I read rather than a change in what I want to argue. When I reserved this piece I wrote that BTW's record held no Hong Kong exchange article at all. That sentence was false. Two briefings are already published: one in October on this exchange's two headings and four classes and no figures, and one in November on what an APNIC membership line can and cannot say about a switched fabric. Neither of those reads the charge table, the connection guidelines, the admission policy and the participant list as four instruments that must name the same counted object. That narrower test is the piece.
It is checkable against named pages, and it produces a stranger's question rather than an auditor's accusation.
The operator, printed two ways
The about page is unambiguous and undated: “Established in April 1995, Hong Kong Internet eXchange (HKIX) is owned and operated by the Hong Kong Internet eXchange Limited (a wholly-owned subsidiary of The Chinese University of Hong Kong Foundation Limited) in collaboration with Information Technology Services Centre (ITSC) of The Chinese University of Hong Kong (CUHK)” (What is HKIX). The policy page is equally unambiguous, equally undated, and names no company at all: “Hong Kong Internet eXchange (HKIX) is operated by Information Technology Services Centre (ITSC) of The Chinese University of Hong Kong (CUHK)” (Main Policies).
Two descriptions of who runs the thing, on the same site, with no date on either and no reconciliation in any of the twelve documents. I print both and adopt neither. A limited company described as a wholly-owned subsidiary of a university foundation, operating in collaboration with a university IT centre, is not the same statement as a university IT centre operating the exchange, and choosing between them from the brand, the domain or a directory card would be invention.
The same policy page does supply the settlement sentence that frames everything below: HKIX “is NOT a transit provider; instead, it is a layer-two settlement-free Internet exchange point primarily for routing of intra-HongKong Internet traffic.”
What the price acts on
The charge table is the most disciplined document on the site. It carries a version number, v1.6, and an update date, 2 Jan 2025, and it exists twice, in Hong Kong dollars and in US dollars, under that single version number (HKD table, USD table). Its columns are precise about their subject: under the spanning heading “Standard Port Charges”, the headings read “Port”, “Interface”, “Standard Interface”, “Availability” with three sub-columns “HKIX1b”, “HKIX1c” and “Satellite Sites”, then “NRC” and “MRC”. The billing period is stated in the definition, not guessed: MRC is “Monthly Recurring Charge”, and NRC is “Non-Recurring Charge (NON-refundable & NON-transferrable to other AS or other company under different name)”.
Eight port-and-interface rows, and the shape of them is worth counting rather than summarising. In Hong Kong dollars: GE LX/LH prints a waived non-recurring charge and 936 monthly; 10GE LR prints 17,940 and 7,800; 10GE ER prints 39,000 with the monthly cell blank; 10GE ZR prints 62,400 with the monthly cell blank; 100GE LR4 prints 35,880 and 31,200; 100GE ER4 prints 234,000 with the monthly cell blank; 400GE FR4 prints 62,400 and 93,600; 400GE LR4 prints 62,400 with the monthly cell blank. Four rows carry a monthly amount and four leave it empty. A blank cell is a blank cell — not zero, not free, not included.
Three more counts, mine, over those eight rows. Every HKIX1b and HKIX1c availability cell reads “Yes”. The Satellite Sites cell reads “Yes” three times, is blank three times, and reads “Some” exactly twice — the two 400GE variants. And three rows print “No” in the “Standard Interface” column: 10GE ER, 10GE ZR and 100GE ER4. Those are precisely the three interfaces the page itself names in its lead-time sentence, and all three carry a non-recurring amount with no monthly amount beside it.
The two currencies are the reason a reader can do arithmetic that the publisher does not do. Thirteen matched pairs across the two printings divide to exactly 7.8 — 936 by 120, 17,940 by 2,300, 7,800 by 1,000, 39,000 by 5,000, 62,400 by 8,000, 35,880 by 4,600, 31,200 by 4,000, 234,000 by 30,000, 93,600 by 12,000, and both discount amounts, 780 by 100 and 3,120 by 400. That quotient is mine, on their printings. Neither page states an exchange rate, a conversion basis, which currency governs, or a rounding rule, and I checked both pages on separate retrievals before writing that sentence.
What the table excludes is stated plainly and belongs in the same breath as the numbers, because it is the difference between a port price and the cost of a working connection. “The port charges listed do NOT cover local circuit/loop charges, cross-connect charges, satellite-site special connection charges, or any other charges needed for making the connection.” And for the third of the three named site classes: “For connections at Satellite Sites, special connection charges will be charged by relevant Satellite Site operators, in addition to the port charges charged by HKIX.”
HKIX prices two classes directly and publishes no amount for the third, because the third is priced by someone else.
The FAQ says the same thing in the voice of a help desk, and then hands the judgement back: satellite sites serve “the direct or indirect customers of the corresponding data centers which are satellite site operators”, and if you are not such a customer “you need to make your own judgement whether it is justified to connect to those satellite sites but not the two core sites as there is extra ‘Special Connect Charge’ involved” (FAQ). The same answer adds that there is no special connection charge when you connect directly to the two core sites or to the reseller's site — but that you still pay for the local circuits or cross-connect involved. The FAQ does not itself say HKIX's port charge still applies on top; the charge table supplies that sentence.
Two discount blocks, both narrower than a reader might hope. The Save-IP discount applies “ONLY if IP address is NOT needed for the port”, reduces the monthly charge by 780 for 10GE and 3,120 for 100GE, requires link aggregation over multiple ports, is “NOT applied to the 1st port which needs IP address”, and comes with a line that quietly caps the ambition: with link aggregation, “only card resilience can be provided but not chassis resilience and site resilience”. The volume discount is “applied under the same AS and the same contract ONLY” — 780 from the fifth 10GE port onward, 3,120 from the third 100GE port onward.
Neither discount applies to GE connections or to non-recurring charges.
What the guidelines admit
The connection guidelines act on a much smaller noun than a port and a much smaller noun than a network: a connection carrying at most one address of each family. “HKIX supports at most one IPv4 and/or one IPv6 address per connection to each participant on HKIX switch.” No trunk port, no VLAN mapping “at all HKIX sites”. Proxy ARP off on the interfaces facing HKIX. One MAC address per port. The switching and transmission equipment must be owned and operated by FTNS providers, and a formal agreement with HKIX is required for every connection (Connection Guidelines). None of that is unusual. All of it is about a different object from the one the price list bills, and different again from the one the policy admits.
What the policy admits
Here the admission test is written out, and it is severe in a way that makes the participant list's noun look odd. The peering model is “SKA (Sender Keep All)”. The exchange is “a settlement-free interconnection point”, and “no settlement needs to be paid by the peering participants for the incoming and outgoing traffic”.
A participant must be “an Autonomous System (AS) by itself with a globally unique AS number assigned by ARIN, RIPE-NCC, APNIC, LACNIC, AFRINIC or their sub-registries”; must be self-sufficient, with “their own primary DNS, Email, WWW and News servers”; must connect at 1Gbps or above; and “The data links to HKIX MUST be provided by the participants.” Most consequentially: “Each participant MUST have its own global Internet connectivity through other Internet access provider(s) independent of HKIX facilities. The connection to HKIX MUST NOT be used as the primary connection to the global Internet.
The key point is that if the link to HKIX or HKIX itself is down, connectivity should still be maintained.”
The page uses “primary”, not “sole”, and that distinction is the page's, not mine. It also insists on equality and on the route servers at once: “All participants of HKIX are considered equal”; “participants must only peer with these servers”; “All HKIX participants must peer with one another via the route servers”; while direct bilateral peering is allowed “as long as the arrangement does not violate any of the policies and guidelines stated here”, and nobody should filter traffic or routing entries to or from other participants “unless it is justifiable”.
So the admitted object is a network that already has a way out, has its own registry-issued identity, brings its own links, and is forbidden to lean on this exchange for its survival. That is a demanding noun. It is not the noun on the price list, and it is not the noun on the participant page.
What the count counts
The participant page introduces its table with a sentence that names the counted object exactly once: “The following Internet Access Providers have been directly connected to HKIX” (List of Participants). The columns are “Internet Access Provider”, “AS Number”, “GE Link(s) to HKIX”, “10GE Link(s) to HKIX”, “100GE Link(s) to HKIX”, “400GE Link(s) to HKIX”, “IPv6 Enabled”, “Blackholing for Anti-DDoS”, “MANRS”. The rows include the names a reader would expect — Akamai 20940, Amazon 16509, Cloudflare 13335, Meta 32934, Google Hong Kong 15169, Microsoft Hong Kong 8075, Netflix 2906, PCCW-HKT 4515, Telstra 4637, CUHK 3661 and 4641 — down to ZTE Corporation 135426.
And then the page ends. Its retrievable text finishes with the literal string “Number of participants=” and no numeral after the equals sign, on separate retrievals, including one that reached the final table row. That is a bounded absence over named passes, nothing more: I am not telling you HKIX has no count, and I am certainly not going to borrow one. A number rendered into that slot by a script, or drawn inside an image, would be a real number I did not see.
What I can tell you is what the page asks a reader to do with an Internet Access Provider carrying an AS Number: treat it as the unit of a population whose total is printed as a label.
That is the awkward join. An Internet Access Provider with an AS Number is not automatically an admitted participant under the policy, because the policy's test — independent global connectivity, own data links, self-sufficiency, not primacy — is not a column in the table. Nor is a participant the same object as a billed port, because the price list bills ports at named site classes and the policy admits organisations. Multiply the monthly 10GE amount by any count you like and you will get a number that is arithmetically clean and editorially worthless, because the two factors were never the same noun.
What the measurement publishes
The statistics page publishes its method and withholds its reading. Its only readable graph captions are “Daily' Graph (5 Minute Average)”, “Weekly' Graph (30 Minute Average)”, “Monthly' Graph (2 Hour Average)” and “Yearly' Graph (1 Day Average)” (Aggregate Switching Statistics). No traffic value, no unit, no axis maximum, no summary table and no update timestamp appears in the retrievable text, and no image alternative text came back with it. The intervals are public. The number the intervals qualify is not, in anything a text reader can open.
The prefix page goes one step further into honesty about method: it advises that a router's suggested maximum-prefix limit be “at least (monthly 2-hr average) / 0.7”, which is a real instruction with a real divisor — and it publishes no figure to divide (Number of Route Prefixes Announced). A reader is handed the formula and told to find the input elsewhere.
The one instrument that finishes its sentence
Against all that, the route policy is complete, and the contrast is the point. It names the route-server AS number, 4635. It sets the minimum accepted block at /24 and warns that improper announcements may lead to port suspension. It gives both community vocabularies in full — “Send prefix to all 4635:4635”, “Send prefix to $Peer-AS only 4635:$Peer-AS”, “Do not send prefix to all 0:4635”, “Do not send prefix to $Peer-AS 0:$Peer-AS”, and the large-community equivalents 4635:1:0, 4635:1:$Peer-AS, 4635:0:0, 4635:0:$Peer-AS — with the instruction to use one vocabulary or the other but “do not use both at the same time”. RPKI has been supported on the route servers “starting from mid-Jun 2020”, VALID is tagged 4635:65021, UNKNOWN is tagged 4635:65022 and then checked against HKIX IP address filtering or IRR filtering, and INVALID is rejected. Blackholing is not only permitted but labelled: the route servers “will accept the /32 prefix for blackholing” and tag it 4635:666 4635:65023 in the announcement (Route Policy).
Every value you need in order to predict what the exchange will do with your prefix is on that page, and every value you need in order to know what the exchange charges, admits or counts is on a different page under a different noun. The instruments that govern routing are complete. The instruments that govern money, membership and measurement are three halves of one answer.
What this leaves a reader holding
The two-layer structure is coherent once you stop expecting one number to do two jobs. Traffic settlement between peers is zero; the infrastructure service that carries it carries a monthly charge; the circuit, the cross-connect and the satellite operator's own special charge sit outside the table and are disclaimed in writing. A network can plan against that. What it cannot do is budget from a single sentence, or reassure anyone with a total, because the price list bills a port at a site class, the policy admits an autonomous system, the guidelines tithe a connection by address, and the list counts a provider.
The legitimate question is not who is hiding what. It is which document a stranger should read first, and the honest answer is that there is no document that reconciles them. HKIX has published a versioned, dated, two-currency price list and a participant page whose total is a label; it has published four averaging intervals and no retrievable value; it has published two descriptions of its own operator, neither dated. The record is not silent. It is four instruments, each scrupulous, none of them talking to the others — and one equals sign with nothing after it.
Member Briefing
Read the full trend briefing
Members read the full briefing with the source notes behind every finding.
Strategic Circle
A daily briefing in your language, built from changes we have verified.
Join for USD 20/monthCancel anytime.
Members also get the full research library, a daily briefing on the networks they follow and the private forum.






