asn.dev

Observed topology

AS12445 SPIDERNET-AS A2A Smart City S.P.A

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS12445: 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
AS1299Arelion Sweden ABTransitIPv4621
AS28716Retelit Digital Services S.p.A.UnclassifiedIPv458
AS6939Hurricane Electric LLCTransitIPv448
AS24482SG.GSHostingIPv44
AS29075IELO-LIAZO SERVICES SASUnclassifiedIPv44
AS59919Brainbox S.r.l.ResidentialIPv44
AS31543myNet GmbHResidentialIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS42538COMUNE DI BRESCIAUnclassifiedIPv4107
AS5382PLANET SERVICE SRLUnclassifiedIPv459
AS28831Phoenix Informatica SRLUnclassifiedIPv459
AS213178WhiteReady S.r.l. Societa' BenefitHostingIPv458

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv41,078
AS25002A2A Smart City S.P.AResidentialIPv4174
AS42538COMUNE DI BRESCIAUnclassifiedIPv4107
AS5382PLANET SERVICE SRLUnclassifiedIPv459
AS28831Phoenix Informatica SRLUnclassifiedIPv459
AS28716Retelit Digital Services S.p.A.UnclassifiedIPv458
AS213178WhiteReady S.r.l. Societa' BenefitHostingIPv458
AS6939Hurricane Electric LLCTransitIPv448
AS24482SG.GSHostingIPv44
AS29075IELO-LIAZO SERVICES SASUnclassifiedIPv44

All 12 adjacent →

Provenance

Where this comes from

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