Network · data from 2026-11-12
AS38274 MEGAXUS-AS-ID-AP - PT. Megaxus Infotech
Registry name: MEGAXUS-AS-ID-AP - PT. Megaxus Infotech, ID · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS38274, 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.
| 122.102.53.0/24 | No ROA | Other origin onlycovered by 122.102.52.0/22 | 673 100% |
| 122.102.48.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 122.102.49.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 122.102.50.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 122.102.51.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 122.102.52.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 122.102.54.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 122.102.55.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
AS-SET
AS38274 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 23 are in fix.csv.
- ROA: none8
- Route object: none1
- Route object: RIR7
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 122.102.53.0/24 | No ROA covers it. Add a ROA for AS38274, maxLength 24. |
| Route object: none | 122.102.53.0/24 | Route objects for it name AS18059, AS24535. A route object for 122.102.52.0/22 with origin AS38274 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38274 in the RIR database for the space. |
| ROA: none | 122.102.48.0/24 | No ROA covers it. Add a ROA for AS38274, maxLength 24. |
| Route object: RIR | 122.102.48.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 122.102.49.0/24 | No ROA covers it. Add a ROA for AS38274, maxLength 24. |
| Route object: RIR | 122.102.49.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 122.102.50.0/24 | No ROA covers it. Add a ROA for AS38274, maxLength 24. |
| Route object: RIR | 122.102.50.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 122.102.51.0/24 | No ROA covers it. Add a ROA for AS38274, maxLength 24. |
| Route object: RIR | 122.102.51.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 122.102.52.0/24 | No ROA covers it. Add a ROA for AS38274, maxLength 24. |
| Route object: RIR | 122.102.52.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 122.102.54.0/24 | No ROA covers it. Add a ROA for AS38274, maxLength 24. |
| Route object: RIR | 122.102.54.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 122.102.55.0/24 | No ROA covers it. Add a ROA for AS38274, maxLength 24. |
| Route object: RIR | 122.102.55.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS38274 whose prefix no peer sees AS38274 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 122.102.48.0/21 | NTTCOM | No ROA |
| 122.102.48.0/22 | NTTCOM, RADB | No ROA |
| 122.102.48.0/23 | NTTCOM | No ROA |
| 122.102.50.0/23 | NTTCOM | No ROA |
| 122.102.52.0/22 | NTTCOM | No ROA |
| 122.102.54.0/23 | NTTCOM | No ROA |
| 202.93.21.0/24 | 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.