Network · data from 2026-11-12
AS23880 Yahoo-AEA - Internet content provider
Registry name: Yahoo-AEA - Internet content provider, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS23880, 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.
| 212.82.117.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 2a00:1288:f043::/48 | No ROA | Other IRR onlyRADB | 636 100% |
AS-SET
AS23880 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 14 are in fix.csv.
- ROA: none2
- Route object: RIR2
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 212.82.117.0/24 | No ROA covers it. Add a ROA for AS23880, maxLength 24. |
| Route object: RIR | 212.82.117.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2a00:1288:f043::/48 | No ROA covers it. Add a ROA for AS23880, maxLength 48. |
| Route object: RIR | 2a00:1288:f043::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS23880 whose prefix no peer sees AS23880 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 183.177.93.0/24 | APNIC, RADB | No ROA |
| 202.43.204.0/22 | RADB | No ROA |
| 202.43.208.0/21 | APNIC, RADB | No ROA |
| 211.115.90.0/23 | RADB | No ROA |
| 211.115.96.0/21 | RADB | No ROA |
| 211.115.106.0/23 | RADB | No ROA |
| 222.231.16.0/22 | RADB | No ROA |
| 222.231.22.0/23 | RADB | No ROA |
| 222.231.48.0/23 | RADB | No ROA |
| 2a00:1288:f843::/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.