Interconnection
AS4849 HKINTCOM-AS AsiaTech Telecom Ltd.
Hosting RIPE
Recorded presence
Internet exchanges
Internet exchanges where Packet Clearing House has a port recorded for AS4849, largest fabric first. An exchange is shared switching where networks interconnect directly rather than paying a transit provider, so turning up at one is a deliberate choice about how this network wants to be reached. Each name opens that exchange's page, with its peering LANs and everyone else on it.
Europe 11
| Exchange | Location | Their address | Policy | Member ports |
|---|---|---|---|---|
| LINX LON1 | London, United Kingdom | 195.66.228.119 | Open | 930 |
| Giganet Internet Exchange | Kyiv, Ukraine | 185.1.62.254 | Open | 355 |
| Speed Internet Exchange | Dronten, Netherlands | 185.1.222.65 | Open | 285 |
| NetIX | Sofia, Bulgaria | 185.1.226.115 | — | 264 |
| InterIX Internet Exchange | Amsterdam, Netherlands | 2001:7f8:134::2a | Open | 234 |
| Nine IX | Paris, France | 185.1.14.174 | — | 165 |
| Bulgarian Internet eXchange | Sofia, Bulgaria | 193.169.198.191 | Open | 139 |
| Budapest Internet Exchange | Budapest, Hungary | 193.188.137.109 | Open | 121 |
| LayerSwitch Internet Exchange | The Hague, Netherlands | 185.1.32.117 | Open | 104 |
| Slovak Internet eXchange Bratislava | Bratislava, Slovakia | 192.108.148.252 | Open | 71 |
| Greek Internet Exchange - Thessaloniki | Thessaloniki, Greece | 185.1.123.31 | Open | 22 |
Recorded rather than inferred: an address on a peering LAN is at that exchange by definition. Member ports counts every participant at the exchange, not this network's ports, so read it as a size proxy. An absent exchange means PCH has no record of it, not that the network is not there. For the operator's own claims, see its PeeringDB record.
From the exchange directory collected 2026-10-15 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,346 exchanges and 97,714 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.