Network · data from 2026-11-12
AS38814 MEGA-VANTAGE-AS-AP - MEGA VANTAGE INFORMATION TECHNOLOGY (HONG KONG) LIMITED
Registry name: MEGA-VANTAGE-AS-AP - MEGA VANTAGE INFORMATION TECHNOLOGY (HONG KONG) LIMITED, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS38814, 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.60.248.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 45.120.180.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 45.120.181.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 45.120.182.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 45.120.183.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 103.60.249.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 103.60.250.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 123.49.245.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 123.49.195.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 666 99% |
AS-SET
AS38814 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 26 are in fix.csv.
- ROA: none7
- Route object: RIR9
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.60.248.0/24 | No ROA covers it. Add a ROA for AS38814, maxLength 24. |
| Route object: RIR | 103.60.248.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 45.120.180.0/24 | No ROA covers it. Add a ROA for AS38814, maxLength 24. |
| Route object: RIR | 45.120.180.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 45.120.181.0/24 | No ROA covers it. Add a ROA for AS38814, maxLength 24. |
| Route object: RIR | 45.120.181.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 45.120.182.0/24 | No ROA covers it. Add a ROA for AS38814, maxLength 24. |
| Route object: RIR | 45.120.182.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 45.120.183.0/24 | No ROA covers it. Add a ROA for AS38814, maxLength 24. |
| Route object: RIR | 45.120.183.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.60.249.0/24 | No ROA covers it. Add a ROA for AS38814, maxLength 24. |
| Route object: RIR | 103.60.249.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.60.250.0/24 | No ROA covers it. Add a ROA for AS38814, maxLength 24. |
| Route object: RIR | 103.60.250.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 123.49.245.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 123.49.195.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 AS38814 whose prefix no peer sees AS38814 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.120.180.0/22 | RADB | No ROA |
| 103.60.248.0/22 | RADB | No ROA |
| 103.60.251.0/24 | RADB | No ROA |
| 116.193.32.0/24 | NTTCOM, RADB | No ROA |
| 116.193.35.0/24 | NTTCOM, RADB | No ROA |
| 116.193.44.0/24 | NTTCOM, RADB | No ROA |
| 116.193.56.0/24 | NTTCOM, RADB | No ROA |
| 123.49.128.0/17 | NTTCOM, RADB | No ROA |
| 123.49.240.0/22 | RADB | No ROA |
| 202.89.0.0/22 | 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.