Network · data from 2026-11-12
AS7499 MACROVIEW-HK-AS-AP - Macroview Telecom Limited
Registry name: MACROVIEW-HK-AS-AP - Macroview Telecom Limited, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS7499, 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.182.244.0/22 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 202.182.246.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 202.182.247.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 202.182.248.0/22 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 202.182.252.0/22 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 202.182.252.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 202.182.253.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
AS-SET
AS7499 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 38 are in fix.csv.
- ROA: none7
- Route object: RIR7
- Route object: not announced24
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 202.182.244.0/22 | No ROA covers it. Add a ROA for AS7499, maxLength 22. |
| Route object: RIR | 202.182.244.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 202.182.246.0/24 | No ROA covers it. Add a ROA for AS7499, maxLength 24. |
| Route object: RIR | 202.182.246.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 202.182.247.0/24 | No ROA covers it. Add a ROA for AS7499, maxLength 24. |
| Route object: RIR | 202.182.247.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 202.182.248.0/22 | No ROA covers it. Add a ROA for AS7499, maxLength 22. |
| Route object: RIR | 202.182.248.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 202.182.252.0/22 | No ROA covers it. Add a ROA for AS7499, maxLength 22. |
| Route object: RIR | 202.182.252.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 202.182.252.0/24 | No ROA covers it. Add a ROA for AS7499, maxLength 24. |
| Route object: RIR | 202.182.252.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 202.182.253.0/24 | No ROA covers it. Add a ROA for AS7499, maxLength 24. |
| Route object: RIR | 202.182.253.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 AS7499 whose prefix no peer sees AS7499 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 202.182.240.0/20 | RADB | No ROA |
| 202.182.240.0/22 | NTTCOM, RADB | No ROA |
| 202.182.240.0/23 | NTTCOM, RADB | No ROA |
| 202.182.240.0/24 | NTTCOM, RADB | No ROA |
| 202.182.241.0/24 | NTTCOM, RADB | No ROA |
| 202.182.242.0/23 | NTTCOM, RADB | No ROA |
| 202.182.242.0/24 | NTTCOM, RADB | No ROA |
| 202.182.243.0/24 | NTTCOM, RADB | No ROA |
| 202.182.244.0/23 | NTTCOM, RADB | No ROA |
| 202.182.244.0/24 | NTTCOM, RADB | No ROA |
| 202.182.245.0/24 | NTTCOM, RADB | No ROA |
| 202.182.246.0/23 | NTTCOM, RADB | No ROA |
| 202.182.248.0/23 | NTTCOM, RADB | No ROA |
| 202.182.248.0/24 | NTTCOM, RADB | No ROA |
| 202.182.249.0/24 | NTTCOM, RADB | No ROA |
| 202.182.250.0/23 | NTTCOM, RADB | No ROA |
| 202.182.250.0/24 | NTTCOM, RADB | No ROA |
| 202.182.251.0/24 | NTTCOM, RADB | No ROA |
| 202.182.252.0/23 | NTTCOM, RADB | No ROA |
| 202.182.254.0/23 | NTTCOM, RADB | No ROA |
| 202.182.254.0/24 | NTTCOM, RADB | No ROA |
| 202.182.255.0/24 | NTTCOM, RADB | No ROA |
| 2403:1c00::/32 | RADB | No ROA |
| 2403:1c00:f000::/36 | 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.