bgpreport

Network · data from 2026-11-12

AS5779 YAHOO-DNB - Yahoo Holdings Inc.

Registry name: YAHOO-DNB - 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
3Route objects not announced registered with origin AS5779, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS5779, 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.69.0/24 No ROA Other IRR onlyRADB 670 100% 66
69.147.70.0/24 No ROA Other IRR onlyRADB 670 100% 66
69.147.71.0/24 No ROA Other IRR onlyRADB 668 99% 66
2001:4998:68::/48 No ROA Other IRR onlyRADB 631 99% 68

AS-SET

AS5779 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 11 are in fix.csv.

  • ROA: none4
  • Route object: RIR4
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none69.147.69.0/24No ROA covers it. Add a ROA for AS5779, maxLength 24.670 of 673
Route object: RIR69.147.69.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none69.147.70.0/24No ROA covers it. Add a ROA for AS5779, maxLength 24.670 of 673
Route object: RIR69.147.70.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none69.147.71.0/24No ROA covers it. Add a ROA for AS5779, maxLength 24.668 of 673
Route object: RIR69.147.71.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none2001:4998:68::/48No ROA covers it. Add a ROA for AS5779, maxLength 48.631 of 636
Route object: RIR2001:4998:68::/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 AS5779 whose prefix no peer sees AS5779 announce. Many are kept on purpose (backup routes, space announced only in some places).

63.250.192.0/19RADBNo ROA
67.195.252.0/22RADBNo ROA
69.147.70.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.