asn.dev

Observed topology

AS208920 RocketWay-AS Rocket Way S.R.L.

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS208920: 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
AS5398Internet one SRLUnclassifiedIPv4 IPv6171
AS20912Giuliano Claudio Peritore trading as "Panservice s.a.s. di Cuseo Fabrizio & C."ResidentialIPv4 IPv678
AS6939Hurricane Electric LLCTransitIPv440
AS24482SG.GSHostingIPv4 IPv66
AS29075IELO-LIAZO SERVICES SASUnclassifiedIPv44
AS31543myNet GmbHResidentialIPv44
AS59919Brainbox S.r.l.ResidentialIPv44
AS8218Zayo Infrastructure France SAUnclassifiedIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS39719Liguria Digitale S.p.A.UnclassifiedIPv459

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS5398Internet one SRLUnclassifiedIPv4 IPv6218
AS20912Giuliano Claudio Peritore trading as "Panservice s.a.s. di Cuseo Fabrizio & C."ResidentialIPv4 IPv690
AS39719Liguria Digitale S.p.A.UnclassifiedIPv459
AS6939Hurricane Electric LLCTransitIPv440
AS24482SG.GSHostingIPv4 IPv66
AS29075IELO-LIAZO SERVICES SASUnclassifiedIPv44
AS31543myNet GmbHResidentialIPv44
AS59919Brainbox S.r.l.ResidentialIPv44
AS8218Zayo Infrastructure France SAUnclassifiedIPv62

Provenance

Where this comes from

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