asn.dev

Observed topology

AS32261

Not seen in any path

This AS number does not appear in any route we observed. That is normal for an AS that is allocated but not announcing, one used only privately, or one whose routes do not reach our collectors.

Interconnection

Exchange presence

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS32261, largest fabric first. An exchange is shared switching where networks interconnect directly rather than paying a transit provider to carry traffic between them, so turning up at one is a deliberate choice about how this network wants to be reached. Each name opens that exchange's own page, with its peering LANs and every other network recorded on it. Recorded at 39 exchanges across 17 countries and 4 regions.

ExchangeLocationTheir addressMember ports
OpenIXP Internet exchange PointJakarta, Indonesia218.100.36.2122,071
LINX LON1London, United Kingdom195.66.226.91925
Neutral Internet ExchangeAmsterdam, Netherlands193.239.118.236665
France-IX ParisParis, France37.49.237.225570
Equinix Internet Exchange AshburnAshburn, United States206.126.237.3388
BroadBand Internet eXchange TokyoTokyo, Japan2001:de8:c::3:2261:1359
Coresite - Any2 WestLos Angeles, United States206.72.211.87344
Any2 CaliforniaLos Angeles, United States206.72.211.87321
Equinix Internet Exchange ChicagoChicago, United States208.115.137.174280
JPIX TokyoTokyo, Japan210.171.225.79259
DE-CIX DusseldorfDüsseldorf, Germany185.1.171.48226
Equinix Internet Exchange DallasDallas, United States206.223.118.134225
New York International Internet ExchangeNew York, United States2001:504:1::a503:2261:1217
DE-CIX HamburgHamburg, Germany185.1.210.205195
FL-IX - The Florida Internet Exchange / Community IX - FloridaMiami, United States206.41.108.26179
Digital Realty Atlanta Internet ExchangeAtlanta, United States206.126.110.29175
Equinix Internet Exchange MiamiMiami, United States198.32.242.220175
DE-CIX ASEAN (Singapore, Malaysia, Brunei)Singapore, Singapore2001:df6:480::7e05:0:1138
BroadBand Internet eXchange OsakaOsaka, Japan218.100.9.128132
France-IX MarseilleMarseille, France37.49.232.96127
PIT Lima - PIT PeruLima, Peru45.183.47.205120
Budapest Internet ExchangeBudapest, Hungary193.188.137.133119
JPIX OsakaOsaka, Japan103.246.232.125114
Northwest Access ExchangePortland, United States198.32.195.85105
BroadBand Internet eXchange Hong KongHong Kong, China103.203.158.164101
Equinix Internet Exchange New YorkNew York, United States198.32.118.6798
Boston Internet ExchangeBoston, United States206.108.236.10488
Equinix Internet Exchange Los AngelesLos Angeles, United States206.223.123.3481
Equinix Internet Exchange Palo AltoPalo Alto, United States198.32.176.20976
Equinix Los Angeles IBXLos Angeles, United States206.223.123.3472
United IX ChicagoChicago, United States206.41.110.9270
Korea Internet Neutral Exchange KINXSeoul, South Korea2001:7fa:8::2b64
Philippine Open Internet ExchangeManila, Philippines198.32.172.15460
Croatian Internet ExchangeZagreb, Croatia185.1.87.12946
Kolkata IXKolkata, India103.74.224.20733
Manama-IXManama, Bahrain77.69.248.2428
Aqaba IXAqaba, Jordan84.252.106.1118
MEX-IX McAllenMcAllen, United States206.71.142.2218
Equinix-LA(former Paix) retiredLos Angeles, United States198.32.242.220

Unlike the tables above, this is recorded rather than inferred. An address on a peering LAN is at that exchange by definition. Two carve-outs all the same. Member ports counts every participant at the exchange, not this network's ports, so read it as a size proxy. And an absent exchange means PCH has no record of it, not that the network is not there.

Derived from routing tables collected at 2026-08-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.02M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Exchange presence comes from a separate dataset: the directory collected 2026-08-09 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,164 recorded member ports, licensed CC BY-NC-SA 3.0.

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.