Observed topology

AS212559 LUMIA-AS LUMIA NETWORK SRL

Residential APNIC Cable/DSL/ISP

Upstreams 6 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 4

Upstream graph Who carries AS212559, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS212559 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS212559: 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
AS28716	Retelit Digital Services S.p.A.	Unclassified	IPv4 IPv6	186
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	75
AS24482	SG.GS	Hosting	IPv4 IPv6	6
AS8218	Zayo Infrastructure France SA	Unclassified	IPv6	3
AS31543	myNet GmbH	Residential	IPv4	3
AS59919	Brainbox S.r.l.	Residential	IPv4	3

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS210869	GLC NETCOM S.R.L	Unclassified	IPv4	150

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS28716	Retelit Digital Services S.p.A.	Unclassified	IPv4 IPv6	304
AS210869	GLC NETCOM S.R.L	Unclassified	IPv4	150
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	97
AS24482	SG.GS	Hosting	IPv4 IPv6	10
AS59919	Brainbox S.r.l.	Residential	IPv4	7
AS31543	myNet GmbH	Residential	IPv4	5
AS8218	Zayo Infrastructure France SA	Unclassified	IPv6	3

Provenance

Where this comes from

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