asn.dev

Observed topology

AS57521 SIMPLYSOFT-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS57521: 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
AS13030Init7 (Switzerland) Ltd.HostingIPv4 IPv6141
AS34927iFog GmbHHostingIPv4 IPv6134
AS58057Securebit AGUnclassifiedIPv4 IPv659
AS20473The Constant Company, LLCHostingIPv4 IPv641
AS357084b42 UGUnclassifiedIPv4 IPv67
AS56755Securebit AGUnclassifiedIPv4 IPv67
AS205794JINZE YANGUnclassifiedIPv66

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS202647Simplysoft GmbHUnclassifiedIPv633

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS13030Init7 (Switzerland) Ltd.HostingIPv4 IPv6141
AS34927iFog GmbHHostingIPv4 IPv6134
AS20473The Constant Company, LLCHostingIPv4 IPv674
AS58057Securebit AGUnclassifiedIPv4 IPv659
AS202647Simplysoft GmbHUnclassifiedIPv633
AS357084b42 UGUnclassifiedIPv4 IPv67
AS56755Securebit AGUnclassifiedIPv4 IPv67
AS205794JINZE YANGUnclassifiedIPv66

Provenance

Where this comes from

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