asn.dev

Observed topology

AS42239 FARLINE-AS

Unclassified RIPE

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS42239: 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
AS20764CJSC RASCOMUnclassifiedIPv4 IPv6107
AS31133PJSC MegaFonMobileIPv4 IPv698
AS57304JSC "RetnNet"UnclassifiedIPv440
AS6939Hurricane Electric LLCTransitIPv430
AS48084Uzhnie Magistraljnie Linii Svyazi LLCUnclassifiedIPv430
AS24482SG.GSHostingIPv4 IPv66
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv4 IPv66
AS12389PJSC RostelecomResidentialIPv65
AS37721Virtual Technologies & SolutionsResidentialIPv45
AS49673Truenetwork LLCUnclassifiedIPv45

All 11 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS34990Ltd. "Cypher"UnclassifiedIPv460

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS20764CJSC RASCOMUnclassifiedIPv4 IPv6127
AS31133PJSC MegaFonMobileIPv4 IPv6113
AS34990Ltd. "Cypher"UnclassifiedIPv460
AS57304JSC "RetnNet"UnclassifiedIPv448
AS6939Hurricane Electric LLCTransitIPv436
AS48084Uzhnie Magistraljnie Linii Svyazi LLCUnclassifiedIPv436
AS24482SG.GSHostingIPv4 IPv67
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv4 IPv67
AS37721Virtual Technologies & SolutionsResidentialIPv46
AS49673Truenetwork LLCUnclassifiedIPv46

All 12 adjacent →

Provenance

Where this comes from

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