asn.dev

Observed topology

AS62013 CLICK-COM-AS str. A. Plamadeala 60 A

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS62013: 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
AS15836Arax-Impex s.r.l.ResidentialIPv4651
AS8772Netassist International EOODUnclassifiedIPv4217
AS29632Netassist International EOODUnclassifiedIPv496

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS51267Interlink Comunicatii SRLUnclassifiedIPv4257
AS57776Urscom-TV S.R.L.UnclassifiedIPv4130
AS35525DIANA-NET SRLUnclassifiedIPv465
AS57713Societatea Comerciala "ACER-COM" S.R.L.UnclassifiedIPv464

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS15836Arax-Impex s.r.l.ResidentialIPv41,050
AS8772Netassist International EOODUnclassifiedIPv4290
AS51267Interlink Comunicatii SRLUnclassifiedIPv4257
AS29632Netassist International EOODUnclassifiedIPv4140
AS57776Urscom-TV S.R.L.UnclassifiedIPv4130
AS35525DIANA-NET SRLUnclassifiedIPv465
AS57713Societatea Comerciala "ACER-COM" S.R.L.UnclassifiedIPv464

Provenance

Where this comes from

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