asn.dev

Observed topology

AS150325 TSUKUDANI-NETWORK - TSUKUDANI NETWORK

Unclassified APNIC Non-Profit

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS150325: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv677
AS38074SDCC Japan-West AreaUnclassifiedIPv670
AS150369TelHi CorporationUnclassifiedIPv445
AS63798Industrial Cyber Security Center of ExcellenceUnclassifiedIPv48
AS357084b42 UGUnclassifiedIPv63
AS37989DCS1 Pte. Ltd.HostingIPv63
AS24482SG.GSHostingIPv61
AS34549meerfarbig GmbH & Co. KGHostingIPv61
AS56662Marcin GondekUnclassifiedIPv61
AS199854Jens ThiesUnclassifiedIPv61

All 11 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS152184Tamukai NetworkUnclassifiedIPv459

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS150369TelHi CorporationUnclassifiedIPv4104
AS6939Hurricane Electric LLCTransitIPv4 IPv677
AS38074SDCC Japan-West AreaUnclassifiedIPv670
AS152184Tamukai NetworkUnclassifiedIPv459
AS63798Industrial Cyber Security Center of ExcellenceUnclassifiedIPv48
AS357084b42 UGUnclassifiedIPv63
AS37989DCS1 Pte. Ltd.HostingIPv63
AS24482SG.GSHostingIPv61
AS34549meerfarbig GmbH & Co. KGHostingIPv61
AS56662Marcin GondekUnclassifiedIPv61

All 12 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.