Network · data from 2026-11-12
AS58816 Garena Indonesia
Registry name: IDNIC-GARENA-AS-ID - PT Garena Indonesia, ID · PeeringDB
31IPv4 routes
93.5% RPKI valid · 93.5% with a route object
0IPv6 routes
2RPKI invalid
0 origin · 2 maxLength
0No ROA
2 with no route object for this origin
20Low visibility
seen by under 10% of full-table peers
16Route objects not announced
registered with origin AS58816, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS58816, 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.73.20.0/22 | Invalid: maxLength | Nonecovered by 202.73.16.0/21 | 183 27% |
| 202.73.22.0/23 | Invalid: maxLength | Nonecovered by 202.73.16.0/21 | 2 0%low visibility |
| 103.69.179.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 124.158.134.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 124.158.142.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 202.73.16.0/21 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 202.181.80.0/21 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.248.57.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 103.248.58.0/23 | Valid | Other IRR onlyRADB | 671 100% |
| 124.158.133.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 670 100% |
| 202.73.16.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 670 100% |
| 124.158.134.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 124.158.135.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 124.158.142.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 202.73.17.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 202.73.18.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 202.73.19.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 202.73.20.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 202.181.80.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 202.181.82.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 202.181.83.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 202.181.84.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 202.181.85.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 202.181.86.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 202.181.87.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 202.73.16.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 33 5%low visibility |
| 43.252.184.0/22 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
| 43.252.184.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 35 5%low visibility |
| 43.252.185.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 35 5%low visibility |
| 43.252.187.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 35 5%low visibility |
| 43.252.186.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 1 0%low visibility |
AS-SET
AS58816'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 44 are in fix.csv.
- ROA: maxLength2
- Route object: none2
- Route object: RIR24
- Route object: not announced16
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 202.73.20.0/22 | ROA 202.73.16.0/21 AS58816 has maxLength 21; the route is a /22. Raise the maxLength, or add a ROA for 202.73.20.0/22. |
| Route object: none | 202.73.20.0/22 | No route object for it. A route object for 202.73.16.0/21 with origin AS58816 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58816 in the RIR database for the space. |
| ROA: maxLength | 202.73.22.0/23 | ROA 202.73.16.0/21 AS58816 has maxLength 21; the route is a /23. Raise the maxLength, or add a ROA for 202.73.22.0/23. |
| Route object: none | 202.73.22.0/23 | No route object for it. A route object for 202.73.16.0/21 with origin AS58816 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58816 in the RIR database for the space. |
| Route object: RIR | 103.69.179.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 124.158.134.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 124.158.142.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.73.16.0/21 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.181.80.0/21 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.248.57.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.248.58.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 124.158.133.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.73.16.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 124.158.134.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 124.158.135.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 124.158.142.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.73.17.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.73.18.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.73.19.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.73.20.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.181.80.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.181.82.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.181.83.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.181.84.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.181.85.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.181.86.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.181.87.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.73.16.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS58816 whose prefix no peer sees AS58816 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.69.176.0/24 | NTTCOM, RADB | No ROA |
| 103.248.56.0/22 | RADB | No ROA |
| 103.248.56.0/24 | APNIC, RADB | Valid |
| 103.248.58.0/24 | RADB | Valid |
| 103.248.59.0/24 | RADB | Valid |
| 124.158.132.0/23 | RADB | No ROA |
| 124.158.143.0/24 | NTTCOM, RADB | Valid |
| 202.73.21.0/24 | NTTCOM, RADB | Valid |
| 202.73.22.0/24 | NTTCOM, RADB | Valid |
| 202.181.80.0/22 | NTTCOM, RADB | Valid |
| 202.181.80.0/24 | NTTCOM, RADB | Valid |
| 202.181.81.0/24 | NTTCOM, RADB | Valid |
| 202.181.82.0/23 | NTTCOM, RADB | Valid |
| 202.181.84.0/22 | NTTCOM, RADB | Valid |
| 202.181.84.0/23 | NTTCOM, RADB | Valid |
| 202.181.86.0/23 | NTTCOM, RADB | Valid |
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.