Skip to main content

AS10010

TOKAI

TOKAI Communications Corporation

Registry

Authoritative registration data

AS number
10010
Name
TOKAI
Organisation
TOKAI Communications Corporation
Country
Flag of Japan JP Japan
RIR
APNIC
Registered
—
Source:asn:rdap retrieved

IPv4 prefixes

186

IPv6 prefixes

7

Total announced

193

Announced prefixes

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

Prefixes announced by AS10010
150.38.0.0/16 IPv4 /16 RPKI not found
164.162.0.0/16 IPv4 /16 RPKI not found
182.20.0.0/16 IPv4 /16 not checked
220.148.0.0/16 IPv4 /16 not checked
42.124.0.0/16 IPv4 /16 RPKI valid
42.126.0.0/16 IPv4 /16 not checked
59.84.0.0/16 IPv4 /16 RPKI valid
59.85.0.0/16 IPv4 /16 not checked
112.138.0.0/17 IPv4 /17 not checked
112.138.128.0/17 IPv4 /17 RPKI valid
112.139.0.0/17 IPv4 /17 not checked
112.139.128.0/17 IPv4 /17 RPKI valid
119.83.128.0/17 IPv4 /17 RPKI valid
120.137.128.0/17 IPv4 /17 RPKI valid
182.21.0.0/17 IPv4 /17 not checked
182.21.128.0/17 IPv4 /17 RPKI valid
183.86.0.0/17 IPv4 /17 RPKI valid
219.126.0.0/17 IPv4 /17 not checked
220.216.0.0/17 IPv4 /17 not checked
27.98.0.0/17 IPv4 /17 RPKI valid
42.125.0.0/17 IPv4 /17 not checked
42.127.0.0/17 IPv4 /17 RPKI valid
112.137.192.0/18 IPv4 /18 RPKI valid
116.254.0.0/18 IPv4 /18 not checked
117.104.0.0/18 IPv4 /18 not checked
119.83.0.0/18 IPv4 /18 not checked
119.83.64.0/18 IPv4 /18 not checked
120.136.192.0/18 IPv4 /18 not checked
124.47.192.0/18 IPv4 /18 RPKI valid
183.86.128.0/18 IPv4 /18 not checked
218.219.0.0/18 IPv4 /18 not checked
219.117.64.0/18 IPv4 /18 not checked
219.96.0.0/18 IPv4 /18 not checked
220.148.0.0/18 IPv4 /18 not checked
27.98.128.0/18 IPv4 /18 not checked
42.125.128.0/18 IPv4 /18 RPKI valid
42.127.128.0/18 IPv4 /18 RPKI valid
42.127.192.0/18 IPv4 /18 not checked
59.85.64.0/18 IPv4 /18 RPKI valid
59.86.0.0/18 IPv4 /18 not checked
59.86.64.0/18 IPv4 /18 not checked
116.254.64.0/19 IPv4 /19 RPKI valid
202.208.192.0/19 IPv4 /19 not checked
203.95.32.0/19 IPv4 /19 RPKI valid
210.146.96.0/19 IPv4 /19 RPKI valid
210.158.224.0/19 IPv4 /19 not checked
211.133.192.0/19 IPv4 /19 not checked
211.7.64.0/19 IPv4 /19 RPKI valid
219.106.192.0/19 IPv4 /19 not checked
219.112.160.0/19 IPv4 /19 not checked
219.124.128.0/19 IPv4 /19 RPKI valid
219.126.64.0/19 IPv4 /19 not checked
219.126.96.0/19 IPv4 /19 RPKI valid
220.148.64.0/19 IPv4 /19 RPKI valid
220.216.0.0/19 IPv4 /19 not checked
27.121.0.0/19 IPv4 /19 RPKI valid
42.125.192.0/19 IPv4 /19 not checked
59.85.224.0/19 IPv4 /19 not checked
59.86.128.0/19 IPv4 /19 RPKI valid
61.120.224.0/19 IPv4 /19 RPKI valid
61.198.96.0/19 IPv4 /19 not checked
61.200.96.0/19 IPv4 /19 RPKI valid
61.211.192.0/19 IPv4 /19 not checked
112.140.0.0/20 IPv4 /20 RPKI valid
112.140.16.0/20 IPv4 /20 RPKI valid
118.151.192.0/20 IPv4 /20 RPKI valid
133.186.0.0/20 IPv4 /20 not checked
133.186.32.0/20 IPv4 /20 RPKI valid
180.233.96.0/20 IPv4 /20 RPKI valid
202.136.192.0/20 IPv4 /20 RPKI valid
210.155.240.0/20 IPv4 /20 RPKI not found
210.171.160.0/20 IPv4 /20 not checked
210.171.240.0/20 IPv4 /20 not checked
210.4.240.0/20 IPv4 /20 RPKI valid
218.219.0.0/20 IPv4 /20 not checked
218.219.32.0/20 IPv4 /20 RPKI valid
218.40.208.0/20 IPv4 /20 not checked
219.112.176.0/20 IPv4 /20 not checked
219.96.16.0/20 IPv4 /20 RPKI valid
220.216.32.0/20 IPv4 /20 not checked
27.121.32.0/20 IPv4 /20 RPKI valid
27.121.48.0/20 IPv4 /20 not checked
61.198.112.0/20 IPv4 /20 RPKI valid
61.200.112.0/20 IPv4 /20 RPKI valid
61.206.64.0/20 IPv4 /20 not checked
61.211.176.0/20 IPv4 /20 not checked
110.172.56.0/21 IPv4 /21 RPKI valid
111.67.112.0/21 IPv4 /21 not checked
203.95.48.0/21 IPv4 /21 not checked
218.219.56.0/21 IPv4 /21 RPKI valid
219.96.32.0/21 IPv4 /21 RPKI valid
220.148.96.0/21 IPv4 /21 RPKI valid
220.216.48.0/21 IPv4 /21 RPKI valid
220.216.56.0/21 IPv4 /21 not checked
220.216.88.0/21 IPv4 /21 RPKI valid
42.125.232.0/21 IPv4 /21 not checked
42.125.240.0/21 IPv4 /21 not checked
61.198.104.0/21 IPv4 /21 not checked
103.239.216.0/22 IPv4 /22 not checked
103.239.92.0/22 IPv4 /22 not checked
103.4.68.0/22 IPv4 /22 not checked
103.41.240.0/22 IPv4 /22 not checked
103.51.80.0/22 IPv4 /22 RPKI not found
111.67.120.0/22 IPv4 /22 RPKI valid
111.67.124.0/22 IPv4 /22 RPKI valid
116.68.220.0/22 IPv4 /22 RPKI valid
133.186.48.0/22 IPv4 /22 not checked
180.149.204.0/22 IPv4 /22 not checked
202.222.0.0/22 IPv4 /22 RPKI not found
202.226.16.0/22 IPv4 /22 RPKI valid
203.114.228.0/22 IPv4 /22 RPKI valid
203.171.212.0/22 IPv4 /22 not checked
218.219.48.0/22 IPv4 /22 RPKI valid
219.96.60.0/22 IPv4 /22 RPKI valid
220.148.132.0/22 IPv4 /22 RPKI valid
220.148.180.0/22 IPv4 /22 RPKI valid
220.148.184.0/22 IPv4 /22 not checked
220.216.112.0/22 IPv4 /22 RPKI valid
220.216.120.0/22 IPv4 /22 not checked
220.216.124.0/22 IPv4 /22 not checked
220.216.84.0/22 IPv4 /22 RPKI valid
220.216.96.0/22 IPv4 /22 RPKI valid
42.125.228.0/22 IPv4 /22 not checked
42.125.252.0/22 IPv4 /22 RPKI valid
45.251.132.0/22 IPv4 /22 RPKI not found
103.217.136.0/23 IPv4 /23 not checked
103.37.10.0/23 IPv4 /23 not checked
116.68.218.0/23 IPv4 /23 RPKI valid
219.124.156.0/23 IPv4 /23 RPKI valid
220.148.188.0/23 IPv4 /23 not checked
220.216.100.0/23 IPv4 /23 RPKI valid
220.216.104.0/23 IPv4 /23 RPKI valid
220.216.106.0/23 IPv4 /23 not checked
220.216.68.0/23 IPv4 /23 RPKI valid
42.125.226.0/23 IPv4 /23 RPKI valid
42.125.248.0/23 IPv4 /23 RPKI valid
61.211.194.0/23 IPv4 /23 RPKI valid
103.136.196.0/24 IPv4 /24 not checked
103.136.197.0/24 IPv4 /24 not checked
103.136.198.0/24 IPv4 /24 RPKI not found
103.136.199.0/24 IPv4 /24 RPKI not found
103.26.34.0/24 IPv4 /24 not checked
103.41.60.0/24 IPv4 /24 not checked
103.97.208.0/24 IPv4 /24 RPKI not found
116.68.217.0/24 IPv4 /24 RPKI valid
124.47.193.0/24 IPv4 /24 RPKI valid
133.225.214.0/24 IPv4 /24 RPKI not found
150.96.0.0/24 IPv4 /24 RPKI not found
158.201.125.0/24 IPv4 /24 not checked
180.233.106.0/24 IPv4 /24 not checked
183.182.160.0/24 IPv4 /24 not checked
183.182.162.0/24 IPv4 /24 RPKI not found
193.151.111.0/24 IPv4 /24 RPKI valid
194.87.225.0/24 IPv4 /24 RPKI valid
202.216.27.0/24 IPv4 /24 not checked
202.216.76.0/24 IPv4 /24 RPKI not found
202.216.77.0/24 IPv4 /24 not checked
202.216.79.0/24 IPv4 /24 RPKI not found
202.222.4.0/24 IPv4 /24 RPKI not found
202.222.5.0/24 IPv4 /24 not checked
203.178.12.0/24 IPv4 /24 RPKI valid
219.106.221.0/24 IPv4 /24 RPKI valid
219.96.59.0/24 IPv4 /24 not checked
220.148.241.0/24 IPv4 /24 not checked
220.216.110.0/24 IPv4 /24 not checked
27.121.43.0/24 IPv4 /24 not checked
42.125.196.0/24 IPv4 /24 not checked
42.125.225.0/24 IPv4 /24 RPKI valid
42.125.234.0/24 IPv4 /24 RPKI valid
42.125.244.0/24 IPv4 /24 RPKI valid
42.125.245.0/24 IPv4 /24 not checked
42.125.251.0/24 IPv4 /24 RPKI valid
42.127.240.0/24 IPv4 /24 not checked
42.127.247.0/24 IPv4 /24 RPKI valid
42.127.250.0/24 IPv4 /24 RPKI valid
42.127.251.0/24 IPv4 /24 not checked
42.127.255.0/24 IPv4 /24 not checked
43.224.28.0/24 IPv4 /24 RPKI not found
45.120.79.0/24 IPv4 /24 not checked
45.90.85.0/24 IPv4 /24 RPKI valid
45.90.86.0/24 IPv4 /24 RPKI valid
45.90.87.0/24 IPv4 /24 not checked
59.84.16.0/24 IPv4 /24 RPKI valid
91.200.58.0/24 IPv4 /24 RPKI valid
94.74.184.0/24 IPv4 /24 not checked
94.74.185.0/24 IPv4 /24 RPKI valid
2406:bb00::/30 IPv6 /30 RPKI valid
2406:bb04::/30 IPv6 /30 not checked
2403:1f00::/32 IPv6 /32 RPKI not found
2403:7800::/32 IPv6 /32 RPKI valid
2401:af80::/33 IPv6 /33 not checked
2403:7800:2018::/48 IPv6 /48 RPKI valid
2403:7800:2019::/48 IPv6 /48 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 AS10010
Address families
BBIX Osaka 100,000 Mbps IPv4 · IPv6
BBIX Tokyo 200,000 Mbps IPv4 · IPv6
Equinix Tokyo 100,000 Mbps IPv4 · IPv6
JPIX OSAKA 40,000 Mbps IPv4 · IPv6
JPIX TOKYO 300,000 Mbps IPv4 · IPv6
JPNAP Tokyo: Peering 200,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 AS10010 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

17 networks seen before AS10010 in AS paths

Observed upstreams
Families
AS4637 ASN-TELSTRA-GLOBAL 5,021 24,111
v4 v6
AS174 COGENT-174 495 21,038
v4 v6
AS1299 TWELVE99 2,849 17,349
v4 v6
AS2497 IIJ 1,505 8,510
v4 v6
AS17676 GIGAINFRA 354 6,809
v4 v6
AS2518 BIGLOBE 161 6,617
v4 v6
AS6939 HURRICANE 336 4,623
v4
AS59103 SOFTETHER 73 2,807
v4 v6
AS8220 COLT 84 1,401
v4 v6
AS20485 TRANSTELECOM 80 997
v4
AS60068 CDN77 1 370
v4
AS132132 REPUBLICTELECOM-SG 47 366
v4
AS8966 Etisalat-AS 4 321
v4
AS9002 RETN-AS 27 270
v4 v6
AS9304 HUTCHISON-AS-AP 20 255
v4
AS18125 MAFFIN 5 5
v4
AS12389 ROSTELECOM-AS 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

41 networks seen after AS10010 in AS paths

Observed downstreams
Families
AS59103 SOFTETHER 864 5,040
v4 v6
AS23642 OBIS 1,505 4,696
v4 v6
AS4637 ASN-TELSTRA-GLOBAL 54 2,740
v6
AS23791 LCV 427 2,107
v4 v6
AS17953 ICO 459 2,013
v4 v6
AS131939 IPSISM-NET 284 1,663
v4
AS131915 WINDE 185 1,565
v4
AS146969 SBT-SC 319 1,427
v4 v6
AS9351 ZLAN 69 1,417
v4
AS63805 RIDC-NET 278 1,176
v4 v6
AS17678 WIND 457 1,025
v4 v6
AS23795 FURUKAWA 267 1,000
v4
AS7690 MIRAI 330 997
v4 v6
AS17683 WINTECH-COM 348 895
v4 v6
AS23836 RELNET 412 875
v4 v6
AS23639 ntt-bizlink 142 850
v4 v6
AS24257 JPIX-64ES 344 837
v4 v6
AS4678 FINE 298 836
v4 v6
AS55385 DA 329 825
v4 v6
AS23785 SUNFIELD 204 777
v4
AS133780 QMC-AS-AP 457 688
v4 v6
AS131946 MU-NET 264 622
v4
AS131156 LAC-AS 301 432
v4 v6
AS63779 JUSTPLAYER 141 362
v4
AS9990 NIandC 265 333
v4
AS38642 YOSHIZOU 264 333
v4
AS131940 BETANET 263 331
v4
AS132504 QUALITIA-AS-AP 256 327
v4
AS131934 ICC-NET 37 232
v4 v6
AS17947 S-UTOPIA 49 164
v4
AS18069 SOFTBANK 74 109
v4
AS55387 RMGR-MIX 35 108
v4
AS131910 SORACOM 22 102
v4
AS7522 STCN 13 96
v4 v6
AS18077 C-able 69 90
v4
AS24268 SAINS 37 61
v4
AS131945 SNTU-NET 41 58
v4
AS24271 iCTV 31 56
v4 v6
AS17676 GIGAINFRA 9 35
v6
AS2497 IIJ 6 14
v6
AS2518 BIGLOBE 1 1
v6

No rows match “”.

Showing – of

Uncertain adjacencies

40 adjacencies that may be an artefact of collector peering

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.