Beirut · Lebanon

Beirut's peering activity splits across three fabrics. OpenIX Beirut carries 23 participant networks, LebIX 17 and A.IX 13, which totals the 53 participant records PeeringDB holds for the city. The colocation side is thinner. PeeringDB lists Berytech Technological Pole, Advanced IX SAL and Capital Outsourcing Beirut, with a single network recorded across all three facilities. Interconnection in Beirut therefore sits in the exchange fabrics rather than in documented facility presence. The carrier registry holds no Lebanese mobile operator ASNs, so nothing in this data shows a mobile network peering at any of the three exchanges.

An address that a database places in Beirut can belong to equipment somewhere else in Lebanon. An operator registers a block once, with one address on the registry record, and every prefix under that record inherits the same city. Mobile networks compound this because subscriber traffic leaves through a small number of gateways, and the gateway rather than the handset decides where the public address appears. Geolocation providers read the location the operator publishes and copy it forward, so a Beirut result often describes a company's registration rather than a street in Beirut.

Anyone checking a Beirut address should read the origin ASN and the netname on the specific prefix instead of the city string. The ASN says which network announces the block; the netname often says whether the range is assigned to fixed broadband, a mobile pool or a hosting customer. Compare that against the exchanges in the city. A network that appears at OpenIX Beirut, LebIX or A.IX has documented interconnection in Lebanon, while one that appears at none of them may route its Beirut-labelled space from wherever its transit reaches.