asn.dev

Observed topology

AS47242 HOST-SPA

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS47242: 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 LimitedUnclassifiedIPv4782
AS174Cogent Communications, LLCTransitIPv4492
AS21056Vianova S.p.AUnclassifiedIPv4418
AS6939Hurricane Electric LLCTransitIPv4331
AS3303Swisscom (Schweiz) AGResidentialIPv438
AS20766Association "Gitoyen"UnclassifiedIPv438
AS24482SG.GSHostingIPv438
AS59919Brainbox S.r.l.ResidentialIPv438
AS31543myNet GmbHResidentialIPv430

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS207799BOTANY SRLUnclassifiedIPv4234
AS43625Wi-Fi System di GianCarlo FornoUnclassifiedIPv4141
AS199125Alliance Reseaux SASUnclassifiedIPv424
AS42425PSA S.r.l.ResidentialIPv418

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS9002RETN LimitedUnclassifiedIPv4947
AS174Cogent Communications, LLCTransitIPv4622
AS21056Vianova S.p.AUnclassifiedIPv4450
AS6939Hurricane Electric LLCTransitIPv4363
AS207799BOTANY SRLUnclassifiedIPv4234
AS43625Wi-Fi System di GianCarlo FornoUnclassifiedIPv4141
AS59919Brainbox S.r.l.ResidentialIPv449
AS42425PSA S.r.l.ResidentialIPv448
AS3303Swisscom (Schweiz) AGResidentialIPv442
AS20766Association "Gitoyen"UnclassifiedIPv442

Provenance

Where this comes from

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