asn.dev

Observed topology

AS42396 PPLNETUA-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS42396: 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
AS35297Dataline LLCUnclassifiedIPv41,158
AS1820WNET TELECOM USA Corp.ResidentialIPv4848
AS35320Eurotranstelecom LtdUnclassifiedIPv4272
AS9002RETN LimitedUnclassifiedIPv480
AS24482SG.GSHostingIPv438
AS6939Hurricane Electric LLCTransitIPv410
AS7713PT Telekomunikasi IndonesiaResidentialIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS56459PE Golub Iryna AnatoliivnaUnclassifiedIPv4125
AS215765"RADIO-LINK SMART" LLCUnclassifiedIPv451
AS39928Broadcasting TV Company "Studio 1+1"UnclassifiedIPv435

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS35297Dataline LLCUnclassifiedIPv41,336
AS1820WNET TELECOM USA Corp.ResidentialIPv4898
AS35320Eurotranstelecom LtdUnclassifiedIPv4281
AS56459PE Golub Iryna AnatoliivnaUnclassifiedIPv4125
AS9002RETN LimitedUnclassifiedIPv4122
AS39928Broadcasting TV Company "Studio 1+1"UnclassifiedIPv4105
AS215765"RADIO-LINK SMART" LLCUnclassifiedIPv451
AS24482SG.GSHostingIPv440
AS6939Hurricane Electric LLCTransitIPv410
AS7713PT Telekomunikasi IndonesiaResidentialIPv41

Provenance

Where this comes from

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