Network · data from 2026-11-12
AS24399 ABN-PEERING-AS-AP - Asia Broadcast Networks Peering AS
Registry name: ABN-PEERING-AS-AP - Asia Broadcast Networks Peering AS, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS24399, 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.133.10.0/24 | Invalid: maxLength | Nonecovered by 202.133.8.0/21 | 2 0%low visibility |
| 203.80.176.0/24 | No ROA | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 203.80.178.0/24 | No ROA | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 203.80.179.0/24 | No ROA | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 203.80.180.0/24 | No ROA | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 203.80.181.0/24 | No ROA | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 203.80.182.0/24 | No ROA | RIR databaseAPNIC, NTTCOM | 671 100% |
| 203.80.183.0/24 | No ROA | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 203.80.177.0/24 | No ROA | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 202.133.8.0/21 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 203.80.184.0/22 | Valid | RIR databaseAPNIC | 671 100% |
AS-SET
AS24399 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 31 are in fix.csv.
- ROA: maxLength1
- ROA: none8
- Route object: none1
- Route object: not announced21
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 202.133.10.0/24 | ROA 202.133.8.0/21 AS24399 has maxLength 21; the route is a /24. Raise the maxLength, or add a ROA for 202.133.10.0/24. |
| Route object: none | 202.133.10.0/24 | No route object for it. A route object for 202.133.8.0/21 with origin AS24399 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24399 in the RIR database for the space. |
| ROA: none | 203.80.176.0/24 | No ROA covers it. Add a ROA for AS24399, maxLength 24. |
| ROA: none | 203.80.178.0/24 | No ROA covers it. Add a ROA for AS24399, maxLength 24. |
| ROA: none | 203.80.179.0/24 | No ROA covers it. Add a ROA for AS24399, maxLength 24. |
| ROA: none | 203.80.180.0/24 | No ROA covers it. Add a ROA for AS24399, maxLength 24. |
| ROA: none | 203.80.181.0/24 | No ROA covers it. Add a ROA for AS24399, maxLength 24. |
| ROA: none | 203.80.182.0/24 | No ROA covers it. Add a ROA for AS24399, maxLength 24. |
| ROA: none | 203.80.183.0/24 | No ROA covers it. Add a ROA for AS24399, maxLength 24. |
| ROA: none | 203.80.177.0/24 | No ROA covers it. Add a ROA for AS24399, maxLength 24. |
Route objects not announced
Route objects with origin AS24399 whose prefix no peer sees AS24399 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 113.208.80.0/21 | RADB | No ROA |
| 113.208.80.0/22 | RADB | No ROA |
| 113.208.80.0/23 | RADB | No ROA |
| 113.208.82.0/23 | RADB | No ROA |
| 113.208.84.0/22 | RADB | No ROA |
| 113.208.84.0/23 | RADB | No ROA |
| 113.208.86.0/23 | RADB | No ROA |
| 116.212.184.0/21 | RADB | No ROA |
| 117.18.224.0/21 | NTTCOM, RADB | No ROA |
| 122.152.48.0/21 | NTTCOM, RADB | No ROA |
| 122.248.0.0/20 | NTTCOM, RADB | No ROA |
| 122.248.32.0/20 | NTTCOM, RADB | No ROA |
| 122.255.64.0/21 | NTTCOM, RADB | No ROA |
| 182.16.143.0/24 | RADB | No ROA |
| 202.6.176.0/20 | NTTCOM, RADB | No ROA |
| 202.84.64.0/21 | NTTCOM, RADB | No ROA |
| 203.80.176.0/21 | NTTCOM | No ROA |
| 203.80.184.0/21 | NTTCOM | No ROA |
| 203.202.224.0/21 | NTTCOM, RADB | No ROA |
| 220.247.160.0/21 | NTTCOM, RADB | No ROA |
| 221.132.120.0/21 | 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.