Mexico City · Mexico
Three exchanges appear in Mexico City in PeeringDB, with 48 participants between them. DE-CIX Mexico is the best connected at 26, ahead of BGP.Exchange - Mexico City with 14 and Equinix Mexico with eight. Three facilities record 11 network presences. An address geolocating here names an operator's published location for the block rather than a device.
Internet exchanges in Mexico City
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 |
|---|---|---|
DE-CIX Mexico DE-CIX MEXICO (Mexico City, Querétaro) | 26 | none in the registry |
BGP.Exchange - Mexico City | 14 | none in the registry |
Equinix Mexico Equinix Internet Exchange Mexico | 8 | 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 |
|---|---|---|
| MTP Sites Mexico City Santa Fe DC | 10 | 2977 Mexico to Toluca free way Col.El Yaqui. Town Hall Cuajimalpa |
| ATC Edge CDMX/E1 | 1 | 481 Juan Vazquez de Mella |
| ATC Edge CDMX/E2 | 0 | 29 Av. Wilfrido Massieu |
What a Mexico City IP address tells you
DE-CIX Mexico, whose registry entry covers Mexico City and Querétaro, carries 26 of the 48 exchange participants recorded in the city. BGP.Exchange - Mexico City holds 14 and Equinix Mexico eight. Colocation is thinner in this data than the exchange side. MTP Sites Mexico City Santa Fe DC records ten networks, ATC Edge CDMX/E1 one and ATC Edge CDMX/E2 none, which is 11 presences across three facilities. No Mexican mobile carrier ASN appears on any of the three participant lists.
An operator announces a prefix from a registry record, and that record carries one address for a range the network can use nationally. Mobile traffic concentrates further and leaves through a small number of gateways that may sit in one city while subscribers use the addresses anywhere. Commercial geolocation databases follow the operator's own published location, so a whole block can read as Mexico City on the strength of a single administrative entry rather than any device being here.
The origin ASN on the exact prefix and the netname on the registry object say more than the city label does. They identify the network announcing the range and the organisation that registered it. If the question is whether that network is present in Mexico City rather than merely labelled with it, the participant lists behind those 48 exchange slots and the 11 facility presences are the records that answer it.
Questions
Which internet exchanges are in Mexico City?
PeeringDB records three. DE-CIX Mexico is the best connected with 26 participants, BGP.Exchange - Mexico City has 14 and Equinix Mexico has eight, giving 48 participant slots in total. The DE-CIX entry covers Mexico City and Querétaro under one registry record.
Do Mexican mobile carriers peer in Mexico City?
No mobile carrier ASN shows up on the participant lists for DE-CIX Mexico, BGP.Exchange - Mexico City or Equinix Mexico in this data. Private interconnection inside colocation is not published in the registry, so the honest answer is that no public peering record ties a Mexican mobile network to the city.
Does an IP that geolocates to Mexico City mean the device is there?
No. The lookup repeats a location an operator registered for the address block. A network can announce that block from anywhere it routes, and mobile addresses in particular sit behind gateways that serve subscribers well outside whatever city the database names.
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