Observed topology

AS59766 ASWICITY WicitY srl

Residential RIPE Cable/DSL/ISP

Upstreams 3 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS59766: 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
AS41327	Fiber Telecom S.p.A.	Residential	IPv4	138
AS174	Cogent Communications, LLC	Transit	IPv4	39
AS12779	IT.Gate S.p.A.	Unclassified	IPv4	3

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS64420	NET WIRELESS S.R.L.	Unclassified	IPv4	59
AS58088	Italo Morellati trading as NETREALITY di Morellati Italo	Unclassified	IPv4	50

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS41327	Fiber Telecom S.p.A.	Residential	IPv4	223
AS64420	NET WIRELESS S.R.L.	Unclassified	IPv4	59
AS174	Cogent Communications, LLC	Transit	IPv4	55
AS58088	Italo Morellati trading as NETREALITY di Morellati Italo	Unclassified	IPv4	50
AS6939	Hurricane Electric LLC	Transit	IPv4	7
AS12779	IT.Gate S.p.A.	Unclassified	IPv4	4

Provenance

Where this comes from

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