asn.dev

Observed topology

AS401561 PROXEL - Proxel Innovations LLC

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS401561: 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 IPv6724

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS7654Internet Solution & Service Provider Co., Ltd.ResidentialIPv4325
AS15829Eutelsat S.A.UnclassifiedIPv4325
AS558543 Killiney Road # 09-01/06UnclassifiedIPv4260
AS136933Gigabitbank GlobalUnclassifiedIPv4260
AS33847Khalifa UniversityUnclassifiedIPv465
AS153005PHU THANH CLOUD COMPANY LIMITEDUnclassifiedIPv465
AS206405CALIU LTDUnclassifiedIPv465

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv63,065
AS401581Infolink Technologies LLCUnclassifiedIPv4585
AS401534GATEL NETWORK SOLUTION LLCUnclassifiedIPv4391
AS7654Internet Solution & Service Provider Co., Ltd.ResidentialIPv4325
AS15829Eutelsat S.A.UnclassifiedIPv4325
AS558543 Killiney Road # 09-01/06UnclassifiedIPv4260
AS136933Gigabitbank GlobalUnclassifiedIPv4260
AS33847Khalifa UniversityUnclassifiedIPv465
AS153005PHU THANH CLOUD COMPANY LIMITEDUnclassifiedIPv465
AS206405CALIU LTDUnclassifiedIPv465

Provenance

Where this comes from

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