asn.dev

Observed topology

AS47217 PLANETEL-SPA Planetel SPA

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS47217: 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
AS9002RETN LimitedUnclassifiedIPv4 IPv62,199
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6894
AS6939Hurricane Electric LLCTransitIPv4 IPv6630
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv669
AS24482SG.GSHostingIPv4 IPv669
AS59919Brainbox S.r.l.ResidentialIPv466

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS214443BE BYTE SRLResidentialIPv4 IPv616

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9002RETN LimitedUnclassifiedIPv4 IPv62,234
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6894
AS6939Hurricane Electric LLCTransitIPv4 IPv6630
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv669
AS24482SG.GSHostingIPv4 IPv669
AS59919Brainbox S.r.l.ResidentialIPv466
AS214443BE BYTE SRLResidentialIPv4 IPv635

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.