Network · data from 2026-11-12
AS151196 JUNYUNLIMITED-AS-AP - JunYun Limited
Registry name: JUNYUNLIMITED-AS-AP - JunYun Limited, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS151196, 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.
| 45.196.104.0/24 | Invalid: origin | RIR databaseAFRINIC | 10 1%low visibility |
| 154.90.66.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 103.162.38.0/23 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 154.90.69.0/24 | Valid | RIR databaseAFRINIC, RADB | 671 100% |
| 154.204.47.0/24 | Valid | RIR databaseAFRINIC, RADB | 671 100% |
| 154.204.50.0/24 | Valid | RIR databaseAFRINIC, RADB | 671 100% |
| 154.204.53.0/24 | Valid | RIR databaseAFRINIC, RADB | 671 100% |
| 154.204.54.0/24 | Valid | RIR databaseAFRINIC, RADB | 671 100% |
| 154.204.62.0/24 | Valid | RIR databaseAFRINIC, RADB | 671 100% |
| 154.212.160.0/24 | Valid | RIR databaseAFRINIC, RADB | 671 100% |
| 154.212.162.0/23 | Valid | RIR databaseAFRINIC, RADB | 671 100% |
AS-SET
AS151196 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 3 are in fix.csv.
- ROA: origin1
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 45.196.104.0/24 | ROAs covering it name AS17561, AS132585, not AS151196. If AS151196 should announce it, add a ROA for AS151196. |
| Route object: RIR | 154.90.66.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS151196 whose prefix no peer sees AS151196 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 156.226.128.0/24 | AFRINIC, RADB | Valid |
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.