Observed topology

AS8161 INSIGHT-AS

Unclassified ARIN

Upstreams 6 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS3356	Level 3 Parent, LLC	Transit	IPv4	369
AS7018	AT&T Enterprises, LLC	Residential	IPv4	318
AS12025	Iron Mountain Data Center	Unclassified	IPv4	138
AS12703	Pulsant (Scotland) Ltd	Hosting	IPv4	58
AS9299	Philippine Long Distance Telephone Company	Unclassified	IPv4	56
AS4775	Globe Telecoms	Unclassified	IPv4	9

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS3356	Level 3 Parent, LLC	Transit	IPv4	369
AS7018	AT&T Enterprises, LLC	Residential	IPv4	318
AS12025	Iron Mountain Data Center	Unclassified	IPv4	138
AS12703	Pulsant (Scotland) Ltd	Hosting	IPv4	58
AS9299	Philippine Long Distance Telephone Company	Unclassified	IPv4	56
AS4775	Globe Telecoms	Unclassified	IPv4	9

Provenance

Where this comes from

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