Observed topology

AS41160 ORIGINENET-AS

Unclassified RIPE Enterprise

Upstreams 6 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS41160: 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
AS12874	Fastweb SpA	Residential	IPv4	562
AS3257	GTT Communications Inc.	Transit	IPv4	338
AS24482	SG.GS	Hosting	IPv4	15
AS29075	IELO-LIAZO SERVICES SAS	Unclassified	IPv4	15
AS31543	myNet GmbH	Residential	IPv4	15
AS59919	Brainbox S.r.l.	Residential	IPv4	15

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS208000	Roberto Cardone trading as Megacom	Unclassified	IPv4	60

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS12874	Fastweb SpA	Residential	IPv4	599
AS3257	GTT Communications Inc.	Transit	IPv4	361
AS208000	Roberto Cardone trading as Megacom	Unclassified	IPv4	60
AS24482	SG.GS	Hosting	IPv4	15
AS29075	IELO-LIAZO SERVICES SAS	Unclassified	IPv4	15
AS31543	myNet GmbH	Residential	IPv4	15
AS59919	Brainbox S.r.l.	Residential	IPv4	15

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-28 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.