asn.dev

Interconnection

AS13194 BITE Bite IP Network

Unclassified RIPE

Exchanges 13 13 active
Countries 8 most in Germany
Regions 1
Largest fabric 1,078 DE-CIX Frankfurt

Recorded presence

Internet exchanges

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS13194, 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 13

ExchangeLocationTheir addressPolicyMember ports
DE-CIX FrankfurtFrankfurt, Germany80.81.194.118Selective1,078
AMS-IX AmsterdamAmsterdam, Netherlands80.249.213.200Selective882
Neutral Internet ExchangeAmsterdam, Netherlands193.239.118.197Selective669
Giganet Internet ExchangeKyiv, Ukraine185.1.62.67Selective355
Equinix Internet Exchange WarsawWarsaw, Poland195.182.219.218Selective297
DE-CIX DusseldorfDüsseldorf, Germany185.1.170.31Selective227
DE-CIX MunichMunich, Germany185.1.208.39—211
Peering.czPrague, Czech Republic185.0.20.51Selective211
DE-CIX HamburgHamburg, Germany185.1.210.50—196
Netnod StockholmStockholm, Sweden195.69.119.211—77
Baltic Internet ExchangeVilnius, Lithuania77.241.206.11Selective76
Santa Monica Internet Local ExchangeRiga, Latvia195.246.227.12Selective24
Netnod Sundsvall- GävleSundsvall, Sweden194.68.128.211Selective18

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