Observed topology
AS397601
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 AS397601, 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 13 exchanges across 9 countries and 4 regions.
| Exchange | Location | Their address | Member ports |
|---|---|---|---|
| DE-CIX Frankfurt | Frankfurt, Germany | 80.81.195.110 | 1,073 |
| AMS-IX Amsterdam | Amsterdam, Netherlands | 80.249.215.232 | 893 |
| Neutral Internet Exchange | Amsterdam, Netherlands | 193.239.118.124 | 665 |
| NAPAfrica IX Johannesburg | Johannesburg, South Africa | 196.60.10.163 | 603 |
| France-IX Paris | Paris, France | 37.49.238.72 | 570 |
| London Network Access Point | London, United Kingdom | 5.57.82.39 | 316 |
| Singapore Internet Exchange | Singapore, Singapore | 103.16.102.252 | 273 |
| Local Internet Exchange Frankfurt | Frankfurt, Germany | 185.1.166.220 | 223 |
| Johannesburg Internet Exchange | Johannesburg, South Africa | 196.60.97.21 | 213 |
| PIT Chile - Santiago | Santiago, Chile | 45.68.16.76 | 174 |
| Torino Piemonte Exchange Point | Torino, Italy | 194.116.96.6 | 123 |
| DE-CIX Marseille | Marseille, France | 185.1.47.124 | 113 |
| Serbian Open Exchange | Belgrade, Serbia | 185.1.27.40 | 51 |
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.