Observed topology

AS395584 PDC-BGP

Unclassified ARIN

Upstreams 1 carry this network

Downstreams 7 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS395584: 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	240

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS58065	Orion Network Limited	Unclassified	IPv4	660
AS14397	1st Class Hosting, LLC	Hosting	IPv4	600
AS46634	Net10 Internet Services, LLC	Unclassified	IPv4	300
AS399275	Solid Systems LLC	Unclassified	IPv4 IPv6	213
AS397130	SmartLayer Business Solutions	Unclassified	IPv4	120
AS30166	Ex3	Unclassified	IPv4	60
AS64249	Charles River Operation	Unclassified	IPv4	60

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS3356	Level 3 Parent, LLC	Transit	IPv4 IPv6	2,253
AS58065	Orion Network Limited	Unclassified	IPv4	660
AS14397	1st Class Hosting, LLC	Hosting	IPv4	600
AS46634	Net10 Internet Services, LLC	Unclassified	IPv4	300
AS399275	Solid Systems LLC	Unclassified	IPv4 IPv6	213
AS397130	SmartLayer Business Solutions	Unclassified	IPv4	120
AS30166	Ex3	Unclassified	IPv4	60
AS64249	Charles River Operation	Unclassified	IPv4	60

Provenance

Where this comes from

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