asn.dev

Observed topology

AS39401 LINKPLUS

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS39401: 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
AS8717A1 Bulgaria EADResidentialIPv41,100
AS12615Global Communication Net PlcUnclassifiedIPv4918
AS8866Vivacom Bulgaria EADResidentialIPv4728
AS31287IPACCT CABLE LtdUnclassifiedIPv444
AS39251NETGUARD LLCUnclassifiedIPv636

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS44309Anton Simeonov"UnclassifiedIPv4682
AS49040K and G UNISAT -TV LLCUnclassifiedIPv4434

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS8717A1 Bulgaria EADResidentialIPv41,525
AS12615Global Communication Net PlcUnclassifiedIPv41,368
AS8866Vivacom Bulgaria EADResidentialIPv4958
AS44309Anton Simeonov"UnclassifiedIPv4682
AS49040K and G UNISAT -TV LLCUnclassifiedIPv4434
AS31287IPACCT CABLE LtdUnclassifiedIPv455
AS39251NETGUARD LLCUnclassifiedIPv636

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.