Observed topology

AS401581 Infolink Technologies LLC

Unclassified ARIN

Upstreams 0 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 0

Upstream graph Who carries AS401581, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS401581 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS401581: 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.

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS40987	BANQ TECH BILGI VE ILETISIM TEKNOLOJILERI LIMITED SIRKETI	Unclassified	IPv4	264
AS15656	Nano Iletisim Bilisim Hizmetleri Teknoloji Sistemleri Sanayi ve Ticaret Ltd Sirketi	Unclassified	IPv4	132
AS43479	TELCOBT BILGI TEKNOLOJILERI SAN. VE TIC. LTD. STI.	Unclassified	IPv4	132
AS33801	Boldyn Networks Finland Holdings Oy	Unclassified	IPv4	66

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS401561	Proxel Innovations LLC	Unclassified	IPv4	594
AS40987	BANQ TECH BILGI VE ILETISIM TEKNOLOJILERI LIMITED SIRKETI	Unclassified	IPv4	264
AS15656	Nano Iletisim Bilisim Hizmetleri Teknoloji Sistemleri Sanayi ve Ticaret Ltd Sirketi	Unclassified	IPv4	132
AS43479	TELCOBT BILGI TEKNOLOJILERI SAN. VE TIC. LTD. STI.	Unclassified	IPv4	132
AS33801	Boldyn Networks Finland Holdings Oy	Unclassified	IPv4	66

Provenance

Where this comes from

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