asn.dev

Observed topology

AS46890 3COM-NET-ROUTER-AS46890 - 3Com Net Router

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS46890: 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
AS263035PORTAL QUEOPS TELECOMUNICACOES LTDAResidentialIPv4420
AS272450Angelica Souza comunicacao multimidiaUnclassifiedIPv4180
AS6939Hurricane Electric LLCTransitIPv4110
AS52925Ascenty Data Centers e Telecomunicacoes S/AUnclassifiedIPv450
AS24482SG.GSHostingIPv410
AS37721Virtual Technologies & SolutionsResidentialIPv410

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS269566PHI TELECOM LTDA.MEUnclassifiedIPv4 IPv6761
AS271723Com Net RouterUnclassifiedIPv4 IPv6432

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS269566PHI TELECOM LTDA.MEUnclassifiedIPv4 IPv6761
AS263035PORTAL QUEOPS TELECOMUNICACOES LTDAResidentialIPv4756
AS6939Hurricane Electric LLCTransitIPv4 IPv6543
AS52925Ascenty Data Centers e Telecomunicacoes S/AUnclassifiedIPv4 IPv6435
AS271723Com Net RouterUnclassifiedIPv4 IPv6432
AS272450Angelica Souza comunicacao multimidiaUnclassifiedIPv4180
AS24482SG.GSHostingIPv4 IPv641
AS37721Virtual Technologies & SolutionsResidentialIPv418

Provenance

Where this comes from

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