asn.dev

Observed topology

AS393950 XIBER-LLC

Residential ARIN

Upstreams 10 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 11
Adjacent (IPv6) 8
Upstream graph Who carries AS393950, and who carries them, drawn as a map up to the transit-free core. 15 exchanges Where AS393950 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS393950: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv61,346
AS174Cogent Communications, LLCTransitIPv4 IPv6432
AS30600MetronetResidentialIPv459
AS852TELUS Communications Inc.ResidentialIPv4 IPv621
AS24482SG.GSHostingIPv4 IPv621
AS53767iCastCenterHostingIPv43
AS14907Wikimedia Foundation Inc.HostingIPv4 IPv62
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv62
AS971PureVoltage Hosting Inc.UnclassifiedIPv41
AS3130RGnet OUUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS22379Manifold Services IncUnclassifiedIPv4 IPv6101
AS397449HaywireResidentialIPv637

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv61,466
AS174Cogent Communications, LLCTransitIPv4 IPv6450
AS22379Manifold Services IncUnclassifiedIPv4 IPv6101
AS30600MetronetResidentialIPv459
AS397449HaywireResidentialIPv637
AS852TELUS Communications Inc.ResidentialIPv4 IPv621
AS24482SG.GSHostingIPv4 IPv621
AS53767iCastCenterHostingIPv43
AS14907Wikimedia Foundation Inc.HostingIPv4 IPv62
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv62

Provenance

Where this comes from

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