Observed topology

AS12445 SPIDERNET-AS

Unclassified RIPE

Upstreams 6 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 10

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.

AS	Network	Type	Families	Paths seen
AS1299	Arelion Sweden AB	Transit	IPv4	621
AS6939	Hurricane Electric LLC	Transit	IPv4	62
AS24482	SG.GS	Hosting	IPv4	5
AS59919	Brainbox S.r.l.	Residential	IPv4	5
AS8218	Zayo Infrastructure France SA	Unclassified	IPv4	3
AS31543	myNet GmbH	Residential	IPv4	3

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS42538	COMUNE DI BRESCIA	Unclassified	IPv4	96
AS5382	PLANET SERVICE SRL	Unclassified	IPv4	59
AS28831	Phoenix Informatica SRL	Unclassified	IPv4	59

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS1299	Arelion Sweden AB	Transit	IPv4	1,070
AS25002	A2A Smart City S.P.A	Residential	IPv4	235
AS42538	COMUNE DI BRESCIA	Unclassified	IPv4	96
AS6939	Hurricane Electric LLC	Transit	IPv4	62
AS5382	PLANET SERVICE SRL	Unclassified	IPv4	59
AS28831	Phoenix Informatica SRL	Unclassified	IPv4	59
AS24482	SG.GS	Hosting	IPv4	5
AS59919	Brainbox S.r.l.	Residential	IPv4	5
AS8218	Zayo Infrastructure France SA	Unclassified	IPv4	3
AS31543	myNet GmbH	Residential	IPv4	3

Provenance

Where this comes from

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