bgpreport

Network · data from 2026-11-12

AS14777 YAHOO - Yahoo Holdings Inc.

Registry name: YAHOO - Yahoo Holdings Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS14777, 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.
69.147.93.0/24 No ROA Other IRR onlyRADB 670 100% 66
69.147.94.0/24 No ROA Other IRR onlyRADB 670 100% 66
69.147.95.0/24 No ROA Other IRR onlyRADB 670 100% 66
209.73.184.0/24 No ROA Other IRR onlyRADB 670 100% 67
69.147.92.0/24 No ROA Other IRR onlyRADB 667 99% 66
2001:4998:14::/48 No ROA Other IRR onlyRADB 632 99% 68

AS-SET

AS14777 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 23 are in fix.csv.

  • ROA: none6
  • Route object: RIR6
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: none69.147.93.0/24No ROA covers it. Add a ROA for AS14777, maxLength 24.670 of 673
Route object: RIR69.147.93.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none69.147.94.0/24No ROA covers it. Add a ROA for AS14777, maxLength 24.670 of 673
Route object: RIR69.147.94.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none69.147.95.0/24No ROA covers it. Add a ROA for AS14777, maxLength 24.670 of 673
Route object: RIR69.147.95.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none209.73.184.0/24No ROA covers it. Add a ROA for AS14777, maxLength 24.670 of 673
Route object: RIR209.73.184.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none69.147.92.0/24No ROA covers it. Add a ROA for AS14777, maxLength 24.667 of 673
Route object: RIR69.147.92.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none2001:4998:14::/48No ROA covers it. Add a ROA for AS14777, maxLength 48.632 of 636
Route object: RIR2001:4998:14::/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 AS14777 whose prefix no peer sees AS14777 announce. Many are kept on purpose (backup routes, space announced only in some places).

66.163.164.0/22RADBNo ROA
68.142.248.0/22RADBNo ROA
68.180.160.0/19RADBNo ROA
69.147.92.0/22RADBNo ROA
69.147.92.0/23RADBNo ROA
69.147.94.0/23RADBNo ROA
72.30.112.0/20RADBNo ROA
72.30.124.0/23RADBNo ROA
74.6.128.0/20RADBNo ROA
74.6.154.0/23RADBNo ROA
74.6.158.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.