Network · data from 2026-11-12
AS7233 YAHOO-US - Yahoo
Registry name: YAHOO-US - Yahoo, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS7233, 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.
| 98.136.0.0/23 | No ROA | Nonecovered by 98.136.0.0/20 | 670 100% |
| 209.131.48.0/23 | No ROA | None | 668 99% |
| 2001:4998:ef61::/48 | No ROA | None | 632 99% |
| 2001:4998:ef60::/48 | No ROA | None | 631 99% |
AS-SET
AS7233 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 21 are in fix.csv.
- ROA: none4
- Route object: none4
- Route object: not announced13
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 98.136.0.0/23 | No ROA covers it. Add a ROA for AS7233, maxLength 23. |
| Route object: none | 98.136.0.0/23 | No route object for it. A route object for 98.136.0.0/20 with origin AS7233 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7233 in the RIR database for the space. |
| ROA: none | 209.131.48.0/23 | No ROA covers it. Add a ROA for AS7233, maxLength 23. |
| Route object: none | 209.131.48.0/23 | No route object for it. Add a route object with origin AS7233 in the RIR database for the space. |
| ROA: none | 2001:4998:ef61::/48 | No ROA covers it. Add a ROA for AS7233, maxLength 48. |
| Route object: none | 2001:4998:ef61::/48 | No route object for it. Add a route object with origin AS7233 in the RIR database for the space. |
| ROA: none | 2001:4998:ef60::/48 | No ROA covers it. Add a ROA for AS7233, maxLength 48. |
| Route object: none | 2001:4998:ef60::/48 | No route object for it. Add a route object with origin AS7233 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS7233 whose prefix no peer sees AS7233 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 66.228.160.0/20 | RADB | No ROA |
| 98.136.0.0/20 | RADB | No ROA |
| 98.137.138.0/23 | RADB | No ROA |
| 206.173.250.64/26 | RADB | No ROA |
| 207.126.224.0/20 | RADB | No ROA |
| 208.67.66.0/23 | RADB | No ROA |
| 209.131.54.0/23 | RADB | No ROA |
| 209.131.62.0/24 | RADB | No ROA |
| 216.145.48.0/20 | RADB | No ROA |
| 216.145.49.0/24 | RADB | No ROA |
| 2001:4998:ef5e::/48 | RADB | No ROA |
| 2001:4998:effd::/48 | RADB | No ROA |
| 2001:49a0:fbff::/48 | RADB | No 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.