asn.dev

Observed topology

AS2527 So-net - Sony Network Communications Inc.

Residential RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS2527: 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
AS1299Arelion Sweden ABTransitIPv4 IPv61,714
AS6939Hurricane Electric LLCTransitIPv4 IPv6713
AS4637Telstra GlobalUnclassifiedIPv4 IPv6661
AS2516KDDI CORPORATIONMobileIPv4594
AS2497Internet Initiative Japan Inc.UnclassifiedIPv4521
AS24482SG.GSHostingIPv4 IPv676
AS3356Level 3 Parent, LLCTransitIPv474
AS132132MyRepublic Ltd.ResidentialIPv474
AS9002RETN LimitedUnclassifiedIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS9600So-net CorporationUnclassifiedIPv4 IPv6917
AS24278USEN CORPORATIONHostingIPv442

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv62,073
AS9600So-net CorporationUnclassifiedIPv4 IPv6917
AS6939Hurricane Electric LLCTransitIPv4 IPv6888
AS4637Telstra GlobalUnclassifiedIPv4 IPv6815
AS2516KDDI CORPORATIONMobileIPv4703
AS2497Internet Initiative Japan Inc.UnclassifiedIPv4634
AS24482SG.GSHostingIPv4 IPv692
AS132132MyRepublic Ltd.ResidentialIPv491
AS3356Level 3 Parent, LLCTransitIPv489
AS24278USEN CORPORATIONHostingIPv442

All 11 adjacent →

Provenance

Where this comes from

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