asn.dev

Observed topology

AS10000 NCM Nagasaki Cable Media Inc.

Residential RIPE

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS10000: 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
AS2497Internet Initiative Japan Inc.UnclassifiedIPv4 IPv6462
AS7679QTnet,Inc.ResidentialIPv4422
AS2516KDDI CORPORATIONMobileIPv4 IPv6142
AS2519ARTERIA Networks CorporationUnclassifiedIPv486
AS2518BIGLOBE Inc.ResidentialIPv460
AS24482SG.GSHostingIPv4 IPv621
AS8966EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSCMobileIPv420
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv620
AS17676SoftBank Corp.MobileIPv420
AS20485Joint Stock Company TransTeleComUnclassifiedIPv420

All 11 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS18150NetComBB Co.,Ltd.UnclassifiedIPv469

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS2497Internet Initiative Japan Inc.UnclassifiedIPv4 IPv6486
AS7679QTnet,Inc.ResidentialIPv4445
AS2516KDDI CORPORATIONMobileIPv4 IPv6148
AS2519ARTERIA Networks CorporationUnclassifiedIPv496
AS18150NetComBB Co.,Ltd.UnclassifiedIPv469
AS2518BIGLOBE Inc.ResidentialIPv465
AS17676SoftBank Corp.MobileIPv421
AS24482SG.GSHostingIPv4 IPv621
AS8966EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSCMobileIPv420
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv620

All 12 adjacent →

Provenance

Where this comes from

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