asn.dev

Observed topology

AS46962 HRCOM

Unclassified ARIN NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS46962: 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
AS6208FiberXResidentialIPv4 IPv6267
AS401866Master IT SupportHostingIPv4117

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS400333JR Network PRUnclassifiedIPv4 IPv6193
AS399599G&B Networks SolutionsUnclassifiedIPv4 IPv6166
AS400443NOVANETUnclassifiedIPv4 IPv6166
AS399831REAL LINK NETWORK LLCUnclassifiedIPv4 IPv6101
AS401831VuvaNet LLCUnclassifiedIPv465
AS401866Master IT SupportHostingIPv636
AS394590SkyTechUnclassifiedIPv627

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6208FiberXResidentialIPv4 IPv6929
AS400333JR Network PRUnclassifiedIPv4 IPv6193
AS399599G&B Networks SolutionsUnclassifiedIPv4 IPv6166
AS400443NOVANETUnclassifiedIPv4 IPv6166
AS401866Master IT SupportHostingIPv4 IPv6153
AS399831REAL LINK NETWORK LLCUnclassifiedIPv4 IPv6101
AS396998Path Network, Inc.UnclassifiedIPv4 IPv692
AS401831VuvaNet LLCUnclassifiedIPv465
AS394590SkyTechUnclassifiedIPv627

Provenance

Where this comes from

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