asn.dev

Observed topology

AS58321 OXYLION-AS Oxylion Sp. z o.o.

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS58321: 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
AS12741Netia SAResidentialIPv4462
AS1299Arelion Sweden ABTransitIPv4185
AS6939Hurricane Electric LLCTransitIPv498
AS3257GTT Communications Inc.TransitIPv484
AS24482SG.GSHostingIPv4 IPv623
AS20473The Constant Company, LLCHostingIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS29522Cyber_Folks S.A.HostingIPv41,607
AS41079Cyber_Folks S.A.HostingIPv4 IPv6514
AS29205VERCOM S.A.UnclassifiedIPv4128
AS34360Cyber_Folks S.A.HostingIPv4119
AS48760Cyber_Folks S.A.UnclassifiedIPv430

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS12741Netia SAResidentialIPv4 IPv61,715
AS29522Cyber_Folks S.A.HostingIPv41,607
AS1299Arelion Sweden ABTransitIPv4704
AS3257GTT Communications Inc.TransitIPv4 IPv6597
AS41079Cyber_Folks S.A.HostingIPv4 IPv6514
AS6939Hurricane Electric LLCTransitIPv4475
AS29205VERCOM S.A.UnclassifiedIPv4453
AS34360Cyber_Folks S.A.HostingIPv4119
AS24482SG.GSHostingIPv4 IPv664
AS48760Cyber_Folks S.A.UnclassifiedIPv430

All 14 adjacent →

Provenance

Where this comes from

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