asn.dev

Internet exchange

Internet Exchange Services Yucatan

active Merida, Mexico MID

Recorded members 32 addresses on file
Connected ports 9 across all participants
Peak traffic 26.6 Mbps peak, as recorded
Peering LANs 2 shared subnets

Overview

What this is

recorded

An internet exchange is shared switching where networks interconnect directly instead of paying a transit provider to carry traffic between them. Members take a port on the fabric and an address on the peering LANs below, then agree bilaterally (or through a route server) about which routes to exchange. Turning up at one is a deliberate choice about how a network wants to be reached, which is why exchange presence says something a routing table cannot.

Location
Merida, Mexico
Region
Latin America
Airport code
MID
Status
Active
PCH record updated
2026-10-11

Everything on this page is what Packet Clearing House had recorded when the directory was collected, not a live view of the fabric. Member counts in particular lag reality, and around 45% of the exchanges in this dataset publish no participant list at all.

Fabric

Peering LANs

2 on file

The shared subnets members take an address on. A network with an interface in one of these blocks is at this exchange by definition, which is what makes exchange presence a recorded fact rather than an inference. Most exchanges run one IPv4 and one IPv6 LAN; extra blocks are usually growth or a migration.

PrefixFamilyStatusParticipants
45.164.110.0/24IPv4Active9
2806:30c:2021:110::/64IPv6Active9

Deprecated and retired blocks are listed rather than dropped. A decommissioned LAN still records how this fabric used to be reached, and filtering it would quietly rewrite the exchange's history.

Participants

Member networks

15 networks · 32 addresses

Every network PCH records with an address on one of the peering LANs above, ordered as the source ranks them: the most-connected participants first. Each network's addresses on the fabric are listed together, IPv4 first. Typing in the box narrows the rows below; Search looks through all 32 recorded addresses.

ASNetworkAddressesrDNSPolicy
AS42WoodyNet, Inc.45.164.110.62806:30c:2021:110::6——Open
AS63293Facebook, Inc.45.164.110.2542806:30c:2021:110::254——Open
AS17072TOTAL PLAY TELECOMUNICACIONES, S.A.P.I. DE C.V.45.164.110.122806:30c:2021:110::12——Open
AS3856Packet Clearing House, Inc.45.164.110.72806:30c:2021:110::7——Open
AS265561LANTOINTERNET SA DE CV45.164.110.192806:30c:2021:110::19——Open
AS265620UFINET MEXICO S. DE R.L. DE C.V.45.164.110.82806:30c:2021:110::8——Open
AS61455LACTLD - LATIN AMERICAN AND CARIBBEAN TLD ASSOCIATION45.164.110.212806:30c:2021:110::21——Open
AS265566TELESISTEMAS PENINSULARES SA DE CV45.164.110.132806:30c:2021:110::13——Open
AS28396AITelecom S.A. de C.V.45.164.110.112806:30c:2021:110::11——Open
AS270111Comunicacion por Fibra SA de CV45.164.110.202806:30c:2021:110::20——Open
AS265583SISTEMAS Y SOLUCIONES DE CAMPECHE SAS DE CV45.164.110.172806:30c:2021:110::17——Open
AS265623REDES Y ASESORIAS DEL MAYAB SA DE CV45.164.110.162806:30c:2021:110::16——Open
AS270173INTERNET EXCHANGE SERVICES YUCATAN45.164.110.152806:30c:2021:110::15——Open
AS270127SECRETARIA DE ADMINISTRACION Y FINANZAS45.164.110.102806:30c:2021:110::10——Open
AS28441INET EXCH SVC YUCATAN45.164.110.245.164.110.12806:30c:2021:110::12806:30c:2021:110::2————Open

Peering policy is what the network declared to PCH, not something anyone verified, and an open policy is an invitation rather than a commitment. Absence of a network here means PCH has no record of it at this exchange, not that it is not present.

Provenance

Where this comes from

Exchange records come from the directory collected 2026-10-12 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,346 exchanges and 98,167 recorded member addresses, licensed CC BY-NC-SA 3.0.

This is a snapshot, not a live view. Members join and leave continuously, and the figures above are what PCH had on file on the collection date. PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.