asn.dev

Observed topology

AS214354 AS_SITEHUB SiteHUB Agency Ltd

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS214354: 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 IPv6447
AS37271Workonline Communications(Pty) LtdUnclassifiedIPv4 IPv6254
AS26042FiberState, LLCHostingIPv4 IPv696
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv611
AS401753BIXCE IncUnclassifiedIPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS329592Sitehub Agency LtdUnclassifiedIPv672
AS205563Marc GomezUnclassifiedIPv664
AS40776TaoNetHostingIPv4 IPv638
AS54728DataPlane.orgUnclassifiedIPv632
AS200690Junxiao ShiUnclassifiedIPv632
AS329273Fastfeet LimitedHostingIPv41

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6576
AS37271Workonline Communications(Pty) LtdUnclassifiedIPv4 IPv6355
AS26042FiberState, LLCHostingIPv4 IPv696
AS329592Sitehub Agency LtdUnclassifiedIPv672
AS205563Marc GomezUnclassifiedIPv664
AS40776TaoNetHostingIPv4 IPv638
AS54728DataPlane.orgUnclassifiedIPv632
AS200690Junxiao ShiUnclassifiedIPv632
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv620
AS401753BIXCE IncUnclassifiedIPv64

All 11 adjacent →

Provenance

Where this comes from

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