Petah Tikva · Israel
PeeringDB records no exchange in Petah Tikva and four colocation facilities holding 34 network presences. MedOne PT1 (Petach Tikva) carries 20 of them, ahead of Bezeq International Shacham Data Center with 12. An address that geolocates to Petah Tikva shows where an operator registered the block, not where a device sits.
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 |
|---|---|---|
| MedOne PT1 (Petach Tikva) | 20 | 94 Jabotinsky Petah Tikva 49517 |
| Bezeq International Shacham Data Center | 12 | 40 Shacham street Ground Floor |
| Bezeq International Sivim Data Center | 2 | 6 Nevatim street |
| EdgeConneX Tel Aviv (EDCTLV11) | 0 | Avshalom Gissin St. 53 |
What a Petah Tikva IP address tells you
Petah Tikva has no exchange on record, so what the city holds sits in colocation rather than on a shared peering fabric. Four facilities appear under the city, and 34 network presences are spread across them. MedOne PT1 (Petach Tikva) accounts for 20, Bezeq International Shacham Data Center for 12, and Bezeq International Sivim Data Center for 2, while EdgeConneX Tel Aviv (EDCTLV11) records none. That last name shows how loosely facility labels track city fields, since a facility named for Tel Aviv is filed here. The carrier registry lists no Israeli mobile ASNs, so carrier peering cannot be checked against a participant list.
A database can place an address in Petah Tikva while the equipment using it sits elsewhere. An operator registers a block against a company record, and that record carries the company's own address rather than the room the traffic passes through. Mobile networks widen the gap, because a carrier releases subscriber traffic through a small number of gateways and everyone behind one gateway shares its public address. Geolocation databases read what the operator publishes, so a city label repeats the operator's paperwork instead of measuring where a connection starts.
The origin ASN on the specific prefix answers more than the city label does. Look at which network announces the block and at what the netname says about its holder, since a prefix registered to one of the facility operators on the Petah Tikva list points at hosting rather than a handset. With 34 network presences in the city's facilities and no exchange record to compare against, those facility lists are the only local reference the public data gives, and a prefix matching none of them reads as an announcement from somewhere else.
Questions
Which internet exchanges are in Petah Tikva?
PeeringDB records none. The city's entries are colocation facilities rather than exchanges, so any peering that happens here happens as private interconnection inside those sites, and the public data holds no participant list for a shared fabric in Petah Tikva.
Do Israel mobile carriers peer in Petah Tikva?
The data cannot say. The carrier registry holds no mobile ASNs for Israel, and Petah Tikva has no exchange participant list to check them against. Any carrier presence in the four facilities would be private interconnection that PeeringDB does not publish.
Does an IP that geolocates to Petah Tikva mean the device is there?
No. Geolocation follows the address an operator published for the block, and that is usually a company registration rather than a device location. Mobile addresses are shared across gateways covering wide areas, so the label describes the operator's record.
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