asn.dev

Observed topology

AS47408 MANDARIN-AS Mandarin S.p.A.

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS47408: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6158
AS174Cogent Communications, LLCTransitIPv4 IPv6111
AS24482SG.GSHostingIPv4 IPv66
AS59919Brainbox S.r.l.ResidentialIPv45
AS8218Zayo Infrastructure France SAUnclassifiedIPv43
AS31543myNet GmbHResidentialIPv43
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv42
AS29632Netassist International EOODUnclassifiedIPv61
AS196959NAMEX CONSORZIOUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS199362Wish Networks s.r.l.UnclassifiedIPv4118
AS209234Data Center S.R.L.UnclassifiedIPv463
AS213315Comune di MisterbiancoUnclassifiedIPv463
AS204280SIELTE S.P.A.UnclassifiedIPv427

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6379
AS174Cogent Communications, LLCTransitIPv4 IPv6157
AS199362Wish Networks s.r.l.UnclassifiedIPv4118
AS209234Data Center S.R.L.UnclassifiedIPv463
AS213315Comune di MisterbiancoUnclassifiedIPv463
AS204280SIELTE S.P.A.UnclassifiedIPv427
AS24482SG.GSHostingIPv4 IPv68
AS59919Brainbox S.r.l.ResidentialIPv47
AS8218Zayo Infrastructure France SAUnclassifiedIPv43
AS31543myNet GmbHResidentialIPv43

All 13 adjacent →

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.