asn.dev

Internet exchange

IXP-GT

active Guatemala, Guatemala GUA

Recorded members 21 addresses on file
Connected ports 13 across all participants
Peak traffic Not reported no figure on file
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
Guatemala, Guatemala
Region
Latin America
Airport code
GUA
Status
Active
PCH record updated
2023-02-25

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.68.5.0/24IPv4Active13
2801:12:e800:5::/64IPv6Active7

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

13 networks · 21 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 21 recorded addresses.

ASNetworkAddressesrDNSPolicy
AS13335Cloudflare, Inc.45.68.5.952801:12:e800:5::95———
AS42WoodyNet, Inc.45.68.5.1092801:12:e800:5::109———
AS32934Facebook, Inc.45.68.5.772801:12:e800:5::77———
AS3856Packet Clearing House, Inc.45.68.5.1102801:12:e800:5::110———
AS267828Senal Nacional S.A.45.68.5.12045.68.5.682801:12:e800:5::68————
AS269940CABLE SISTEMA S.R.L. DE C.V.45.68.5.91——
AS28049ISP SOLUTIONS S.A.45.68.5.70——
AS263761Broadcom Group, S.A45.68.5.124——
AS269926SKYWAY45.68.5.125——
AS271885ASOCIACION DE RED AVANZADA GUATEMALTECA PARA LA INVESTIGACION Y LA EDUCACION (IXP GT)45.68.5.12801:12:e800:5::1———
AS266755CONECTIVIDAD Y TECNOLOGIA S.A.45.68.5.121——
AS267885MSW S.A.45.68.5.762801:12:e800:5::76———
AS272969HOGARES INTELIGENTES, S. A.45.68.5.74——

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-13 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,346 exchanges and 98,177 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.