Summary

  • SAIX is not run by the telecom regulator. Its governance page hands King Abdulaziz City for Science and Technology the design, build, host and operate role, gives the Ministry of Communications and Information Technology the initiative, and leaves the ICT regulator one job: keeping the exchange aligned with regulation. The general terms name KACST, or a reseller it appoints, as the party a member actually contracts with.
  • What that operator publishes is unusually wide — a seven-column member roll carrying AS numbers, IPv4 and IPv6 addresses, port speeds and sites, plus a three-row price ladder at SAR 2,500, SAR 4,750 and SAR 30,000 a month. What it does not print is the clock. The payable price is fixed by a separately signed Connection Agreement; the advance notice for an upward change is an unfilled parenthesis; a downward change, by the text, may be applied instantly.

The signature settles who runs it

An exchange sitting inside its own regulator would be a particular instrument: the body that licenses a network and the body that admits it to the fabric would be one institution, and the port would be a licensed privilege rather than a purchase. That reading does not survive the exchange's own pages.

The governance page puts three institutions in three slots, in plain prose. KACST is "a scientific government institution that supports and enhances scientific applied research"; it "has been mandated to design, and implement the infrastructure required for SAIX"; and it hosts and operates the first site. The regulator's slot is narrow: "Its role in the initiative is to ensure the alignment between SAIX and the regulatory environment in the Kingdom of Saudi Arabia." The ministry's slot is broad: "MCIT is leading the SAIX initiative and is responsible for all of its aspects".

The about page supplies the origin story in one sentence — "MCIT approached King Abdulaziz City for Science & Technology to design, implement and operate SAIX" — and dates the first site's completed implementation phase to May 2017 at the KACST Data Center in Riyadh.

The General Terms and Conditions are where the layering stops being rhetoric. KACST is defined as "the party with whom Member has executed the SAIX Connection, i.e. either KACST or a third party appointed as a designated reseller by KACST", and the SAIX Infrastructure as "the Internet Exchange Infrastructure operated by KACST". Article 3.1 does the work: "The KACST will make and keep the Connection available to Member, and Member agrees to pay the price therefore, under the terms of the SAIX Connection Agreement."

So the paying network's counterparty is a science city. The regulator keeps a sentence, and the sentence is about alignment.

The roll is wider than most

On the member list the columns run: Organization Name, ASN, IPv4 Address, IPv6 Address, Service Speed, Service Type, Location. Service Type takes two values, Public Peering and Private Peering. Every location visible in the captured roll is either Riyadh or Jeddah.

KACST appears three times under AS8895: 10 Gbps private peering in Jeddah at 212.138.253.8 and 2001:1490:108::8; 30 Gbps public peering in Riyadh at 45.94.12.7, 45.94.12.8, 2001:1497::7 and 2001:1497::8; and 30 Gbps private peering in Riyadh at 212.138.252.7, 212.138.252.8, 2001:1490:104::7 and 2001:1490:104::8. Saudi Telecom Company, AS25019, sits at 400 Gbps public peering in Riyadh. The speed column reaches 800 and 1000 Gbps further down.

Admission is stated on the membership page and not in a numbered article of the terms: "SAIX membership is open for national or international network with a registered Autonomous System Number (AS) and IP address space, and accept Terms & Conditions Agreement." Four steps follow — review the Technical Requirements Document, review the Service Level Agreement, review the General Terms and Conditions, fill the Member Registration Form. There is no article headed Admission anywhere in the terms; Article 2 is Applicability and Appendices.

The ladder, and where it stops

The peering page carries a table headed Peering Prices, with two columns, Connection Speed and Monthly Price, and three rows: 1 GB at SAR 2,500, 10 GB at SAR 4,750, 100 GB at SAR 30,000. Speeds are printed as GB, not Gbps, and no effective, publication or last-updated date appears in the captured text.

Read as a rate, the ladder slopes hard. Mine, not printed: 2,500 divided by 1 is SAR 2,500 per GB of connection speed per month, 4,750 divided by 10 is SAR 475, 30,000 divided by 100 is SAR 300. The small port therefore costs 8.33 times the per-GB rate of the large one. And one 1 GB port for twelve months at the printed monthly price is SAR 30,000 — the identical figure to a single month of the 100 GB port.

The ladder stops at 100 GB. The roll does not. Ports at 400, 800 and 1000 Gbps are listed as connected, priced nowhere on the public page. That is not a contradiction: it is a perimeter. The biggest buyers buy from a document the public cannot read.

The clock is a blank

Article 5.1 sends the payable price to the Connection Agreement, including additional future order forms. The public ladder and the contract price are different objects, and only one of them is on the website.

Article 5.5 then does something I have not seen in an exchange rulebook this month:

"The KACST reserves the right to periodically reassess and reestablish the price of the Connection. Upward price changes shall be made public at least (Period will be defined once the connection agreement signed) prior to a change. Downward price changes may be applied instantly."

The parenthesis is not a redaction and not my paraphrase. The same string appears in Article 5.2, where the invoicing deadline belongs and where an unfilled blank sits before the word days; in Article 5.4, where the payment deadline belongs; and in Articles 8.2 and 8.3, inside both limitation-of-liability periods.

The contrast inside one document is the finding. The same terms state Article 6.2 precisely — either party may terminate on written notice, effective at the end of the calendar quarter in which the notice was received — and Article 11.1 precisely: amended conditions take effect on the stipulated commencement date or, failing that, when the contracting party is notified, including by posting on the SAIX website. This instrument knows how to print a clock. It prints four and leaves the fifth as a hole.

What the printed text therefore says, on its face, is asymmetric in a single direction: a cut may arrive with no waiting period at all, and a rise has no published waiting period either, because the period is deferred to a document no reader can see. The discretion is not hidden in a footnote. It is the shape of the sentence.

Two counters, one of them short

The homepage prints a block headed SAIX in Numbers: 3 Sites, 41 Connected Members, 160 Connected Ports, 6.7 Tbps Provisioned Capacity, 225 Total ASNs, +33K IPv4/IPv6 Prefixes, with traffic labels ALL-TIME PEAK, PEAK, AVERAGE and CURRENT. No date appears beside any of it, and the block is obviously populated at load time.

The roll names two locations. The second-site announcement names Jeddah's Global Data Hub at King Abdullah University of Science and Technology, and carries two dates, 1 November 2022 and 16 April 2024 — original and update, most likely, though the page was available to me only as an excerpt.

Three sites against two names is a coverage gap, and I will not close it by assuming a building. A site can carry cross-connects with no member row of its own, and a roll can lag a build. What can be said is narrower: the one number a passer-by reads first is the one number nothing else on the site reconciles.

What a member is buying

The record is not a scandal, and I am not reporting one. Nothing I read says a price was raised, that notice was withheld, that any network was overcharged, or that anything was done improperly by KACST, the ministry or the regulator. No Connection Agreement crossed my desk; the actual notice period any member holds may be thirty days, ninety, or none.

What the documents show is a specific and useful asymmetry. The operator of a shared fabric has published the population that depends on it, the addresses at which they sit, the speeds they bought, and the price of the three ports anyone can self-serve. It has also published the rule that governs revision of that price. That rule has no clock in it. A network weighing a cross-connect, a router port and a multi-year transit plan reads a price ladder that can move, and a text that declines to say how much warning it gets when it moves up.

Every other exchange I have read this month differs only in which half of the instrument is missing. One withholds the member register. One withholds the shareholder bridge. One prices the port and buries the vote. This one publishes almost everything and still leaves the one parameter that decides the timing risk to the party that can see the whole fabric and the network that can see only its own row.

Boundaries

  1. What was read, on 19 November 2026: the governance page, the about page, the General Terms and Conditions, the peering page, the member list, the homepage, the membership page and a second-site announcement. The terms text reached me as search-index extraction of the PDF, never as a page-image read, and the full document was not inspected end to end.
  2. No Connection Agreement was obtained. Nothing here states the notice period any member actually has; the finding is confined to what the published text itself prints.
  3. The placeholder conclusion rests on five coherent occurrences of the same parenthetical in Articles 5.2, 5.4, 5.5, 8.2 and 8.3, plus an unfilled blank before "days" in 5.2. That is strong evidence and not a visual check of the page.
  4. No dated version history: the terms carry v1.5 in the file name and a 2020/04 upload path with no printed cover date seen; the price table, the member roll and the homepage counters carry no effective or last-updated line in the captured text.
  5. The Technical Requirements Document (v1.6) and the Service Level Agreement (v1.2) were located but not opened. Excerpt-level material from them, including a monthly availability figure and a maintenance notice period, is not used as a finding here.
  6. Speeds on the price table are printed as GB, not Gbps, and are reported as printed. No conversion is attempted.
  7. The homepage counts three sites; the roll names Riyadh and Jeddah only. The third site is unresolved, not disproven: a site can exist with no listed member.
  8. Homepage counters are dynamic and undated. They are a point-in-time reading of a publisher's own dashboard, not an independent measurement.
  9. The roll's row set may be truncated in retrieval and carries no date; the total row count was not confirmed.
  10. No claim that any price was raised, that any notice was withheld, that any member was overcharged, or that anything about KACST, MCIT or CITC is improper. The finding is about the text of the published instrument.
  11. CITC has since been renamed the Communications, Space and Technology Commission; the governance page predates the change and uses CITC. Both appear only as the page prints them.
  12. "Not-for-profit" and "announced by MCIT" are the publisher's own descriptions. No corporate registration document was read, and no legal form is asserted here beyond what those pages say.
  13. The price ladder is not a tariff schedule. Article 5.1 sends the payable price to the Connection Agreement, so the ladder and the contract price are different objects and this article keeps them apart.
  14. The per-GB figures and the twelve-month multiplication are my own labelled arithmetic on the printed rows. Nothing is annualised as a cost of service, divided by traffic or converted into a per-member figure.
  15. Prior coverage named rather than repeated: the MIX Milano owner roll and admission article; the SwissIX two products separated by a vote; the LINX rulebook whose member register stayed closed; the PCH directory count with an undefined counted object; the IX.br open port with an asterisk.