asn.dev

Observed topology

AS38074 SDCC-AS-AP SDCC Japan-West Area

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS38074: 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
AS150363SoftEther CorporationResidentialIPv4 IPv6215
AS59103SoftEther CorporationUnclassifiedIPv422
AS63798Industrial Cyber Security Center of ExcellenceUnclassifiedIPv418

Transit

Downstream networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS49867Shuji ItoUnclassifiedIPv4 IPv6263
AS58790SERVER-G GroupHostingIPv4 IPv6194
AS200455HOTARU NETWORK LTD.UnclassifiedIPv6132
AS39753Kai LiuUnclassifiedIPv6121
AS140868TakataSDCC NetHostingIPv674
AS150325TSUKUDANI NETWORKUnclassifiedIPv672
AS12198JSMSR NetworkUnclassifiedIPv665
AS38656LoutresUnclassifiedIPv636
AS38646NeodylandUnclassifiedIPv631
AS152873NeodylandUnclassifiedIPv628

All 14 downstreams →

Adjacency

Adjacent networks

All 19

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

ASNetworkTypeFamiliesPaths seen
AS150363SoftEther CorporationResidentialIPv4 IPv61,346
AS49867Shuji ItoUnclassifiedIPv4 IPv6263
AS58790SERVER-G GroupHostingIPv4 IPv6194
AS200455HOTARU NETWORK LTD.UnclassifiedIPv6132
AS39753Kai LiuUnclassifiedIPv6121
AS140868TakataSDCC NetHostingIPv674
AS150325TSUKUDANI NETWORKUnclassifiedIPv672
AS12198JSMSR NetworkUnclassifiedIPv665
AS150362Mamireimu Net Work'sUnclassifiedIPv4 IPv645
AS38656LoutresUnclassifiedIPv636

All 19 adjacent →

Provenance

Where this comes from

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