asn.dev

Observed topology

AS62467 TXNET - TXNet Communications LLC

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS62467: 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
AS394437PS LightwaveUnclassifiedIPv4 IPv6170
AS174Cogent Communications, LLCTransitIPv4 IPv6108
AS6300FidiumResidentialIPv4 IPv683
AS6939Hurricane Electric LLCTransitIPv4 IPv648
AS14907Wikimedia Foundation Inc.HostingIPv4 IPv69
AS971PureVoltage Hosting Inc.UnclassifiedIPv45
AS25091IP-Max SAUnclassifiedIPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS26286MysticDev LLCUnclassifiedIPv4 IPv6627
AS18783RD Sec LLCUnclassifiedIPv4 IPv6119
AS402084AES Services LLCUnclassifiedIPv424

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS26286MysticDev LLCUnclassifiedIPv4 IPv6927
AS394437PS LightwaveUnclassifiedIPv4 IPv6543
AS174Cogent Communications, LLCTransitIPv4 IPv6444
AS35847Ezee FiberResidentialIPv4190
AS6939Hurricane Electric LLCTransitIPv4 IPv6170
AS18783RD Sec LLCUnclassifiedIPv4 IPv6119
AS6300FidiumResidentialIPv4 IPv683
AS14907Wikimedia Foundation Inc.HostingIPv4 IPv634
AS402084AES Services LLCUnclassifiedIPv424
AS971PureVoltage Hosting Inc.UnclassifiedIPv420

All 11 adjacent →

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.