Observed topology

AS213791 XeniaGroup-SRL XeniaGroup SRL

Residential RIPE NSP

Upstreams 6 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS213791: 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 IPv6	121
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	54
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	41
AS49581	Ferdinand Zink trading as Tube-Hosting	Hosting	IPv4	3
AS59919	Brainbox S.r.l.	Residential	IPv4	3
AS197071	active 1 GmbH	Unclassified	IPv4	3

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS218698	XeniaGroup SRL	Unclassified	IPv4	61

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS41327	Fiber Telecom S.p.A.	Residential	IPv4 IPv6	155
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	106
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	84
AS198064	ZEROPACKETS LTD	Unclassified	IPv4 IPv6	69
AS218698	XeniaGroup SRL	Unclassified	IPv4	61
AS59919	Brainbox S.r.l.	Residential	IPv4	4
AS49581	Ferdinand Zink trading as Tube-Hosting	Hosting	IPv4	3
AS197071	active 1 GmbH	Unclassified	IPv4	3

Provenance

Where this comes from

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