Network · data from 2026-11-12
AS23696 Asia Utama
Registry name: FIRSTASIANET-AS-ID - PT Asia Akses Utama, ID · PeeringDB
17IPv4 routes
100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
0 with no route object for this origin
13Low visibility
seen by under 10% of full-table peers
24Route objects not announced
registered with origin AS23696, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS23696, 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.93.112.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 202.93.116.0/22 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 202.93.120.0/22 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 202.93.124.0/22 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 202.93.112.0/24 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 35 5%low visibility |
| 202.93.113.0/24 | Valid | Other IRR onlyNTTCOM, REACH | 35 5%low visibility |
| 202.93.114.0/24 | Valid | Other IRR onlyNTTCOM, REACH | 35 5%low visibility |
| 202.93.115.0/24 | Valid | Other IRR onlyNTTCOM, REACH | 35 5%low visibility |
| 202.93.116.0/24 | Valid | Other IRR onlyNTTCOM, REACH | 35 5%low visibility |
| 202.93.117.0/24 | Valid | Other IRR onlyNTTCOM, REACH | 35 5%low visibility |
| 202.93.118.0/24 | Valid | Other IRR onlyNTTCOM, REACH | 35 5%low visibility |
| 202.93.119.0/24 | Valid | Other IRR onlyNTTCOM, REACH | 35 5%low visibility |
| 202.93.120.0/24 | Valid | Other IRR onlyNTTCOM, REACH | 35 5%low visibility |
| 202.93.121.0/24 | Valid | Other IRR onlyNTTCOM, REACH | 35 5%low visibility |
| 202.93.122.0/24 | Valid | Other IRR onlyNTTCOM | 35 5%low visibility |
| 202.93.123.0/24 | Valid | Other IRR onlyNTTCOM | 35 5%low visibility |
| 202.93.124.0/24 | Valid | Other IRR onlyNTTCOM, REACH | 35 5%low visibility |
AS-SET
AS23696'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 41 are in fix.csv.
- Route object: RIR17
- Route object: not announced24
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 202.93.112.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.93.116.0/22 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 202.93.120.0/22 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 202.93.124.0/22 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 202.93.112.0/24 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 202.93.113.0/24 | Route object only in NTTCOM, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 202.93.114.0/24 | Route object only in NTTCOM, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 202.93.115.0/24 | Route object only in NTTCOM, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 202.93.116.0/24 | Route object only in NTTCOM, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 202.93.117.0/24 | Route object only in NTTCOM, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 202.93.118.0/24 | Route object only in NTTCOM, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 202.93.119.0/24 | Route object only in NTTCOM, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 202.93.120.0/24 | Route object only in NTTCOM, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 202.93.121.0/24 | Route object only in NTTCOM, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 202.93.122.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 202.93.123.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 202.93.124.0/24 | Route object only in NTTCOM, REACH. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS23696 whose prefix no peer sees AS23696 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 117.103.8.0/21 | NTTCOM, RADB | No ROA |
| 202.67.32.0/20 | NTTCOM, RADB | No ROA |
| 202.93.112.0/20 | NTTCOM, RADB | Valid |
| 202.93.112.0/21 | NTTCOM, RADB | Valid |
| 202.93.112.0/23 | NTTCOM, RADB | Valid |
| 202.93.114.0/23 | NTTCOM | Valid |
| 202.93.116.0/23 | NTTCOM | Valid |
| 202.93.118.0/23 | NTTCOM | Valid |
| 202.93.120.0/21 | NTTCOM | Valid |
| 202.93.120.0/23 | NTTCOM | Valid |
| 202.93.122.0/23 | NTTCOM | Valid |
| 202.93.124.0/23 | NTTCOM | Valid |
| 202.93.125.0/24 | NTTCOM | Valid |
| 202.93.126.0/23 | NTTCOM | Valid |
| 202.93.126.0/24 | NTTCOM | Valid |
| 202.93.127.0/24 | NTTCOM | Valid |
| 202.93.224.0/20 | NTTCOM, RADB | No ROA |
| 202.93.240.0/21 | NTTCOM, RADB | No ROA |
| 202.123.224.0/20 | NTTCOM, RADB | No ROA |
| 202.148.0.0/19 | NTTCOM, RADB | No ROA |
| 202.159.0.0/17 | NTTCOM, RADB | No ROA |
| 202.160.254.0/24 | NTTCOM, RADB | No ROA |
| 202.180.48.0/21 | RADB | No ROA |
| 203.201.160.0/20 | 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.