asn.dev

Observed topology

AS10000 NCM Nagasaki Cable Media Inc.

Upstreams 11 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 11
Adjacent (IPv6) 5

Transit

Upstream networks

inferred

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 IPv6496
AS7679QTnet,Inc.ResidentialIPv4401
AS2516KDDI CORPORATIONMobileIPv4 IPv6164
AS2518BIGLOBE Inc.ResidentialIPv480
AS2519ARTERIA Networks CorporationUnclassifiedIPv470
AS24482SG.GSHostingIPv4 IPv621
AS20485Joint Stock Company TransTeleComUnclassifiedIPv420
AS17676SoftBank Corp.MobileIPv420
AS8966EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSCMobileIPv420
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv620
AS38001NewMedia Express Pte LtdHostingIPv61

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.

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.UnclassifiedIPv450

Adjacency

Adjacent networks

16 shown

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

ASNetworkTypeFamiliesPaths seen
AS2497Internet Initiative Japan Inc.UnclassifiedIPv4 IPv6505
AS7679QTnet,Inc.ResidentialIPv4424
AS2516KDDI CORPORATIONMobileIPv4 IPv6172
AS2518BIGLOBE Inc.ResidentialIPv480
AS2519ARTERIA Networks CorporationUnclassifiedIPv479
AS18150NetComBB Co.,Ltd.UnclassifiedIPv450
AS17676SoftBank Corp.MobileIPv421
AS24482SG.GSHostingIPv4 IPv621
AS8966EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSCMobileIPv420
AS20485Joint Stock Company TransTeleComUnclassifiedIPv420
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv620
AS38001NewMedia Express Pte LtdHostingIPv61

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.

Interconnection

Exchange presence

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS10000, largest fabric first. An exchange is shared switching where networks interconnect directly rather than paying a transit provider to carry traffic between them, so turning up at one is a deliberate choice about how this network wants to be reached. Each name opens that exchange's own page, with its peering LANs and every other network recorded on it. Recorded at 6 exchanges across 3 countries and 1 region.

ExchangeLocationTheir addressMember ports
BroadBand Internet eXchange TokyoTokyo, Japan101.203.88.139358
JPIX TokyoTokyo, Japan210.171.224.141259
BroadBand Internet eXchange SingaporeSingapore, Singapore103.231.152.80151
BroadBand Internet eXchange OsakaOsaka, Japan218.100.9.34132
JPIX OsakaOsaka, Japan103.246.232.141114
BroadBand Internet eXchange Hong KongHong Kong, China103.203.158.80101

Unlike the tables above, this is recorded rather than inferred. An address on a peering LAN is at that exchange by definition. Two carve-outs all the same. Member ports counts every participant at the exchange, not this network's ports, so read it as a size proxy. And an absent exchange means PCH has no record of it, not that the network is not there.

Provenance

Where this comes from

Derived from routing tables collected at 2026-08-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.02M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.

Exchange presence comes from a separate dataset: the directory collected 2026-08-08 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,137 recorded member ports, licensed CC BY-NC-SA 3.0.

PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.