asn.dev

Observed topology

AS58221 FGU-AS

Unclassified RIPE Enterprise

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS58221: 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
AS199995Omega Telecom LLCResidentialIPv448
AS9002RETN LimitedUnclassifiedIPv410
AS209116LLC "WEB PRO"UnclassifiedIPv44
AS50263A-Systems Sp. z o.o.UnclassifiedIPv43
AS24482SG.GSHostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS44630A1799 Military UnitUnclassifiedIPv466
AS212560LLC "ID STRATEGY"UnclassifiedIPv442
AS43332LLC "ID STRATEGY"UnclassifiedIPv48

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS199995Omega Telecom LLCResidentialIPv4132
AS44630A1799 Military UnitUnclassifiedIPv466
AS212560LLC "ID STRATEGY"UnclassifiedIPv442
AS9002RETN LimitedUnclassifiedIPv423
AS209116LLC "WEB PRO"UnclassifiedIPv414
AS50263A-Systems Sp. z o.o.UnclassifiedIPv412
AS43332LLC "ID STRATEGY"UnclassifiedIPv410
AS24482SG.GSHostingIPv43

Provenance

Where this comes from

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