Summary
- NL-ix advertises "A way to reach ~2.400 Peering networks with a single port" and states in words that it "covers the Transport between locations"; no page read prices an inter-site link, a second site or a cross-connect.
- Across twelve nl-ix.net documents read on 21 November 2026, the only currency amounts are one London promotional block: 10G = 425 EUR, 100G = 2500 EUR, 400G = 5500 EUR, "based on 24 months", with no billing period stated and a signing deadline of 30 june 2026.
- The cross-connect into the fabric is the customer's to arrange and pay for, and optics beyond the standard single-mode default carry an additional charge with no amount printed.
A distributed Internet exchange is an awkward thing to price, because what it sells is not a place. It sells the right to appear at many places at once. NL-ix runs that model across Western Europe, and its pages are unusually articulate about the many places and unusually quiet about the price of the once.
What the single port promises, in words
The peering page states the proposition without ornament: "A way to reach ~2.400 Peering networks with a single port." The saving is then described rather than priced. Connecting to this fabric, the page says, "saves the complexity and hassle of connecting to multiple Internet Exchanges and saves costs as NL-ix covers the Transport between locations." A third sentence separates NL-ix's own inter-site transport from the transport a customer would otherwise buy to reach other exchanges: "All it takes is a single port to gain access to the content your end-users want, cutting out the need for multiple ports with IX's and Transport costs to and from these exchanges."
That is a careful set of distinctions, and it is worth holding onto all three. The first sentence is a count. The second is a service description. The third is a comparison against a cost the customer would otherwise carry. None of them is a rate, and none of them tells you how many of those places your port actually reaches under the standard fee.
The network architecture page adds the physical picture in approximate terms: "The footprint of NL-ix covers ~100 datacenters located throughout Western Europe." Every point of presence, it continues, is "connected to at least one core location". Amsterdam is described as the largest core site and, in the same breath, as three of them — "The largest core site of the NL-ix network is in Amsterdam and consists of three core sites" — a sentence that uses one noun for the container and its contents. Other international core locations "consist of two sites that are redundantly connected to other core locations", and the backbone "uses wavelengths with capacities up to 400 Gbps".
The locations page then lists places rather than facilities, and lists them without a total. I counted seventeen metropolitan headings in the retrieved text — Amsterdam, Arnhem, Berlin, Brussels, Copenhagen, Dublin, Düsseldorf, Eindhoven, Frankfurt, Groningen, London, Luxembourg, Marseille, Munich, Paris, Rotterdam, Stockholm — with sub-places such as Almere, Utrecht, Slough, Delft and The Hague hanging beneath them. The page asserts that "All NL-ix locations are seamlessly interconnected over our low-latency European fabric", and prints no number of locations, data centres or facilities. Its statistic components were placeholders in every retrieval.
So the reach arrives twice, as two different objects. About a hundred data centres on one page. Seventeen named metropolitan areas on another, with no count at all. Nothing in the documents read converts one into the other, and no page states how many sites a base port fee reaches.
The connected networks page is candid about its own categories — it distinguishes networks connected to the fabric from Peering members — and then renders its list in the browser: "The ConnectedNetworks component will render here." No count of networks, of members or of facilities is printed in the text a reader or a crawler receives.
What it costs, in one block
Across the twelve documents read, exactly three currency amounts appear. They sit together on a London promotional page:
To support new connections in London, temporary promotional conditions are currently available for selected services. Promotional pricing, based on 24 months: 10G = 425 EUR 100G = 2500 EUR 400G = 5500 EUR No Connection Fee Contract must be signed for 30 june 2026.
That is the whole published price of the product described above, and the page is explicit that it is temporary and conditional. Two things are missing from it, and both matter more than the amounts. There is no billing period: 425, 2500 and 5500 are not labelled per month, per year, per quarter or in total, and "based on 24 months" is the only term attached to them. There is also no VAT sentence on that page at all.
The deadline does not resolve the ambiguity. A contract that "must be signed for 30 june 2026" is a condition dated before this reading, and nothing in the documents says whether the promotion is still open, was renewed, or has lapsed. Report the deadline beside the amounts, and the status stays unknown.
The ratios inside the ladder are still informative, and this is my arithmetic rather than anything NL-ix prints. Divide each amount by its own port speed: 425 ÷ 10 = 42.5; 2500 ÷ 100 = 25; 5500 ÷ 400 = 13.75. The amount per gigabit of port speed falls steeply as the port grows. Because the unstated period is the same on all three lines, it cancels out of that comparison — which is precisely why the shape of the ladder can be quoted and the absolute level cannot.
The same page describes the London position in physical terms rather than commercial ones: "2 × 400G subsea links to Amsterdam", "1 × 400G subsea link to Brussels", "1 × 400G subsea link to Paris", and paths into the wider platform "without the need to manage inter-metro transport separately". That last phrase is a statement about management, not about money, and it belongs in the same paragraph as the amounts without being mistaken for one.
The transport is in words, the number is on a form
This is where the reserved question answers itself, and not in the direction I expected. I went looking for an unprinted inter-site transport term. It is printed — as words. "Covers the Transport between locations" is a service claim, and it is the substantive half of the single-port promise: the fabric between sites is the operator's business, and the customer buys one socket into it.
The contract machinery handles what the marketing does not. The General Agreement extraction makes the Order Form an integral part of the agreement and places the payment obligation on "the costs for the Service as specified on the Order Form". It invoices fixed recurring costs per calendar quarter and one-time costs at delivery, bills usage monthly in arrears on a 95th-percentile model, states that prices and rates are in euro exclusive of VAT, and reserves an annual re-assessment with at least two calendar months' notice. A second agreement version repeats the order-form model and defines peering in its own words as "the advertising of routes via BGP4".
Both of those PDFs were readable to me only as search-index extraction; one of them returned no readable text at all, and a third version is referenced in retrieval without being read. So I report the clauses as extraction and quote none of them. What survives the grading is structural rather than textual: the billing apparatus exists, it is quarterly for fixed costs and monthly for usage, and it points at a per-customer document that is not published. The unit is not absent from the contract. It is absent from the promotion.
The last metre, and the extra optics
What the port does not include is easier to establish than what it costs, because NL-ix says so plainly. On the support page: "Once your order is placed, NL-ix will forward you a CFA/LOA for you to order a cross-connect into the IX node present in your selected facility. You are responsible for arranging and paying for the cross-connect to reach the IX fabric."
That sentence does real work next to "No Connection Fee". A waived connection fee is NL-ix's own charge; the cross-connect is the customer's purchase from whoever runs the building. The two are different objects and the article keeps them apart.
The resources page adds a second unbundled item without a figure: standard single-mode optics are supported by default, and "For an additional charge, customer may request specialised optics, including extended reach optics in any common 100 Ghz DWDM or CWDM bands."
There is one exception on record, and it is narrow by the company's own account. The London upgrade article contrasts Telehouse's "cheap inter-building cross connects and more expensive intra-building cross connects" and explains the workaround: "for the Telehouse campus NL-ix provides cross connects for inter-building cross connects along with our service. This requires a slight markup on the price, but is more cost effective than handling the cross connect yourself." Telehouse campus, inter-building only, markup never quantified. It is a local arrangement described in an engineering post, not a general cross-connect policy, and it does not travel.
The services page lists nine named services — Peering, Transit, Cloud Connectivity, SaaS Connect, Transport, Elastic Interconnect, Anti-DDoS, The Interconnect CONsole and Custom Network — and prints no price, tariff, rate card or public order entry for any of them. The London page was found by search, not by navigation from that menu. A separate page for Amsterdam names points of presence that carry 800G there, which is the only place in the set where facility names meet a port speed; it is Amsterdam-specific and does not establish 800G anywhere else.
What a buyer can and cannot add up
The published material lets you build the shape of a bill and not its largest term. You can see a port speed and an amount, a term of 24 months, no connection fee, and a deadline. You cannot see a billing period, a VAT treatment on that page, a per-site charge, a per-cross-connect amount, a transport line, or the number of sites the base fee includes.
That is not a scandal; it is a disclosure perimeter, and its edges are unusually clean. The company tells you that it carries the traffic between its sites, then tells you that you buy the cable into its node, then offers you a promotional number without a clock. The accountability question is not whether the price is fair. It is "define the object": which sites a port reaches, how many cross-connects it needs, and what the Order Form says. A buyer who asks those three questions before signing is comparing a product; a buyer who compares 425 EUR to another exchange's rate card without a period is comparing a number to nothing.
BTW has been here in other shapes. The FICIX briefing found a port ladder priced to the euro beside a flat monthly fee whose unit of application was never printed. The DE-CIX briefing found twelve pages with no currency amount on any of them. The SIX briefing found one-time port prices and no recurring fee, because the inter-building fabric there is not bought at all. The TREX piece made the simplest version of the point: a port is not a path. None of those read a fabric where the socket and the reach are printed as two different objects at two different levels of precision. This one does, and the gap between them is the finding.
Boundaries of this reading
- This reading covers twelve nl-ix.net documents retrieved on 21 November 2026 between 00:49Z and 01:05Z, each retained as a snapshot. No reviewed page displayed a publication or last-updated date, so no figure here carries an as-of date of its own.
- Nine documents were read as directly retrieved page text. The two General Agreement PDFs were available only as search-index extraction, and one of them returned no readable text at all, so their clauses are reported as extraction and no verbatim quotation is taken from them.
- The Amsterdam 400G/800G page was a search excerpt only; it is Amsterdam-specific and does not establish 800G availability anywhere else.
- The connected-networks page renders its list in the browser, and no count of networks, members or facilities is quoted from it. The placeholder was visible in its place, and that is recorded as an access fact rather than as a claim about the list.
- The locations page prints no numeric count, and the count of seventeen metropolitan headings is mine.
- About 100 data centres and the named metropolitan areas are different counted objects. Nothing read converts one into the other, and no sites-per-port or cost-per-site figure is computed anywhere.
- The London promotional block states no billing period and no VAT treatment. No monthly, annual, total-contract or one-off basis is inferred, and no VAT rate is applied.
- The promotion's signing deadline of 30 June 2026 precedes this reading. Nothing read states whether it is current, lapsed or renewed, and neither is asserted.
- The published amounts are a promotional artefact. The operative price instrument is a per-customer Order Form, which is not among the documents read and whose contents are not described.
- "Covers the Transport between locations" is quoted as a service description. It is not read as a price term, as a guarantee that every inter-site link is included, or as anything about cross-connects.
- "No Connection Fee" is reported as printed and is not read as covering the cross-connect, which the support page places on the customer to arrange and pay for.
- The Telehouse inter-building arrangement is scoped by the company's own article to the Telehouse campus; its slight markup is never quantified and is not generalised to any other location.
- Two agreement versions are reported and a third is referenced without being read. No document read states which version is in force, so no clause is adopted as the operative one.
- No order was placed, no quotation requested and no sales contact made. No customer's bill, contract or Order Form was seen, and nothing here concerns any customer's position or conduct.
- No BGP session, looking glass, routing table, peering database record, exchange export or traffic measurement was queried. Nothing here is a measurement of the network.
- Statements about what BTW has already published describe BTW's own record as searched on 21 November 2026 and are not claims about the subject.
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.






