Network · data from 2026-11-12
AS23678 MyKRIS ASIA KL
Registry name: MYKRIS-AS-MY - Enterprise Managed Services Sdn. Bhd., MY · PeeringDB
102IPv4 routes
100.0% RPKI valid · 100.0% with a route object
4IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
0 with no route object for this origin
3Low visibility
seen by under 10% of full-table peers
96Route objects not announced
registered with origin AS23678, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS23678, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 202.133.96.0/24 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 673 100% |
| 27.131.60.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 202.133.102.0/23 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 672 100% |
| 202.133.104.0/22 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 672 100% |
| 202.133.104.0/23 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 672 100% |
| 202.133.104.0/24 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 672 100% |
| 202.133.105.0/24 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 672 100% |
| 202.133.106.0/23 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 672 100% |
| 202.133.106.0/24 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 672 100% |
| 202.133.107.0/24 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 672 100% |
| 27.131.32.0/19 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 27.131.32.0/20 | Valid | RIR databaseAPNIC, RADB, REACH | 672 100% |
| 27.131.32.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 27.131.33.0/24 | Valid | RIR databaseAPNIC, RADB, REACH | 672 100% |
| 27.131.34.0/24 | Valid | RIR databaseAPNIC, RADB, REACH | 672 100% |
| 27.131.35.0/24 | Valid | RIR databaseAPNIC, RADB, REACH | 672 100% |
| 27.131.36.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 27.131.37.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 27.131.38.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 27.131.39.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 27.131.40.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 27.131.40.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 27.131.41.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 27.131.42.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 27.131.43.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 27.131.44.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 27.131.45.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 27.131.46.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 27.131.47.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 27.131.48.0/21 | Valid | RIR databaseAPNIC, RADB, REACH | 672 100% |
| 27.131.48.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 27.131.49.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 27.131.50.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 27.131.51.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 27.131.52.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 27.131.53.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 27.131.54.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 27.131.55.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 27.131.56.0/22 | Valid | RIR databaseAPNIC, RADB, REACH | 672 100% |
| 27.131.56.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 27.131.57.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 27.131.58.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 27.131.59.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 27.131.60.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 27.131.61.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 43.252.44.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 43.252.44.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 43.252.45.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 43.252.46.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 43.252.47.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 103.12.64.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 103.12.64.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 103.12.64.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 103.12.65.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 103.12.66.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 103.12.67.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 103.137.120.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 672 100% |
| 103.137.121.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 672 100% |
| 103.137.122.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 672 100% |
| 103.137.123.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 672 100% |
| 103.221.60.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.221.61.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.221.62.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.243.192.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 103.243.192.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 103.243.193.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.243.194.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 122.0.16.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 122.0.16.0/21 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 122.0.16.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 122.0.17.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 122.0.18.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 122.0.19.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 122.0.20.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 122.0.21.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 122.0.22.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 122.0.22.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 122.0.23.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 122.0.24.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 122.0.24.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 122.0.25.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 122.0.26.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 122.0.27.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 122.0.28.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 122.0.28.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 122.0.29.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 122.0.30.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 150.107.157.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 150.107.158.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 150.107.159.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 202.133.96.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 202.133.96.0/21 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 202.133.96.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 202.133.97.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 202.133.98.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 202.133.99.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 202.133.100.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 202.133.100.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 202.133.101.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 202.133.102.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 202.133.103.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 150.107.156.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 670 100% |
| 2405:6400::/32 | Valid | RIR databaseAPNIC, RADB | 635 100% |
| 2405:6400::/36 | Valid | RIR databaseAPNIC | 1 0%low visibility |
| 2405:6400::/42 | Valid | RIR databaseAPNIC | 1 0%low visibility |
| 2405:6400:1000::/36 | Valid | RIR databaseAPNIC | 1 0%low visibility |
AS-SET
AS23678's PeeringDB record names no AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 106 are in fix.csv.
- Route object: RIR10
- Route object: not announced96
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 202.133.96.0/24 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 27.131.60.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.133.102.0/23 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 202.133.104.0/22 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 202.133.104.0/23 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 202.133.104.0/24 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 202.133.105.0/24 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 202.133.106.0/23 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 202.133.106.0/24 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 202.133.107.0/24 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS23678 whose prefix no peer sees AS23678 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 27.131.32.0/21 | NTTCOM, RADB | Valid |
| 27.131.32.0/22 | NTTCOM, RADB | Valid |
| 27.131.32.0/23 | NTTCOM, RADB | Valid |
| 27.131.34.0/23 | NTTCOM, RADB | Valid |
| 27.131.36.0/22 | NTTCOM, RADB | Valid |
| 27.131.36.0/23 | NTTCOM, RADB | Valid |
| 27.131.38.0/23 | NTTCOM, RADB | Valid |
| 27.131.40.0/21 | NTTCOM, RADB | Valid |
| 27.131.40.0/22 | NTTCOM, RADB | Valid |
| 27.131.42.0/23 | NTTCOM, RADB | Valid |
| 27.131.44.0/22 | NTTCOM, RADB | Valid |
| 27.131.44.0/23 | NTTCOM, RADB | Valid |
| 27.131.46.0/23 | NTTCOM, RADB | Valid |
| 27.131.48.0/20 | NTTCOM, RADB | Valid |
| 27.131.48.0/22 | NTTCOM, RADB | Valid |
| 27.131.48.0/23 | NTTCOM, RADB | Valid |
| 27.131.50.0/23 | NTTCOM, RADB | Valid |
| 27.131.52.0/22 | NTTCOM, RADB | Valid |
| 27.131.52.0/23 | NTTCOM, RADB | Valid |
| 27.131.54.0/23 | NTTCOM, RADB | Valid |
| 27.131.56.0/21 | NTTCOM, RADB | Valid |
| 27.131.56.0/23 | NTTCOM, RADB | Valid |
| 27.131.58.0/23 | NTTCOM, RADB | Valid |
| 27.131.60.0/22 | NTTCOM, RADB | Valid |
| 27.131.62.0/23 | NTTCOM, RADB | Valid |
| 27.131.62.0/24 | NTTCOM, RADB | Valid |
| 27.131.63.0/24 | NTTCOM, RADB | Valid |
| 43.252.44.0/23 | APNIC, NTTCOM, RADB | Valid |
| 103.5.105.0/24 | NTTCOM, RADB | No ROA |
| 103.137.120.0/22 | APNIC, NTTCOM | Valid |
| 103.137.120.0/23 | APNIC, NTTCOM | Valid |
| 103.137.122.0/23 | APNIC, NTTCOM | Valid |
| 103.221.60.0/22 | APNIC, NTTCOM, RADB | Valid |
| 103.221.60.0/23 | APNIC, RADB | Valid |
| 103.221.62.0/23 | APNIC, RADB | Valid |
| 103.235.28.0/22 | NTTCOM, RADB | No ROA |
| 103.235.28.0/23 | NTTCOM, RADB | No ROA |
| 103.235.28.0/24 | NTTCOM, RADB | No ROA |
| 103.235.29.0/24 | NTTCOM, RADB | No ROA |
| 103.235.30.0/23 | NTTCOM, RADB | No ROA |
| 103.235.30.0/24 | NTTCOM, RADB | No ROA |
| 103.235.31.0/24 | NTTCOM, RADB | No ROA |
| 122.0.16.0/22 | NTTCOM, RADB | Valid |
| 122.0.16.0/23 | NTTCOM, RADB | Valid |
| 122.0.18.0/23 | NTTCOM, RADB | Valid |
| 122.0.20.0/22 | NTTCOM, RADB | Valid |
| 122.0.20.0/23 | NTTCOM, RADB | Valid |
| 122.0.24.0/21 | NTTCOM, RADB | Valid |
| 122.0.24.0/23 | NTTCOM, RADB | Valid |
| 122.0.26.0/23 | NTTCOM, RADB | Valid |
| 122.0.28.0/22 | NTTCOM, RADB | Valid |
| 122.0.30.0/23 | NTTCOM, RADB | Valid |
| 122.0.31.0/24 | NTTCOM, RADB | Valid |
| 150.107.156.0/22 | APNIC, NTTCOM, RADB | Valid |
| 202.133.96.0/23 | NTTCOM, RADB | Valid |
| 202.133.98.0/23 | NTTCOM, RADB | Valid |
| 202.133.100.0/22 | NTTCOM, RADB | Valid |
| 202.133.104.0/21 | NTTCOM, RADB | Valid |
| 202.133.108.0/22 | NTTCOM, RADB | Valid |
| 202.133.108.0/23 | NTTCOM, RADB | Valid |
| 202.133.108.0/24 | NTTCOM, RADB | Valid |
| 202.133.109.0/24 | NTTCOM, RADB | Valid |
| 202.133.110.0/23 | NTTCOM, RADB | Valid |
| 202.133.110.0/24 | NTTCOM, RADB | Valid |
| 202.133.111.0/24 | NTTCOM, RADB | Valid |
| 202.171.32.0/20 | NTTCOM, RADB | No ROA |
| 202.171.32.0/21 | NTTCOM, RADB | No ROA |
| 202.171.32.0/22 | NTTCOM, RADB | No ROA |
| 202.171.32.0/23 | NTTCOM, RADB | No ROA |
| 202.171.32.0/24 | NTTCOM, RADB | No ROA |
| 202.171.33.0/24 | NTTCOM, RADB | No ROA |
| 202.171.34.0/23 | NTTCOM, RADB | No ROA |
| 202.171.34.0/24 | NTTCOM, RADB | No ROA |
| 202.171.35.0/24 | NTTCOM, RADB | No ROA |
| 202.171.36.0/22 | NTTCOM, RADB | No ROA |
| 202.171.36.0/23 | NTTCOM, RADB | No ROA |
| 202.171.36.0/24 | NTTCOM, RADB | No ROA |
| 202.171.37.0/24 | NTTCOM, RADB | No ROA |
| 202.171.38.0/23 | NTTCOM, RADB | No ROA |
| 202.171.38.0/24 | NTTCOM, RADB | No ROA |
| 202.171.39.0/24 | NTTCOM, RADB | No ROA |
| 202.171.40.0/21 | NTTCOM, RADB | No ROA |
| 202.171.40.0/22 | NTTCOM, RADB | No ROA |
| 202.171.40.0/23 | NTTCOM, RADB | No ROA |
| 202.171.40.0/24 | NTTCOM, RADB | No ROA |
| 202.171.41.0/24 | NTTCOM, RADB | No ROA |
| 202.171.42.0/23 | NTTCOM, RADB | No ROA |
| 202.171.42.0/24 | NTTCOM, RADB | No ROA |
| 202.171.43.0/24 | NTTCOM, RADB | No ROA |
| 202.171.44.0/22 | NTTCOM, RADB | No ROA |
| 202.171.44.0/23 | NTTCOM, RADB | No ROA |
| 202.171.44.0/24 | NTTCOM, RADB | No ROA |
| 202.171.45.0/24 | NTTCOM, RADB | No ROA |
| 202.171.46.0/23 | NTTCOM, RADB | No ROA |
| 202.171.46.0/24 | NTTCOM, RADB | No ROA |
| 202.171.47.0/24 | APNIC, NTTCOM, RADB | No ROA |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.