bgpreport

Network · data from 2026-11-12

AS10230 YAHOO-SG - internet content provider

Registry name: YAHOO-SG - internet content provider, SG · 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
14Route objects not announced registered with origin AS10230, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS10230, 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.118.0/24 No ROA Other origin onlycovered by 180.222.118.0/23 671 100% 67
180.222.119.0/24 No ROA Other origin onlycovered by 180.222.118.0/23 670 100% 67
180.222.96.0/24 No ROA Other IRR onlyRADB 671 100% 67
2406:2000:a4::/48 No ROA Other IRR onlyRADB 632 99% 69

AS-SET

AS10230 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 22 are in fix.csv.

  • ROA: none4
  • Route object: none2
  • Route object: RIR2
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
ROA: none180.222.118.0/24No ROA covers it. Add a ROA for AS10230, maxLength 24.671 of 673
Route object: none180.222.118.0/24Route objects for it name AS38072. A route object for 180.222.118.0/23 with origin AS10230 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10230 in the RIR database for the space.671 of 673
ROA: none180.222.119.0/24No ROA covers it. Add a ROA for AS10230, maxLength 24.670 of 673
Route object: none180.222.119.0/24Route objects for it name AS38072. A route object for 180.222.118.0/23 with origin AS10230 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10230 in the RIR database for the space.670 of 673
ROA: none180.222.96.0/24No ROA covers it. Add a ROA for AS10230, maxLength 24.671 of 673
Route object: RIR180.222.96.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2406:2000:a4::/48No ROA covers it. Add a ROA for AS10230, maxLength 48.632 of 636
Route object: RIR2406:2000:a4::/48Route object only in RADB. Add it in the RIR database for the space.632 of 636

Route objects not announced

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

106.10.133.0/24RADBNo ROA
115.178.12.0/23APNICNo ROA
115.178.14.0/23APNICNo ROA
124.108.72.0/22APNIC, RADBNo ROA
124.108.78.0/23RADBNo ROA
180.222.118.0/23RADBNo ROA
180.233.112.0/22APNICNo ROA
183.177.72.0/21RADBNo ROA
183.177.72.0/22APNICNo ROA
183.177.84.0/22RADBNo ROA
202.43.208.0/21APNICNo ROA
202.43.208.0/22APNICNo ROA
202.43.212.0/22APNICNo ROA
202.165.96.0/20RADBNo 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.