asn.dev

Observed topology

AS60246 PG-19

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS60246: 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
AS35598INETCOM CARRIER LLCUnclassifiedIPv4 IPv61,548
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv6487
AS62255BiMajLink d.o.o.UnclassifiedIPv4 IPv678
AS24482SG.GSHostingIPv4 IPv639
AS9002RETN LimitedUnclassifiedIPv4 IPv631
AS37721Virtual Technologies & SolutionsResidentialIPv429
AS49673Truenetwork LLCUnclassifiedIPv429
AS6939Hurricane Electric LLCTransitIPv49
AS34927iFog GmbHHostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS204435New-Com Trade Ltd.UnclassifiedIPv465

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS35598INETCOM CARRIER LLCUnclassifiedIPv4 IPv61,594
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv6500
AS62255BiMajLink d.o.o.UnclassifiedIPv4 IPv680
AS204435New-Com Trade Ltd.UnclassifiedIPv465
AS24482SG.GSHostingIPv4 IPv640
AS9002RETN LimitedUnclassifiedIPv4 IPv632
AS37721Virtual Technologies & SolutionsResidentialIPv430
AS49673Truenetwork LLCUnclassifiedIPv430
AS6939Hurricane Electric LLCTransitIPv49
AS34927iFog GmbHHostingIPv41

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.