Network · data from 2026-11-12
AS135987 INDRA-RELOAD-AS-VN - Reload Company Limited
Registry name: INDRA-RELOAD-AS-VN - Reload Company Limited, VN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS135987, 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.142.218.0/23 | No ROA | Other IRR onlyNTTCOM | 2 0%low visibility |
| 103.116.104.0/22 | No ROA | RIR databaseAPNIC | 672 100% |
| 103.133.224.0/22 | No ROA | RIR databaseAPNIC | 672 100% |
| 103.142.138.0/23 | No ROA | RIR databaseAPNIC | 672 100% |
| 103.150.124.0/23 | No ROA | RIR databaseAPNIC | 672 100% |
| 103.154.100.0/23 | No ROA | RIR databaseAPNIC | 672 100% |
| 2001:df7:a900::/48 | No ROA | RIR databaseAPNIC | 636 100% |
| 103.127.196.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 672 100% |
| 103.127.197.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 2 0%low visibility |
AS-SET
AS135987 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 13 are in fix.csv.
- ROA: none7
- Route object: RIR1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.142.218.0/23 | No ROA covers it. Add a ROA for AS135987, maxLength 23. |
| Route object: RIR | 103.142.218.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 103.116.104.0/22 | No ROA covers it. Add a ROA for AS135987, maxLength 22. |
| ROA: none | 103.133.224.0/22 | No ROA covers it. Add a ROA for AS135987, maxLength 22. |
| ROA: none | 103.142.138.0/23 | No ROA covers it. Add a ROA for AS135987, maxLength 23. |
| ROA: none | 103.150.124.0/23 | No ROA covers it. Add a ROA for AS135987, maxLength 23. |
| ROA: none | 103.154.100.0/23 | No ROA covers it. Add a ROA for AS135987, maxLength 23. |
| ROA: none | 2001:df7:a900::/48 | No ROA covers it. Add a ROA for AS135987, maxLength 48. |
Route objects not announced
Route objects with origin AS135987 whose prefix no peer sees AS135987 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.127.196.0/22 | APNIC, NTTCOM | No ROA |
| 103.142.218.0/24 | NTTCOM | No ROA |
| 103.142.219.0/24 | NTTCOM | No ROA |
| 2404:26c0::/48 | APNIC, NTTCOM | No ROA |
| 2405:4340::/48 | APNIC, NTTCOM | 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.