asn.dev

Observed topology

AS7682 HOTNET - HOKKAIDO TELECOMMUNICATIONS NETWORK Co., Inc.

Unclassified AFRINIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS7682: 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
AS2516KDDI CORPORATIONMobileIPv4 IPv6253
AS6939Hurricane Electric LLCTransitIPv453
AS4713NTT DOCOMO BUSINESS,Inc.ResidentialIPv4 IPv637
AS17676SoftBank Corp.MobileIPv4 IPv625
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv67
AS24482SG.GSHostingIPv4 IPv67
AS20485Joint Stock Company TransTeleComUnclassifiedIPv46

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS18141HBAUnclassifiedIPv47

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS2516KDDI CORPORATIONMobileIPv4 IPv6253
AS6939Hurricane Electric LLCTransitIPv454
AS4713NTT DOCOMO BUSINESS,Inc.ResidentialIPv4 IPv639
AS17676SoftBank Corp.MobileIPv4 IPv626
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv68
AS24482SG.GSHostingIPv4 IPv68
AS18141HBAUnclassifiedIPv47
AS20485Joint Stock Company TransTeleComUnclassifiedIPv47

Provenance

Where this comes from

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