Observed topology

AS395471 DATACCESS

Unclassified ARIN NSP

Upstreams 4 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS395471: 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
AS21559	OSNET	Unclassified	IPv4	532
AS1299	Arelion Sweden AB	Transit	IPv4	184
AS23379	Blackburn Technologies II, LLC	Unclassified	IPv4	60
AS23520	Columbus Networks USA, Inc.	Residential	IPv4	1

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS18895	Nustream Communications	Unclassified	IPv4	1,722
AS20372	Office of Management and Budget	Unclassified	IPv4	323
AS396082	COSOTNET INC	Unclassified	IPv4	236

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS18895	Nustream Communications	Unclassified	IPv4	1,760
AS23520	Columbus Networks USA, Inc.	Residential	IPv4	1,201
AS1299	Arelion Sweden AB	Transit	IPv4	923
AS21559	OSNET	Unclassified	IPv4	845
AS20372	Office of Management and Budget	Unclassified	IPv4	323
AS396082	COSOTNET INC	Unclassified	IPv4	236
AS23379	Blackburn Technologies II, LLC	Unclassified	IPv4	127

Provenance

Where this comes from

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