Network · data from 2026-11-12
AS135445 IDNIC-AIRPAY-AS-ID - PT. Airpay International Indonesia
Registry name: IDNIC-AIRPAY-AS-ID - PT. Airpay International Indonesia, ID · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS135445, 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.
| 124.158.137.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 202.73.16.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 103.69.177.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.69.178.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.223.1.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.223.3.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 124.158.131.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 124.158.140.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 124.158.141.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
AS-SET
AS135445 isn't in PeeringDB, where networks name their 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 22 are in fix.csv.
- ROA: origin2
- Route object: none2
- Route object: RIR7
- Route object: not announced11
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 124.158.137.0/24 | ROAs covering it name AS135462, not AS135445. If AS135445 should announce it, add a ROA for AS135445. |
| Route object: none | 124.158.137.0/24 | Route objects for it name AS135462. Add a route object with origin AS135445 in the RIR database for the space. |
| ROA: origin | 202.73.16.0/24 | ROAs covering it name AS58816, not AS135445. If AS135445 should announce it, add a ROA for AS135445. |
| Route object: none | 202.73.16.0/24 | Route objects for it name AS58816. Add a route object with origin AS135445 in the RIR database for the space. |
| Route object: RIR | 103.69.177.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.69.178.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.223.1.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.223.3.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 124.158.131.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 124.158.140.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 124.158.141.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 AS135445 whose prefix no peer sees AS135445 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.223.0.0/22 | NTTCOM, RADB | Valid |
| 103.223.0.0/24 | NTTCOM, RADB | Valid |
| 103.223.2.0/23 | NTTCOM, RADB | Valid |
| 103.223.2.0/24 | NTTCOM, RADB | Valid |
| 124.158.128.0/23 | NTTCOM, RADB | No ROA |
| 124.158.128.0/24 | NTTCOM, RADB | Valid |
| 124.158.129.0/24 | NTTCOM, RADB | Valid |
| 124.158.130.0/23 | NTTCOM, RADB | No ROA |
| 124.158.130.0/24 | NTTCOM, RADB | Valid |
| 124.158.132.0/24 | NTTCOM, RADB | Valid |
| 124.158.140.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.