Petach Tikva · Israel
PeeringDB records one exchange in Petach Tikva. IIX Israel, registered as Israel Internet eXchange, has 15 participants. A single colocation facility, SDS4 Petch Tikva, is on file with no network presences recorded. An address that geolocates to Petach Tikva shows what an operator registered for the block, not where a device sits.
Internet exchanges in Petach Tikva
An exchange is a shared switch where networks hand traffic to each other directly. Participant counts come from PeeringDB, where each network maintains its own record.
| Exchange | Participants | Registry carriers peering |
|---|---|---|
IIX Israel Israel Internet eXchange | 15 | none in the registry |
Exchange records: PeeringDB.
Colocation facilities
Buildings where networks put equipment. The network count is how many PeeringDB members list a presence there, which shows where capacity in the city sits.
| Facility | Networks present | Address |
|---|---|---|
| SDS4 Petch Tikva | 0 | Harakevet 8 |
What a Petach Tikva IP address tells you
All of the recorded peering in Petach Tikva sits on one fabric. IIX Israel, whose long name is Israel Internet eXchange, holds 15 participants, and that is the entire participant count for the city. Colocation adds nothing measurable, since the one facility on file, SDS4 Petch Tikva, records zero network presences. The city reads as an exchange location without a matching colocation footprint in the data. The exchange lists no mobile carrier ASN, and the carrier registry holds no Israeli mobile ASNs, so nothing in the record shows a carrier peering here.
An address that a database places in Petach Tikva may be announced from anywhere the announcing network reaches. Operators register blocks against a company record, and that record carries a corporate address rather than the site holding the equipment. Mobile traffic concentrates through a small number of gateways, so one public address can cover subscribers across a wide area. Geolocation providers follow the operator's own published location, which means a city result reflects an administrative entry rather than a measurement of where the traffic starts.
The origin ASN on the exact prefix is the check worth making. It names the network announcing the block, and the netname on the registry object names the holder. Comparing that holder against the 15 participants on IIX Israel shows whether the network has any recorded presence in the city. A prefix originating from a network absent from that list, and absent from the single facility record, has no local footprint in the data, whatever the city label says.
Questions
Which internet exchanges are in Petach Tikva?
One, IIX Israel, registered under the long name Israel Internet eXchange, with 15 participants. The city also has a single colocation facility, SDS4 Petch Tikva, though it records no network presences, so the exchange holds all the counted interconnection.
Do Israel mobile carriers peer in Petach Tikva?
The record does not show it. The IIX Israel participant list flags no mobile carrier ASN, and the carrier registry holds no Israeli mobile ASNs to compare it with. That leaves the question open rather than answered in the negative.
Does an IP that geolocates to Petach Tikva mean the device is there?
No. The city label comes from the address an operator registered for the block, which is usually a company office. Mobile addresses pass through gateways covering large areas, so a Petach Tikva result identifies the operator's record and not the device.
Sources
- PeeringDB - exchanges, participant counts, facilities and network presence, snapshot 2026-09-07
- PROXIES.SX carrier and ASN registry - operator ASNs used to match peering participants