Network · data from 2026-11-12
AS18293 YAHOO-HK2-AP - Internet content provider
Registry name: YAHOO-HK2-AP - Internet content provider, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS18293, 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.
| 180.222.116.0/24 | No ROA | Nonecovered by 180.222.116.0/23 | 671 100% |
| 180.222.117.0/24 | No ROA | Nonecovered by 180.222.116.0/23 | 671 100% |
| 180.222.113.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 2406:2000:a8::/48 | No ROA | Other IRR onlyRADB | 633 100% |
AS-SET
AS18293 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 20 are in fix.csv.
- ROA: none4
- Route object: none2
- Route object: RIR2
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 180.222.116.0/24 | No ROA covers it. Add a ROA for AS18293, maxLength 24. |
| Route object: none | 180.222.116.0/24 | No route object for it. A route object for 180.222.116.0/23 with origin AS18293 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18293 in the RIR database for the space. |
| ROA: none | 180.222.117.0/24 | No ROA covers it. Add a ROA for AS18293, maxLength 24. |
| Route object: none | 180.222.117.0/24 | No route object for it. A route object for 180.222.116.0/23 with origin AS18293 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18293 in the RIR database for the space. |
| ROA: none | 180.222.113.0/24 | No ROA covers it. Add a ROA for AS18293, maxLength 24. |
| Route object: RIR | 180.222.113.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2406:2000:a8::/48 | No ROA covers it. Add a ROA for AS18293, maxLength 48. |
| Route object: RIR | 2406:2000:a8::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS18293 whose prefix no peer sees AS18293 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 124.108.80.0/22 | RADB, REACH | No ROA |
| 124.108.92.0/22 | REACH | No ROA |
| 124.108.104.0/23 | REACH | No ROA |
| 180.222.116.0/23 | RADB | No ROA |
| 180.233.118.0/24 | RADB | No ROA |
| 202.1.232.0/23 | REACH | No ROA |
| 202.8.76.0/24 | REACH | Invalid: origin |
| 202.43.220.0/22 | APNIC, RADB, REACH | No ROA |
| 202.165.104.0/23 | RADB | No ROA |
| 203.14.212.0/24 | APNIC | No ROA |
| 203.84.222.0/23 | APNIC, RADB, REACH | No ROA |
| 203.99.254.0/24 | APNIC, 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.