Tel Aviv · Israel

Exchange peering in Tel Aviv is small on the record. BGP.Exchange - Tel-Aviv holds 7 participants, while colocation holds slightly more, with 11 network presences across three facilities. TIS Tel Aviv Burla Hub and Data Center carries 7 of them, Bezeq International TLV Data Center carries 3, and Internet Binat Tel Aviv DC carries 1. Most of the city's recorded interconnection therefore sits in facility presence rather than on the shared fabric. No mobile carrier ASN appears among the exchange participants, and the carrier registry holds no mobile ASNs for Israel, so carrier peering here goes unrecorded either way.

A Tel Aviv geolocation result describes paperwork more often than equipment. An operator registers an address block against a company record, and the address in that record belongs to the company, not to the rack. Mobile networks stretch the gap further, since subscriber traffic leaves through a handful of gateways and every subscriber behind one of them carries the same public address. Databases build their city fields from what operators publish, so a block announced across the country still lands on whichever city the operator wrote down.

Someone checking a Tel Aviv address gets more from the prefix than from the city string. The origin ASN says which network announces the block, and the netname says who registered it. A prefix held by one of the three facility operators on the city's list reads as hosting, while a prefix held by a mobile network reads as consumer access whatever city the lookup returns. With 7 exchange participants and 11 facility presences on record, the local reference set is small enough to check by hand.