asn.dev

Internet exchange

MEX-IX McAllen

active McAllen, United States

Recorded members 36 addresses on file
Connected ports 18 across all participants
Peak traffic 479 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
McAllen, United States
Region
North America
Status
Active

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
206.71.142.0/24IPv4Active18
2620:3b:6000::/64IPv6Active18

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

18 networks · 36 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 36 recorded addresses.

ASNetworkAddressesrDNSPolicy
AS6939Hurricane Electric LLC206.71.142.162620:3b:6000::1b1b:1——Open
AS13335Cloudflare, Inc.206.71.142.102620:3b:6000::3417:1——Open
AS20940Akamai International B.V.206.71.142.132620:3b:6000::51cc:1——Open
AS199524G-Core Labs S.A.206.71.142.202620:3b:6000::3:b64:1——Open
AS11172Alestra, S. de R.L. de C.V.206.71.142.272620:3b:6000::2ba4:1——Open
AS18734Operbes, S.A. de C.V.206.71.142.112620:3b:6000::492e:1——Open
AS17072TOTAL PLAY TELECOMUNICACIONES, S.A.P.I. DE C.V.206.71.142.242620:3b:6000::42b0:1——Open
AS19332COORDINADORA DE CARRIER'S, S.A. DE C.V.206.71.142.262620:3b:6000::4b84:1——Open
AS13999Mega Cable, S.A. de C.V.206.71.142.172620:3b:6000::36af:1——Open
AS6503Axtel, S.A.B. de C.V.206.71.142.122620:3b:6000::1967:1——Open
AS52580Azion Technologies Ltda.206.71.142.212620:3b:6000::cd64:1——Open
AS265605VELOCOM SA DE CV206.71.142.232620:3b:6000::4:d85:1——Open
AS7438PEGASO PCS206.71.142.182620:3b:6000::1d0e:1——Open
AS40731Latin IP LLC206.71.142.152620:3b:6000::9f1b:1——Open
AS33438Datum206.71.142.252620:3b:6000::829e:1———
AS22566IP Matrix, S.A. de C.V.206.71.142.192620:3b:6000::5826:1——Open
AS32261SUBSPACE206.71.142.222620:3b:6000::7e05:1——Open
AS46489TWITCH INTERACTIVE INC.206.71.142.142620:3b:6000::b599:1——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-11 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,346 exchanges and 98,138 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.