Guadalajara · Mexico
Guadalajara's weight in PeeringDB sits in buildings rather than on a peering fabric. Two exchanges are registered, GDL-IX with a single participant and IX GDL with none, while three facilities hold 21 network presences, 13 of them at HostDime GDL Mexico Data Center. An address geolocating here reflects an operator's registry record, not a device's position.
Internet exchanges in Guadalajara
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 |
|---|---|---|
GDL-IX GDL-IXP | 1 | none in the registry |
IX GDL | 0 | 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 |
|---|---|---|
| HostDime GDL Mexico Data Center | 13 | Avenida López Mateos Sur 2077 Col, Jardines Plaza del Sol |
| Megacable Data Center - Guadalajara | 7 | Calle Jose Mariano Abasolo 1571 Cerro del Jagüey |
| Triara Guadalajara | 1 | Birch Street 269 A Col. Del Fresno |
What a Guadalajara IP address tells you
Both Guadalajara exchanges are thinly populated in this data. GDL-IX, registered as GDL-IXP, shows one participant and IX GDL shows none, which leaves the city with a single recorded exchange participant. Networks that interconnect in Guadalajara do it inside colocation instead. HostDime GDL Mexico Data Center records 13 networks, Megacable Data Center - Guadalajara seven and Triara Guadalajara one, so three buildings hold 21 network presences against that one exchange slot. No mobile carrier ASN appears at either exchange.
An address that geolocates to Guadalajara reports where an operator registered the block. The network can announce that prefix from anywhere it routes, and mobile traffic reaches the internet through a small number of gateways, so one published location can stand behind addresses used across a wide area. Geolocation databases follow the operator's own record, which is why a city with one exchange participant still appears as the answer for many addresses.
The origin ASN on the specific prefix and the netname on the registry object are more use than the city field. They say which network announces the range and who registered it. Because Guadalajara's public peering data is close to empty, the facility records for HostDime GDL Mexico Data Center, Megacable Data Center - Guadalajara and Triara Guadalajara are where a network's presence in the city would show up.
Questions
Which internet exchanges are in Guadalajara?
Two are registered in PeeringDB, GDL-IX (GDL-IXP) with one participant and IX GDL with none. The city's interconnection sits in colocation instead, where HostDime GDL Mexico Data Center records 13 networks, Megacable Data Center - Guadalajara seven and Triara Guadalajara one.
Do Mexican mobile carriers peer in Guadalajara?
Neither GDL-IX nor IX GDL lists a mobile carrier ASN in this data, and with one participant between them there is very little public peering to read. Mobile operators can still interconnect privately in the city's facilities, which the registry does not record.
Does an IP that geolocates to Guadalajara mean the device is there?
No. The city name comes from an operator's registry entry for the address block and from databases that copy it. The same block can be announced from elsewhere on the network, and mobile users sit behind gateways that cover much more ground than one city.
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