asn.dev

Observed topology

AS214292 DE-CIX Management GmbH

Upstreams 0 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 8
Adjacent (IPv6) 6

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS214292: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you.

Transit

Downstream networks

inferred

Networks for which AS214292 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS15169Google LLCHostingIPv4 IPv61,081

Adjacency

Adjacent networks

14 shown

Every AS seen directly next to AS214292 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS15169Google LLCHostingIPv4 IPv64,845
AS971PureVoltage Hosting Inc.UnclassifiedIPv42,872
AS13830PureVoltage Hosting Inc.HostingIPv41,844
AS12552GlobalConnect ABUnclassifiedIPv426
AS37721Virtual Technologies & SolutionsResidentialIPv426
AS57463NetIX Communications JSCUnclassifiedIPv426
AS37100SEACOM LimitedUnclassifiedIPv426
AS29632Netassist International EOODUnclassifiedIPv65
AS56662Marcin GondekUnclassifiedIPv65
AS17639Converge ICT Solutions Inc.UnclassifiedIPv65
AS213241TECHIT.BE SRLResidentialIPv65
AS24482SG.GSHostingIPv4 IPv65

Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Interconnection

Exchange presence

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS214292, 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 8 exchanges across 5 countries and 3 regions.

ExchangeLocationTheir addressMember ports
DE-CIX FrankfurtFrankfurt, Germany80.81.193.2211,073
DE-CIX New YorkNew York, United States206.82.104.54279
DE-CIX MadridMadrid, Spain185.1.192.246229
DE-CIX DallasDallas, United States206.53.202.186174
DE-CIX ASEAN (Singapore, Malaysia, Brunei)Singapore, Singapore103.162.254.84138
DE-CIX ChicagoChicago, United States149.112.11.7983
DE-CIX Kuala LumpurKuala Lumpur, Malaysia103.119.234.4246
DE-CIX PhoenixPhoenix, United States149.112.27.2940

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.

Provenance

Where this comes from

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.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.

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.