asn.dev

Observed topology

AS21140 FLY-TELECOM-AS Fly Telecom LLC

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS21140: 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 IPv6141
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv638
AS8641LLC "Nauka-Svyaz"UnclassifiedIPv4 IPv625
AS50673Serverius Holding B.V.UnclassifiedIPv46
AS24482SG.GSHostingIPv4 IPv64
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv4 IPv64
AS37721Virtual Technologies & SolutionsResidentialIPv43
AS49673Truenetwork LLCUnclassifiedIPv43
AS62255BiMajLink d.o.o.UnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS43228SimpleTelecom LLCUnclassifiedIPv48

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS35598INETCOM CARRIER LLCUnclassifiedIPv4 IPv6141
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv642
AS8641LLC "Nauka-Svyaz"UnclassifiedIPv4 IPv625
AS43228SimpleTelecom LLCUnclassifiedIPv48
AS50673Serverius Holding B.V.UnclassifiedIPv46
AS37721Virtual Technologies & SolutionsResidentialIPv45
AS49673Truenetwork LLCUnclassifiedIPv45
AS24482SG.GSHostingIPv4 IPv64
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv4 IPv64
AS62255BiMajLink d.o.o.UnclassifiedIPv61

Provenance

Where this comes from

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