asn.dev

Observed topology

AS39513 ONECOM-AS IXP

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS39513: 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
AS3257GTT Communications Inc.TransitIPv427
AS50263A-Systems Sp. z o.o.UnclassifiedIPv423
AS6939Hurricane Electric LLCTransitIPv47
AS24482SG.GSHostingIPv41
AS34927iFog GmbHHostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS43998Cifrovye Dispetcherskie Sistemy LLCUnclassifiedIPv459
AS45022LLC RAZOM COMMUNICATIONSUnclassifiedIPv45

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS43998Cifrovye Dispetcherskie Sistemy LLCUnclassifiedIPv459
AS3257GTT Communications Inc.TransitIPv457
AS50263A-Systems Sp. z o.o.UnclassifiedIPv448
AS6939Hurricane Electric LLCTransitIPv47
AS49559A-Systems Sp. z o.o.UnclassifiedIPv46
AS45022LLC RAZOM COMMUNICATIONSUnclassifiedIPv45
AS60159EUROLINE UKRAINE LLCUnclassifiedIPv43
AS24482SG.GSHostingIPv41
AS34927iFog GmbHHostingIPv41

Provenance

Where this comes from

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