asn.dev

Observed topology

AS214731 ETO-AS

Unclassified RIPE Educational/Research

Upstreams 20 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 2
Adjacent (IPv6) 23
Upstream graph Who carries AS214731, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS214731 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 20

Networks observed carrying traffic for AS214731: 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
AS216211CYBERVERSE LLCHostingIPv4 IPv6307
AS53667FranTech SolutionsHostingIPv6199
AS44103The Mastermind Holding B.V.UnclassifiedIPv6152
AS6939Hurricane Electric LLCTransitIPv6145
AS17433Hytron Network Services LimitedResidentialIPv6144
AS35661VIRTUA SYSTEMS SASUnclassifiedIPv6118
AS53808MoeDoveUnclassifiedIPv6106
AS209554ISIF OUResidentialIPv6106
AS52025ParadoxNetworks LimitedUnclassifiedIPv698
AS34927iFog GmbHHostingIPv672

All 20 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS205779Tianhang YuanUnclassifiedIPv637

Adjacency

Adjacent networks

All 23

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

ASNetworkTypeFamiliesPaths seen
AS216211CYBERVERSE LLCHostingIPv4 IPv6307
AS53667FranTech SolutionsHostingIPv6199
AS6939Hurricane Electric LLCTransitIPv6176
AS44103The Mastermind Holding B.V.UnclassifiedIPv6152
AS17433Hytron Network Services LimitedResidentialIPv6144
AS35661VIRTUA SYSTEMS SASUnclassifiedIPv6118
AS53808MoeDoveUnclassifiedIPv6106
AS209554ISIF OUResidentialIPv6106
AS52025ParadoxNetworks LimitedUnclassifiedIPv698
AS34927iFog GmbHHostingIPv672

All 23 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-31 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.50M 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.