asn.dev

Observed topology

AS200242 DE-THEIRS open-source & non-profit modern transitcontent network

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS200242: 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.

ASNetworkTypeFamiliesPaths seen
AS34927iFog GmbHHostingIPv6144
AS917Misaka Network, Inc.UnclassifiedIPv4 IPv6127
AS6939Hurricane Electric LLCTransitIPv685
AS21738RozintResidentialIPv677
AS210152Jon Vanvik trading as Vanvik InternetUnclassifiedIPv670
AS142064VergeTelUnclassifiedIPv660
AS208453Johan Karlsson trading as SweHostingHostingIPv659
AS59678SYSTEM36 LLCHostingIPv634
AS29632Netassist International EOODUnclassifiedIPv610
AS205794JINZE YANGUnclassifiedIPv68
AS17639Converge ICT Solutions Inc.UnclassifiedIPv66
AS24482SG.GSHostingIPv66
AS204092Association GRIFONUnclassifiedIPv66
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv66
AS48185team.blue NVUnclassifiedIPv66
AS33891Core-Backbone GmbHHostingIPv65
AS52025ParadoxNetworks LimitedUnclassifiedIPv64

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 AS200242 was observed as the last hop before the origin, meaning it appears to provide them transit.

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

18 shown

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

ASNetworkTypeFamiliesPaths seen
AS34927iFog GmbHHostingIPv6144
AS917Misaka Network, Inc.UnclassifiedIPv4 IPv6127
AS6939Hurricane Electric LLCTransitIPv685
AS21738RozintResidentialIPv677
AS210152Jon Vanvik trading as Vanvik InternetUnclassifiedIPv670
AS142064VergeTelUnclassifiedIPv660
AS208453Johan Karlsson trading as SweHostingHostingIPv659
AS59678SYSTEM36 LLCHostingIPv634
AS29632Netassist International EOODUnclassifiedIPv610
AS205794JINZE YANGUnclassifiedIPv68
AS17639Converge ICT Solutions Inc.UnclassifiedIPv66
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv66
AS204092Association GRIFONUnclassifiedIPv66
AS24482SG.GSHostingIPv66
AS48185team.blue NVUnclassifiedIPv66
AS33891Core-Backbone GmbHHostingIPv65
AS52025ParadoxNetworks LimitedUnclassifiedIPv64

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 AS200242, 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 3 exchanges across 3 countries and 2 regions.

ExchangeLocationTheir addressMember ports
Neutral Internet ExchangeAmsterdam, Netherlands193.239.118.234665
Ontario Internet ExchangeToronto, Canada2001:504:125:e1::da198
Kansas City Internet ExchangeKansas City, United States206.51.7.21572

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-09 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.03M 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.