asn.dev

Observed topology

AS214451 R3ido101 Oliver Reid

Hosting RIPE

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

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS214451: 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
AS52025ParadoxNetworks LimitedUnclassifiedIPv4 IPv660
AS212396FyfeWeb LtdHostingIPv4 IPv639
AS215638Cilix LimitedResidentialIPv421
AS6939Hurricane Electric LLCTransitIPv47
AS24482SG.GSHostingIPv4 IPv63
AS48185team.blue NVUnclassifiedIPv4 IPv62
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv62
AS34019Hivane AssociationUnclassifiedIPv61
AS37721Virtual Technologies & SolutionsResidentialIPv41
AS49673Truenetwork LLCUnclassifiedIPv41

All 12 upstreams →

Transit

Downstream networks

inferred

Networks for which AS214451 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 12

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

ASNetworkTypeFamiliesPaths seen
AS52025ParadoxNetworks LimitedUnclassifiedIPv4 IPv660
AS212396FyfeWeb LtdHostingIPv4 IPv639
AS215638Cilix LimitedResidentialIPv421
AS6939Hurricane Electric LLCTransitIPv47
AS24482SG.GSHostingIPv4 IPv63
AS48185team.blue NVUnclassifiedIPv4 IPv62
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv62
AS34019Hivane AssociationUnclassifiedIPv61
AS37721Virtual Technologies & SolutionsResidentialIPv41
AS49673Truenetwork LLCUnclassifiedIPv41

All 12 adjacent →

Provenance

Where this comes from

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