Observed topology
AS46489
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
Internet exchanges where Packet Clearing House has a port recorded for AS46489, 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 38 exchanges across 18 countries and 3 regions.
| Exchange | Location | Their address | Member ports |
|---|---|---|---|
| DE-CIX Frankfurt | Frankfurt, Germany | 2001:7f8::b599:0:1 | 1,073 |
| LINX LON1 | London, United Kingdom | 195.66.225.25 | 925 |
| Indonesian Internet Exchange (IIX-Jakarta) | Jakarta, Indonesia | 123.108.9.221 | 923 |
| AMS-IX Amsterdam | Amsterdam, Netherlands | 80.249.210.197 | 894 |
| Neutral Internet Exchange | Amsterdam, Netherlands | 193.239.117.158 | 665 |
| France-IX Paris | Paris, France | 37.49.237.25 | 570 |
| Equinix Internet Exchange Singapore | Singapore, Singapore | 27.111.229.46 | 490 |
| Equinix Internet Exchange Ashburn | Ashburn, United States | 206.126.236.193 | 388 |
| Seattle Internet Exchange | Seattle, United States | 206.81.81.54 | 350 |
| Any2 California | Los Angeles, United States | 206.72.210.165 | 321 |
| Hong Kong Internet Exchange | Hong Kong, China | 123.255.90.46 | 307 |
| Equinix Internet Exchange Warsaw | Warsaw, Poland | 195.182.218.245 | 300 |
| Toronto Internet Exchange | Toronto, Canada | 206.108.35.45 | 286 |
| Equinix Internet Exchange Chicago | Chicago, United States | 208.115.136.193 | 280 |
| JPIX Tokyo | Tokyo, Japan | 210.171.225.161 | 259 |
| Equinix Internet Exchange Sydney | Sydney, Australia | 45.127.172.198 | 238 |
| DE-CIX Madrid | Madrid, Spain | 2001:7f8:a0::b599:0:1 | 229 |
| Equinix Internet Exchange Dallas | Dallas, United States | 206.223.118.163 | 225 |
| Peering.cz | Prague, Czech Republic | 185.0.20.116 | 212 |
| IX Australia (Sydney NSW) | Sydney, Australia | 218.100.52.157 | 199 |
| FL-IX - The Florida Internet Exchange / Community IX - Florida | Miami, United States | 206.41.108.58 | 179 |
| ESpanix Madrid Lower LAN | Madrid, Spain | 193.149.1.41 | 177 |
| Digital Realty Atlanta Internet Exchange | Atlanta, United States | 206.126.110.238 | 175 |
| Equinix Internet Exchange Miami | Miami, United States | 198.32.243.200 | 175 |
| Berlin Commercial Internet Exchange | Berlin, Germany | 193.178.185.106 | 152 |
| Taipei Internet Exchange (TPIX) | Taipei, Taiwan | 203.163.222.93 | 151 |
| DE-CIX Marseille | Marseille, France | 2001:7f8:36::b599:0:1 | 113 |
| Northwest Access Exchange | Portland, United States | 198.32.195.121 | 105 |
| Equinix Internet Exchange New York | New York, United States | 198.32.118.198 | 98 |
| CANIX Internet Exchange - Montreal | Montreal, Canada | 198.179.18.70 | 88 |
| Bangkok Neutral Internet Exchange | Bangkok, Thailand | 203.159.68.134 | 78 |
| Equinix Internet Exchange Palo Alto | Palo Alto, United States | 198.32.176.232 | 76 |
| Equinix Los Angeles IBX | Los Angeles, United States | 206.223.123.247 | 72 |
| Korea Internet Neutral Exchange KINX | Seoul, South Korea | 139.150.100.187 | 64 |
| Salt Lake Internet Exchange | Salt Lake City, United States | 149.112.13.29 | 38 |
| Kolkata IX | Kolkata, India | 103.74.224.118 | 33 |
| Neutral Internet Exchange 2 | Amsterdam, Netherlands | 185.1.122.19 | 19 |
| MEX-IX McAllen | McAllen, United States | 206.71.142.14 | 18 |
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-08 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,137 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.