Summary

  • The Saudi Arabian Internet Exchange publishes 3 sites, 41 connected members, 160 connected ports, 6.7 Tbps of provisioned capacity, 223 total ASNs and more than 33,000 IPv4/IPv6 prefixes in the numbers block on its own homepage, read on 11 November 2026.
  • A provisioning figure is a stock, not a flow: it fixes a ceiling on what could be handed off domestically without showing what is. No measured traffic figure appears in the page text reviewed that day, so the record confirms capability and leaves localisation unverified.

The numbers block on the exchange's own site is short, and on 11 November 2026 it read like a bill of materials. Three sites. 41 connected members. 160 connected ports. 6.7 Tbps provisioned capacity. 223 total ASNs. More than 33,000 IPv4/IPv6 prefixes. The same page describes the operator as a non-profit exchange point "brought by MCIT in cooperation with KACST" — brought by the Ministry of Communications and Information Technology in cooperation with King Abdulaziz City for Science and Technology.

Every figure in that block is an inventory. Count the sites, count the ports, sum the capacity those ports can deliver, count the network identities that appear. Nothing in the block states how much traffic crosses the fabric, what the busiest hour looks like, or what share of the provisioned capacity has ever been lit at once. Those are different numbers about different things, and only the second kind tells you whether a country's internet traffic is actually being handed off at home.

The block also invites arithmetic the operator does not perform itself. 6.7 Tbps spread across 160 connected ports is roughly 42 Gbps per port. Spread across 41 connected members it is roughly 163 Gbps per member. Those 160 ports across those 41 members come to about 3.9 ports each. All three are divisions of published figures, not published measurements, and none of them says whether a single port has run near its share for a single hour.

That distinction is not pedantry. A lane count on a motorway tells you how many cars could pass; a traffic count tells you how many did. An exchange that provisions 6.7 Tbps has built the on-ramps, lit the fabric across three sites and recruited 41 members to connect to it. A country that wants its domestic traffic to stay domestic needs exactly that. It also needs to know about the cars.

The operator aims higher on the same page. It states that SAIX "interconnects networks and optimize traffic performance in Saudi Arabia by reducing latency and improving localization of both content and traffic." That is an ambition written as a function. It is the operator's claim, quoted here as it stands, and nothing in the reviewed text measures it.

The ASN and prefix counts carry real weight of a different kind. 223 network identities and more than 33,000 IPv4 and IPv6 prefixes describe a routing population substantial enough to make a domestic fabric worth joining, and a prefix count large enough that the exchange is not a two-member experiment. They do not say where those networks sit, where their traffic terminates, or whether a given prefix is served from inside the country rather than pulled across a border and announced at the fabric.

No measured traffic figure appears in the page text reviewed on 11 November 2026, and no participant roster appears there either. That is a statement about one page and one date, not a verdict on how the operator handles disclosure overall: this review establishes what that block shows, and nothing about what else the exchange may publish.

What the record does establish is specific and not trivial. Domestic hand-off of meaningful scale exists: three sites, 160 connected ports and 6.7 Tbps of provisioned capacity is not a pilot. A routing population exists: 223 ASNs, tens of thousands of prefixes. And the exchange has a stated institutional sponsor in the state and a science-and-technology body, which is how a national fabric gets built before it gets measured.

What the record leaves open is everything about load. Utilisation of the 6.7 Tbps. The ratio of domestic to internationally pulled traffic, which is the quantity a localisation argument actually turns on. Whether the 41 members and 160 ports are exercised or merely provisioned. The composition of the 223 networks — access providers, enterprises, content, government — is unknown from this page.

For a reader with a decision to make, the consequences differ by seat. An operator weighing a port can treat the inventory as evidence that domestic peering is feasible, priced and populated; it cannot treat the inventory as evidence of how much traffic a new port would actually exchange. An investor should read a build denominated in provisioned capacity the way any stock figure deserves to be read: as a promise whose value depends on a flow nobody has published. A regulator writing a localisation target in terabits of installed capacity has chosen a metric that cannot distinguish a hand-off layer that exists from one that is used.

How does an inventory turn into a performance claim without anyone lying? By juxtaposition. Ports and provisioned terabits sit in a block where a reader expects the headline number to describe the network, so a stock gets read as a result. It is also the easiest number to publish and the hardest to dispute: nobody argues with a port count, while a utilisation figure invites questions about the hour it was taken.

The next decisive number about the Saudi Arabian Internet Exchange is therefore not a larger provisioning headline. It is a flow figure carrying a measurement date and a stated period — peak, average or utilisation — published by the operator or produced by an independent measurement. Until one appears, the precise reading is this: the hand-off layer exists at real scale, and domestic localisation remains a case rather than a measurement.

Evidence: SAIX site, read 11 November 2026; BTW directory record.