asn.dev

Observed topology

AS214371 HORIZON-IT

Hosting RIPE Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS214371: 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 LLCTransitIPv4 IPv662
AS213622Falcon FZE LLCUnclassifiedIPv4 IPv657
AS214757Jakub KrsaUnclassifiedIPv4 IPv68
AS24482SG.GSHostingIPv4 IPv63
AS401753BIXCE IncUnclassifiedIPv4 IPv63
AS20764CJSC RASCOMUnclassifiedIPv41
AS50917Diederik Focko de ZeeUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS218582VOLUNIAUnclassifiedIPv4 IPv6101
AS214542Gino Ben SalahHostingIPv638

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6157
AS218582VOLUNIAUnclassifiedIPv4 IPv6101
AS213622Falcon FZE LLCUnclassifiedIPv4 IPv678
AS214542Gino Ben SalahHostingIPv638
AS214757Jakub KrsaUnclassifiedIPv4 IPv620
AS24482SG.GSHostingIPv4 IPv68
AS401753BIXCE IncUnclassifiedIPv4 IPv68
AS20764CJSC RASCOMUnclassifiedIPv42
AS50917Diederik Focko de ZeeUnclassifiedIPv41

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.