asn.dev

Observed topology

AS202709 NETOIP

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS202709: 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
AS60798Servereasy SrlHostingIPv4 IPv6885
AS6939Hurricane Electric LLCTransitIPv4190
AS60822Wispone S.R.L.UnclassifiedIPv428
AS209992Telweb s.r.l.UnclassifiedIPv422
AS8218Zayo Infrastructure France SAUnclassifiedIPv419
AS24482SG.GSHostingIPv419
AS31543myNet GmbHResidentialIPv419
AS59919Brainbox S.r.l.ResidentialIPv419

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS200345SAMTEL NETWORK SRLUnclassifiedIPv458
AS44084Multiwire S.r.l.ResidentialIPv42

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS60798Servereasy SrlHostingIPv4 IPv6930
AS6939Hurricane Electric LLCTransitIPv4200
AS200345SAMTEL NETWORK SRLUnclassifiedIPv458
AS60822Wispone S.R.L.UnclassifiedIPv430
AS209992Telweb s.r.l.UnclassifiedIPv422
AS8218Zayo Infrastructure France SAUnclassifiedIPv420
AS24482SG.GSHostingIPv420
AS31543myNet GmbHResidentialIPv420
AS59919Brainbox S.r.l.ResidentialIPv420
AS44084Multiwire S.r.l.ResidentialIPv43

Provenance

Where this comes from

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