asn.dev

Observed topology

AS214022 VIRTNET Joseph Rawlings trading as Virtnet.bond

Unclassified RIPE

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

Transit

Upstream networks

All 18

Networks observed carrying traffic for AS214022: 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
AS6939Hurricane Electric LLCTransitIPv689
AS394177SHIFT HOSTING LLCHostingIPv4 IPv634
AS400587Ryamer, LLCHostingIPv434
AS8772Netassist International EOODUnclassifiedIPv68
AS52025ParadoxNetworks LimitedUnclassifiedIPv68
AS24482SG.GSHostingIPv4 IPv65
AS34927iFog GmbHHostingIPv65
AS401753BIXCE IncUnclassifiedIPv4 IPv65
AS29632Netassist International EOODUnclassifiedIPv64
AS37989DCS1 Pte. Ltd.HostingIPv64

All 18 upstreams →

Transit

Downstream networks

inferred

Networks for which AS214022 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 18

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv689
AS394177SHIFT HOSTING LLCHostingIPv4 IPv634
AS400587Ryamer, LLCHostingIPv434
AS8772Netassist International EOODUnclassifiedIPv68
AS52025ParadoxNetworks LimitedUnclassifiedIPv68
AS24482SG.GSHostingIPv4 IPv65
AS34927iFog GmbHHostingIPv65
AS401753BIXCE IncUnclassifiedIPv4 IPv65
AS29632Netassist International EOODUnclassifiedIPv64
AS37989DCS1 Pte. Ltd.HostingIPv64

All 18 adjacent →

Provenance

Where this comes from

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