asn.dev

Observed topology

AS213791 XENIAHOSTING

Residential RIPE NSP

Upstreams 7 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 9
Adjacent (IPv6) 7
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.

ASNetworkTypeFamiliesPaths seen
AS41327Fiber Telecom S.p.A.ResidentialIPv4 IPv6123
AS197071active 1 GmbHUnclassifiedIPv461
AS6939Hurricane Electric LLCTransitIPv4 IPv652
AS174Cogent Communications, LLCTransitIPv4 IPv641
AS59919Brainbox S.r.l.ResidentialIPv43
AS6204INTERKVM HOST SRLUnclassifiedIPv61
AS49581Ferdinand Zink trading as Tube-HostingHostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS218698XeniaGroup SRLUnclassifiedIPv4 IPv698

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS41327Fiber Telecom S.p.A.ResidentialIPv4 IPv6165
AS174Cogent Communications, LLCTransitIPv4 IPv6125
AS6939Hurricane Electric LLCTransitIPv4 IPv6110
AS218698XeniaGroup SRLUnclassifiedIPv4 IPv698
AS198064ZEROPACKETS LTDUnclassifiedIPv4 IPv689
AS197071active 1 GmbHUnclassifiedIPv461
AS59919Brainbox S.r.l.ResidentialIPv44
AS3257GTT Communications Inc.TransitIPv4 IPv62
AS6204INTERKVM HOST SRLUnclassifiedIPv61
AS49581Ferdinand Zink trading as Tube-HostingHostingIPv41

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-29 10:00 UTC by route-views2,rrc00, as seen from 76 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.