asn.dev

Observed topology

AS207054 FLYNET-IT FLYNET SRL

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS207054: 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
AS1299Arelion Sweden ABTransitIPv4 IPv6197
AS6939Hurricane Electric LLCTransitIPv4 IPv6124
AS174Cogent Communications, LLCTransitIPv4 IPv695
AS3257GTT Communications Inc.TransitIPv4 IPv639
AS24482SG.GSHostingIPv4 IPv69
AS3303Swisscom (Schweiz) AGResidentialIPv47
AS59919Brainbox S.r.l.ResidentialIPv47
AS29632Netassist International EOODUnclassifiedIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS215288Michele BranchiniHostingIPv4 IPv695
AS210598Francesco Fabbro trading as Microweb SasUnclassifiedIPv4 IPv694

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6255
AS6939Hurricane Electric LLCTransitIPv4 IPv6200
AS174Cogent Communications, LLCTransitIPv4 IPv6127
AS215288Michele BranchiniHostingIPv4 IPv695
AS210598Francesco Fabbro trading as Microweb SasUnclassifiedIPv4 IPv694
AS3257GTT Communications Inc.TransitIPv4 IPv652
AS24482SG.GSHostingIPv4 IPv613
AS3303Swisscom (Schweiz) AGResidentialIPv49
AS59919Brainbox S.r.l.ResidentialIPv49
AS29632Netassist International EOODUnclassifiedIPv64

Provenance

Where this comes from

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