bgpreport

Network · data from 2026-11-12

AS38032 YAHOO-HK2-AP - internet content provider

Registry name: YAHOO-HK2-AP - internet content provider, HK · not in PeeringDB

3IPv4 routes 0.0% RPKI valid · 33.3% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
4No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
9Route objects not announced registered with origin AS38032, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS38032, 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.115.0/24 No ROA Nonecovered by 180.222.114.0/23 671 100% 67
180.222.114.0/24 No ROA Nonecovered by 180.222.114.0/23 668 99% 67
180.222.112.0/24 No ROA Other IRR onlyRADB 671 100% 67
2406:2000:98::/48 No ROA Other IRR onlyRADB 633 100% 69

AS-SET

AS38032 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 17 are in fix.csv.

  • ROA: none4
  • Route object: none2
  • Route object: RIR2
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none180.222.115.0/24No ROA covers it. Add a ROA for AS38032, maxLength 24.671 of 673
Route object: none180.222.115.0/24No route object for it. A route object for 180.222.114.0/23 with origin AS38032 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38032 in the RIR database for the space.671 of 673
ROA: none180.222.114.0/24No ROA covers it. Add a ROA for AS38032, maxLength 24.668 of 673
Route object: none180.222.114.0/24No route object for it. A route object for 180.222.114.0/23 with origin AS38032 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38032 in the RIR database for the space.668 of 673
ROA: none180.222.112.0/24No ROA covers it. Add a ROA for AS38032, maxLength 24.671 of 673
Route object: RIR180.222.112.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2406:2000:98::/48No ROA covers it. Add a ROA for AS38032, maxLength 48.633 of 636
Route object: RIR2406:2000:98::/48Route object only in RADB. Add it in the RIR database for the space.633 of 636

Route objects not announced

Route objects with origin AS38032 whose prefix no peer sees AS38032 announce. Many are kept on purpose (backup routes, space announced only in some places).

27.123.192.0/20RADBNo ROA
115.178.0.0/20RADBNo ROA
115.178.8.0/23RADBNo ROA
124.108.92.0/22RADBNo ROA
124.108.96.0/20RADBNo ROA
124.108.104.0/23RADBNo ROA
124.108.106.0/23RADBNo ROA
124.108.108.0/23RADBNo ROA
180.222.114.0/23RADBNo 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.