bgpreport

Network · data from 2026-11-12

AS14778 YAHOO - Yahoo Holdings Inc.

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

6IPv4 routes 0.0% RPKI valid · 50.0% with a route object
9IPv6 routes 0.0% RPKI valid · 33.3% with a route object
0RPKI invalid 0 origin · 0 maxLength
15No ROA 9 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
55Route objects not announced registered with origin AS14778, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS14778, 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.
117.104.191.0/24 No ROA Other origin only 671 100% 67
202.174.4.0/24 No ROA Other origin only 671 100% 67
203.83.216.0/24 No ROA None 671 100% 67
2406:2000:ef67::/48 No ROA Other origin only 633 100% 69
2406:2000:efbc::/48 No ROA Other origin only 633 100% 69
2406:2000:efbe::/48 No ROA None 633 100% 69
2406:6e00:ef98::/48 No ROA None 633 100% 69
2a00:1288:ef83::/48 No ROA None 633 100% 68
2001:4998:ef84::/48 No ROA None 632 99% 68
77.238.175.0/24 No ROA Other IRR onlyRADB 671 100% 67
184.165.10.0/24 No ROA Other IRR onlyRADB 670 100% 66
2a00:1288:ef9b::/48 No ROA Other IRR onlyRADB 636 100% 67
2a00:1288:efc1::/48 No ROA Other IRR onlyRADB 633 100% 68
2001:4998:ef6f::/48 No ROA Other IRR onlyRADB 632 99% 68
117.104.190.0/24 No ROA RIR databaseAPNIC, RADB 671 100% 67

AS-SET

AS14778 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 84 are in fix.csv.

  • ROA: none15
  • Route object: none9
  • Route object: RIR5
  • Route object: not announced55
ChangePrefix or setDetailFull-table peers
ROA: none117.104.191.0/24No ROA covers it. Add a ROA for AS14778, maxLength 24.671 of 673
Route object: none117.104.191.0/24Route objects for it name AS10229. Add a route object with origin AS14778 in the RIR database for the space.671 of 673
ROA: none202.174.4.0/24No ROA covers it. Add a ROA for AS14778, maxLength 24.671 of 673
Route object: none202.174.4.0/24Route objects for it name AS10229, AS24031. Add a route object with origin AS14778 in the RIR database for the space.671 of 673
ROA: none203.83.216.0/24No ROA covers it. Add a ROA for AS14778, maxLength 24.671 of 673
Route object: none203.83.216.0/24No route object for it. Add a route object with origin AS14778 in the RIR database for the space.671 of 673
ROA: none2406:2000:ef67::/48No ROA covers it. Add a ROA for AS14778, maxLength 48.633 of 636
Route object: none2406:2000:ef67::/48Route objects for it name AS10229. Add a route object with origin AS14778 in the RIR database for the space.633 of 636
ROA: none2406:2000:efbc::/48No ROA covers it. Add a ROA for AS14778, maxLength 48.633 of 636
Route object: none2406:2000:efbc::/48Route objects for it name AS10229. Add a route object with origin AS14778 in the RIR database for the space.633 of 636
ROA: none2406:2000:efbe::/48No ROA covers it. Add a ROA for AS14778, maxLength 48.633 of 636
Route object: none2406:2000:efbe::/48No route object for it. Add a route object with origin AS14778 in the RIR database for the space.633 of 636
ROA: none2406:6e00:ef98::/48No ROA covers it. Add a ROA for AS14778, maxLength 48.633 of 636
Route object: none2406:6e00:ef98::/48No route object for it. Add a route object with origin AS14778 in the RIR database for the space.633 of 636
ROA: none2a00:1288:ef83::/48No ROA covers it. Add a ROA for AS14778, maxLength 48.633 of 636
Route object: none2a00:1288:ef83::/48No route object for it. Add a route object with origin AS14778 in the RIR database for the space.633 of 636
ROA: none2001:4998:ef84::/48No ROA covers it. Add a ROA for AS14778, maxLength 48.632 of 636
Route object: none2001:4998:ef84::/48No route object for it. Add a route object with origin AS14778 in the RIR database for the space.632 of 636
ROA: none77.238.175.0/24No ROA covers it. Add a ROA for AS14778, maxLength 24.671 of 673
Route object: RIR77.238.175.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none184.165.10.0/24No ROA covers it. Add a ROA for AS14778, maxLength 24.670 of 673
Route object: RIR184.165.10.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none2a00:1288:ef9b::/48No ROA covers it. Add a ROA for AS14778, maxLength 48.636 of 636
Route object: RIR2a00:1288:ef9b::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2a00:1288:efc1::/48No ROA covers it. Add a ROA for AS14778, maxLength 48.633 of 636
Route object: RIR2a00:1288:efc1::/48Route object only in RADB. Add it in the RIR database for the space.633 of 636
ROA: none2001:4998:ef6f::/48No ROA covers it. Add a ROA for AS14778, maxLength 48.632 of 636
Route object: RIR2001:4998:ef6f::/48Route object only in RADB. Add it in the RIR database for the space.632 of 636
ROA: none117.104.190.0/24No ROA covers it. Add a ROA for AS14778, maxLength 24.671 of 673

Route objects not announced

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

66.163.184.0/21RADBNo ROA
66.218.64.0/19RADBNo ROA
66.218.90.0/23RADBNo ROA
66.228.184.0/22RADBNo ROA
66.228.188.0/22RADBNo ROA
67.28.115.0/24RADBNo ROA
67.195.160.0/19RADBNo ROA
67.195.224.0/19RADBNo ROA
68.180.152.0/21RADBNo ROA
72.30.96.0/20RADBNo ROA
72.30.212.0/22RADBNo ROA
72.30.216.0/22RADBNo ROA
72.30.232.0/21RADBNo ROA
74.6.0.0/16RADBNo ROA
74.6.64.0/19RADBNo ROA
74.6.148.0/23RADBNo ROA
74.6.150.0/23RADBNo ROA
74.6.152.0/23RADBNo ROA
74.6.156.0/23RADBNo ROA
74.6.232.0/21RADBNo ROA
74.6.232.0/22RADBNo ROA
74.6.236.0/22RADBNo ROA
74.6.240.0/21RADBNo ROA
98.136.64.0/18RADBNo ROA
98.137.64.0/19RADBNo ROA
98.137.192.0/20RADBNo ROA
98.137.216.0/21RADBNo ROA
98.139.0.0/20RADBNo ROA
98.139.48.0/20RADBNo ROA
98.139.96.0/22RADBNo ROA
98.139.104.0/22RADBNo ROA
184.165.9.0/24RADBNo ROA
193.93.196.0/24RADBNo ROA
193.93.199.0/24RADBNo ROA
209.73.160.0/20RADBNo ROA
209.73.176.0/21RADBNo ROA
209.73.188.0/23RADBNo ROA
216.109.112.0/20RADBNo ROA
2001:4998:50::/46RADBNo ROA
2001:4998:54::/46RADBNo ROA
2001:4998:ef5f::/48RADBNo ROA
2001:4998:ef62::/48RADBNo ROA
2001:4998:ef63::/48RADBNo ROA
2001:4998:ef64::/48RADBNo ROA
2001:4998:ef65::/48RADBNo ROA
2001:4998:ef6d::/48RADBNo ROA
2001:4998:ef6e::/48RADBNo ROA
2001:4998:ef70::/48RADBNo ROA
2001:4998:ef72::/48RADBNo ROA
2001:4998:ef78::/48RADBNo ROA
2001:4998:ef7b::/48RADBNo ROA
2001:4998:ef9b::/48RADBNo ROA
2a00:1288:ef67::/48RADBNo ROA
2a00:1288:ef6c::/48RADBNo ROA
2a00:1288:efc4::/48RADBNo 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.