asn.dev

Observed topology

AS4725 ODN - SoftBank Corp.

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS4725: 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
AS17676SoftBank Corp.MobileIPv4 IPv68,054

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS17505SoftBank Corp.UnclassifiedIPv4702
AS7514Computer Engineering & Consulting, Ltd.HostingIPv4438
AS23795Fitec Corp.UnclassifiedIPv4177
AS59121Asahi Kasei Networks CorporationUnclassifiedIPv4104
AS17509STARNET Co.,Ltd.UnclassifiedIPv4 IPv689
AS137269Novartis Singapore Pte LtdUnclassifiedIPv446
AS59116AIG Technologies KKUnclassifiedIPv4 IPv626
AS1370081120 Shimokuzawa Chuo-ku Sagamihara-shi Kanagawa-kenUnclassifiedIPv425
AS131989PFU LIMITEDUnclassifiedIPv421
AS37888HORIBA, Ltd.UnclassifiedIPv49

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS17676SoftBank Corp.MobileIPv4 IPv69,337
AS17505SoftBank Corp.UnclassifiedIPv4702
AS7514Computer Engineering & Consulting, Ltd.HostingIPv4438
AS2914NTT America, Inc.TransitIPv4354
AS23795Fitec Corp.UnclassifiedIPv4177
AS59121Asahi Kasei Networks CorporationUnclassifiedIPv4104
AS17509STARNET Co.,Ltd.UnclassifiedIPv4 IPv689
AS137269Novartis Singapore Pte LtdUnclassifiedIPv446
AS59116AIG Technologies KKUnclassifiedIPv4 IPv626
AS1370081120 Shimokuzawa Chuo-ku Sagamihara-shi Kanagawa-kenUnclassifiedIPv425

Provenance

Where this comes from

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