Network · data from 2026-11-12
AS38896 CERGIS
Registry name: CERGIS-AS-AP - PT. Centra Global Investama, ID · PeeringDB
58IPv4 routes
100.0% RPKI valid · 94.8% with a route object
1IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
3 with no route object for this origin
31Low visibility
seen by under 10% of full-table peers
82Route objects not announced
registered with origin AS38896, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS38896, 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.
| 103.2.144.0/23 | Valid | Nonecovered by 103.2.144.0/22 | 673 100% |
| 103.2.146.0/23 | Valid | Nonecovered by 103.2.144.0/22 | 673 100% |
| 122.129.110.0/23 | Valid | Nonecovered by 122.129.108.0/22 | 673 100% |
| 121.58.184.0/23 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 121.58.186.0/23 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 121.58.188.0/23 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 121.58.190.0/23 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 122.129.96.0/23 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 122.129.98.0/23 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 122.129.100.0/23 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 122.129.102.0/23 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 122.129.104.0/23 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 122.129.106.0/23 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 122.129.108.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 122.129.112.0/23 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 122.129.114.0/23 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 122.129.115.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 122.129.116.0/23 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 122.129.118.0/23 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 122.129.117.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 671 100% |
| 122.129.118.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 671 100% |
| 103.2.145.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 103.2.147.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 103.2.144.0/24 | Valid | Other IRR onlyRADB | 35 5%low visibility |
| 103.2.146.0/24 | Valid | Other IRR onlyRADB | 35 5%low visibility |
| 121.58.184.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 121.58.185.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 121.58.186.0/24 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 35 5%low visibility |
| 121.58.187.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 121.58.188.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 121.58.189.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 121.58.190.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 121.58.191.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 122.129.96.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 122.129.97.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 122.129.98.0/24 | Valid | Other IRR onlyRADB | 35 5%low visibility |
| 122.129.99.0/24 | Valid | Other IRR onlyRADB | 35 5%low visibility |
| 122.129.100.0/24 | Valid | Other IRR onlyRADB | 35 5%low visibility |
| 122.129.101.0/24 | Valid | Other IRR onlyRADB | 35 5%low visibility |
| 122.129.102.0/24 | Valid | Other IRR onlyRADB | 35 5%low visibility |
| 122.129.103.0/24 | Valid | Other IRR onlyRADB | 35 5%low visibility |
| 122.129.104.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 122.129.105.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 122.129.106.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 122.129.107.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 122.129.108.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 122.129.109.0/24 | Valid | Other IRR onlyRADB | 35 5%low visibility |
| 122.129.110.0/24 | Valid | Other IRR onlyRADB | 35 5%low visibility |
| 122.129.111.0/24 | Valid | Other IRR onlyRADB | 35 5%low visibility |
| 122.129.112.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 122.129.113.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 122.129.114.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 122.129.116.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 122.129.119.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 121.58.184.0/21 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 122.129.96.0/20 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 122.129.112.0/21 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 103.2.144.0/22 | Valid | RIR databaseAPNIC, NTTCOM | 669 99% |
| 2402:8600::/32 | Valid | RIR databaseAPNIC | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS38896: AS-CERGIS-AP. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS38896 isn't in the set, or no route object for AS38896 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS38896 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS-CERGIS-AP | In no IRR database read today. | |||||
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 137 are in fix.csv.
- Route object: none3
- Route object: RIR51
- AS-SET: not found1
- Route object: not announced82
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 103.2.144.0/23 | No route object for it. A route object for 103.2.144.0/22 with origin AS38896 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38896 in the RIR database for the space. |
| Route object: none | 103.2.146.0/23 | No route object for it. A route object for 103.2.144.0/22 with origin AS38896 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38896 in the RIR database for the space. |
| Route object: none | 122.129.110.0/23 | No route object for it. A route object for 122.129.108.0/22 with origin AS38896 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38896 in the RIR database for the space. |
| Route object: RIR | 121.58.184.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 121.58.186.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 121.58.188.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 121.58.190.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 122.129.96.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 122.129.98.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 122.129.100.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 122.129.102.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 122.129.104.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 122.129.106.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 122.129.108.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 122.129.112.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 122.129.114.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 122.129.115.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 122.129.116.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 122.129.118.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 122.129.117.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 122.129.118.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.2.145.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.2.147.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.2.144.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.2.146.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 121.58.184.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 121.58.185.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 121.58.186.0/24 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 121.58.187.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 121.58.188.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 121.58.189.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 121.58.190.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 121.58.191.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 122.129.96.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 122.129.97.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 122.129.98.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 122.129.99.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 122.129.100.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 122.129.101.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 122.129.102.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 122.129.103.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 122.129.104.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 122.129.105.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 122.129.106.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 122.129.107.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 122.129.108.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 122.129.109.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 122.129.110.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 122.129.111.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 122.129.112.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 122.129.113.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 122.129.114.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 122.129.116.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 122.129.119.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| AS-SET: not found | AS-CERGIS-AP | PeeringDB names AS-CERGIS-AP; no IRR database read has it. |
Route objects not announced
Route objects with origin AS38896 whose prefix no peer sees AS38896 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 116.213.24.0/21 | NTTCOM | No ROA |
| 116.213.24.0/22 | NTTCOM | No ROA |
| 116.213.24.0/23 | NTTCOM, RADB | No ROA |
| 116.213.24.0/24 | NTTCOM, RADB | No ROA |
| 116.213.25.0/24 | NTTCOM | No ROA |
| 116.213.26.0/23 | NTTCOM | No ROA |
| 116.213.26.0/24 | NTTCOM, RADB | No ROA |
| 116.213.27.0/24 | NTTCOM, RADB | No ROA |
| 116.213.28.0/22 | NTTCOM | No ROA |
| 116.213.28.0/23 | NTTCOM | No ROA |
| 116.213.28.0/24 | NTTCOM, RADB | No ROA |
| 116.213.29.0/24 | NTTCOM, RADB | No ROA |
| 116.213.30.0/23 | NTTCOM | No ROA |
| 116.213.30.0/24 | NTTCOM, RADB | No ROA |
| 116.213.31.0/24 | NTTCOM, RADB | No ROA |
| 117.103.8.0/21 | NTTCOM, RADB | No ROA |
| 117.103.10.0/23 | NTTCOM, RADB | No ROA |
| 117.103.12.0/22 | NTTCOM, RADB | No ROA |
| 121.58.184.0/22 | NTTCOM | Valid |
| 121.58.188.0/22 | NTTCOM | Valid |
| 122.58.184.0/21 | NTTCOM | No ROA |
| 122.58.184.0/22 | NTTCOM | No ROA |
| 122.58.184.0/23 | NTTCOM | No ROA |
| 122.58.184.0/24 | NTTCOM | No ROA |
| 122.58.185.0/24 | NTTCOM | No ROA |
| 122.58.186.0/23 | NTTCOM | No ROA |
| 122.58.186.0/24 | NTTCOM | No ROA |
| 122.58.187.0/24 | NTTCOM | No ROA |
| 122.58.188.0/22 | NTTCOM | No ROA |
| 122.58.188.0/23 | NTTCOM | No ROA |
| 122.58.188.0/24 | NTTCOM | No ROA |
| 122.58.189.0/24 | NTTCOM | No ROA |
| 122.58.190.0/23 | NTTCOM | No ROA |
| 122.58.190.0/24 | NTTCOM | No ROA |
| 122.58.191.0/24 | NTTCOM | No ROA |
| 122.129.96.0/21 | NTTCOM | Valid |
| 122.129.96.0/22 | NTTCOM, RADB | Valid |
| 122.129.100.0/22 | NTTCOM | Valid |
| 122.129.104.0/21 | NTTCOM | Valid |
| 122.129.104.0/22 | NTTCOM, RADB | Valid |
| 122.129.108.0/22 | NTTCOM | Valid |
| 122.129.112.0/22 | NTTCOM | Valid |
| 122.129.116.0/22 | NTTCOM | Valid |
| 202.67.32.0/20 | NTTCOM, RADB | No ROA |
| 202.89.208.0/20 | RADB | No ROA |
| 202.89.208.0/21 | RADB | No ROA |
| 202.89.208.0/22 | RADB | No ROA |
| 202.89.208.0/23 | RADB | No ROA |
| 202.89.209.0/24 | RADB | No ROA |
| 202.89.210.0/23 | RADB | No ROA |
| 202.89.210.0/24 | RADB | No ROA |
| 202.89.211.0/24 | RADB | No ROA |
| 202.89.212.0/22 | RADB | No ROA |
| 202.89.212.0/23 | RADB | No ROA |
| 202.89.212.0/24 | RADB | No ROA |
| 202.89.213.0/24 | RADB | No ROA |
| 202.89.214.0/23 | RADB | No ROA |
| 202.89.214.0/24 | RADB | No ROA |
| 202.89.215.0/24 | RADB | No ROA |
| 202.89.216.0/21 | RADB | No ROA |
| 202.89.216.0/22 | RADB | No ROA |
| 202.89.216.0/23 | RADB | No ROA |
| 202.89.216.0/24 | RADB | No ROA |
| 202.89.217.0/24 | RADB | No ROA |
| 202.89.218.0/23 | RADB | No ROA |
| 202.89.218.0/24 | RADB | No ROA |
| 202.89.219.0/24 | RADB | No ROA |
| 202.89.220.0/22 | RADB | No ROA |
| 202.89.220.0/23 | RADB | No ROA |
| 202.89.220.0/24 | RADB | No ROA |
| 202.89.221.0/24 | RADB | No ROA |
| 202.89.222.0/23 | RADB | No ROA |
| 202.89.222.0/24 | RADB | No ROA |
| 202.89.223.0/24 | RADB | No ROA |
| 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.