asn.dev

Observed topology

AS205398 TYLER-OBRIEN _

Unclassified RIPE Educational/Research

Upstreams 14 carry this network
Downstreams 0 this network carries
Adjacent (IPv4) 0
Adjacent (IPv6) 14
Upstream graph Who carries AS205398, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS205398 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 14

Networks observed carrying traffic for AS205398: 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
AS53667FranTech SolutionsHostingIPv6206
AS917Misaka Network, Inc.UnclassifiedIPv6173
AS20473The Constant Company, LLCHostingIPv6133
AS44103The Mastermind Holding B.V.UnclassifiedIPv676
AS52025ParadoxNetworks LimitedUnclassifiedIPv672
AS394177SHIFT HOSTING LLCHostingIPv670
AS44684Mythic Beasts LtdHostingIPv645
AS56655Gigahost ASUnclassifiedIPv638
AS835GoCodeIT IncUnclassifiedIPv637
AS61138Zappie Host LLCUnclassifiedIPv637

All 14 upstreams →

Transit

Downstream networks

inferred

Networks for which AS205398 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

All 14

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

ASNetworkTypeFamiliesPaths seen
AS53667FranTech SolutionsHostingIPv6206
AS917Misaka Network, Inc.UnclassifiedIPv6173
AS20473The Constant Company, LLCHostingIPv6133
AS44103The Mastermind Holding B.V.UnclassifiedIPv676
AS52025ParadoxNetworks LimitedUnclassifiedIPv672
AS394177SHIFT HOSTING LLCHostingIPv670
AS44684Mythic Beasts LtdHostingIPv645
AS56655Gigahost ASUnclassifiedIPv638
AS835GoCodeIT IncUnclassifiedIPv637
AS61138Zappie Host LLCUnclassifiedIPv637

All 14 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-28 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.21M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

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. 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.

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