Skip to main content

AS10000

NCM

Nagasaki Cable Media Inc.

Registry

Authoritative registration data

AS number
10000
Name
NCM
Organisation
Nagasaki Cable Media Inc.
Country
Flag of Japan JP Japan
RIR
APNIC
Registered
—
Source:asn:rdap retrieved

IPv4 prefixes

20

IPv6 prefixes

1

Total announced

21

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS10000
114.134.128.0/19 IPv4 /19 not checked
163.131.32.0/19 IPv4 /19 RPKI valid
111.91.240.0/20 IPv4 /20 not checked
114.134.96.0/20 IPv4 /20 RPKI valid
126.52.0.0/20 IPv4 /20 not checked
202.169.64.0/20 IPv4 /20 not checked
202.169.80.0/20 IPv4 /20 RPKI valid
202.228.240.0/20 IPv4 /20 RPKI valid
203.129.96.0/20 IPv4 /20 RPKI valid
203.170.32.0/20 IPv4 /20 not checked
218.216.0.0/20 IPv4 /20 not checked
219.109.64.0/20 IPv4 /20 RPKI valid
61.114.96.0/20 IPv4 /20 not checked
61.206.208.0/20 IPv4 /20 not checked
14.1.8.0/21 IPv4 /21 not checked
180.214.224.0/21 IPv4 /21 RPKI valid
103.29.48.0/22 IPv4 /22 RPKI valid
203.215.56.0/22 IPv4 /22 not checked
203.217.156.0/22 IPv4 /22 RPKI valid
219.100.0.0/22 IPv4 /22 not checked
2405:ed00::/32 IPv6 /32 RPKI valid

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS10000
Address families
BBIX Amsterdam 1,000 Mbps IPv4 · IPv6
BBIX Fukuoka 10,000 Mbps IPv4 · IPv6
BBIX Hong Kong 1,000 Mbps IPv4 · IPv6
BBIX Osaka 100,000 Mbps IPv4 · IPv6
BBIX Singapore 1,000 Mbps IPv4 · IPv6
BBIX Tokyo 100,000 Mbps IPv4 · IPv6
BBIX US-West 1,000 Mbps IPv4 · IPv6
JPIX FUKUOKA 10,000 Mbps IPv4 · IPv6
JPIX OSAKA 100,000 Mbps IPv4 · IPv6
JPIX TOKYO 100,000 Mbps IPv4 · IPv6
JPNAP Fukuoka 100,000 Mbps IPv4 · IPv6
JPNAP Osaka 100,000 Mbps IPv4 · IPv6
JPNAP Tokyo: Peering 100,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS10000 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

10 networks seen before AS10000 in AS paths

Observed upstreams
Families
AS2497 IIJ 164 1,377
v4 v6
AS7679 QTNET 103 1,177
v4
AS2516 KDDI 139 640
v4 v6
AS2519 VECTANT 28 265
v4
AS2518 BIGLOBE 22 144
v4 v6
AS17676 GIGAINFRA 10 95
v4
AS8966 Etisalat-AS 3 60
v4
AS9002 RETN-AS 2 22
v4 v6
AS20485 TRANSTELECOM 1 20
v4
AS132132 REPUBLICTELECOM-SG 1 20
v4

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS10000 in AS paths

Observed downstreams
Families
AS18150 SNI-JP 162 201
v4

No rows match “”.

Showing – of

Uncertain adjacencies

11 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 61
v4 v6
AS49544 i3Dnet 1 41
v4 v6
AS2500 WIDE-BB 1 21
v4 v6
AS4777 APNIC-COLO 1 21
v4 v6
AS14907 WIKIMEDIA 1 21
v4 v6
AS35280 F5 1 21
v4 v6
AS59105 HOMENOC 1 21
v4 v6
AS17639 CONVERGE-AS 1 20
v4 v6
AS18106 VIEWQWEST-SG-AP 1 20
v4
AS199524 GCORE 1 20
v4
AS25152 K-ROOT-SERVER 1 1
v6

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.