bgpreport

Network · data from 2026-11-12

AS36752 YAHOO-SP1 - Yahoo Holdings Inc.

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

3IPv4 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
4No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
39Route objects not announced registered with origin AS36752, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS36752, 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.
209.73.177.0/24 No ROA Other IRR onlyRADB 670 100% 67
209.73.178.0/24 No ROA Other IRR onlyRADB 670 100% 67
209.73.179.0/24 No ROA Other IRR onlyRADB 665 99% 67
2001:4998:15c::/48 No ROA Other IRR onlyRADB 631 99% 68

AS-SET

AS36752 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 47 are in fix.csv.

  • ROA: none4
  • Route object: RIR4
  • Route object: not announced39
ChangePrefix or setDetailFull-table peers
ROA: none209.73.177.0/24No ROA covers it. Add a ROA for AS36752, maxLength 24.670 of 673
Route object: RIR209.73.177.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none209.73.178.0/24No ROA covers it. Add a ROA for AS36752, maxLength 24.670 of 673
Route object: RIR209.73.178.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none209.73.179.0/24No ROA covers it. Add a ROA for AS36752, maxLength 24.665 of 673
Route object: RIR209.73.179.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
ROA: none2001:4998:15c::/48No ROA covers it. Add a ROA for AS36752, maxLength 48.631 of 636
Route object: RIR2001:4998:15c::/48Route object only in RADB. Add it in the RIR database for the space.631 of 636

Route objects not announced

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

66.94.224.0/22RADBNo ROA
66.94.240.0/20RADBNo ROA
66.163.168.0/21RADBNo ROA
66.196.76.0/22RADBNo ROA
66.196.94.0/23RADBNo ROA
66.196.96.0/21RADBNo ROA
67.195.128.0/19RADBNo ROA
67.195.128.0/20RADBNo ROA
67.195.152.0/21RADBNo ROA
68.180.140.0/22RADBNo ROA
68.180.144.0/21RADBNo ROA
68.180.192.0/20RADBNo ROA
68.180.208.0/20RADBNo ROA
69.147.80.0/20RADBNo ROA
72.30.22.0/23RADBNo ROA
74.6.73.0/24RADBNo ROA
98.136.16.0/20RADBNo ROA
98.136.32.0/21RADBNo ROA
98.136.40.0/21RADBNo ROA
98.136.48.0/20RADBNo ROA
98.137.32.0/19RADBNo ROA
98.137.58.0/23RADBNo ROA
98.137.76.0/22RADBNo ROA
98.137.77.0/24RADBNo ROA
98.137.128.0/19RADBNo ROA
98.137.128.0/21RADBNo ROA
98.137.136.0/23RADBNo ROA
98.137.140.0/22RADBNo ROA
98.137.144.0/21RADBNo ROA
98.137.152.0/21RADBNo ROA
98.139.64.0/19RADBNo ROA
98.139.108.0/22RADBNo ROA
208.67.64.0/21RADBNo ROA
208.67.64.0/23RADBNo ROA
208.67.68.0/22RADBNo ROA
209.73.178.0/23RADBNo ROA
209.131.32.0/20RADBNo ROA
2001:4998:28::/46RADBNo ROA
2001:4998:2c::/46RADBNo 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.