Network · data from 2026-11-12
AS10229 YAHOO-TW1 - Yahoo Inc.
Registry name: YAHOO-TW1 - Yahoo Inc., TW · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS10229, 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.
| 203.83.216.0/23 | No ROA | RIR databaseAPNIC | 105 16% |
AS-SET
AS10229 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 65 are in fix.csv.
- ROA: none1
- Route object: not announced64
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 203.83.216.0/23 | No ROA covers it. Add a ROA for AS10229, maxLength 23. |
Route objects not announced
Route objects with origin AS10229 whose prefix no peer sees AS10229 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 27.123.200.0/21 | APNIC, RADB | No ROA |
| 117.104.191.0/24 | RADB | No ROA |
| 119.160.240.0/20 | APNIC | No ROA |
| 119.160.240.0/23 | APNIC | No ROA |
| 119.160.240.0/24 | APNIC | No ROA |
| 119.160.241.0/24 | APNIC | No ROA |
| 119.160.242.0/23 | APNIC | No ROA |
| 119.160.242.0/24 | APNIC | No ROA |
| 119.160.243.0/24 | APNIC | No ROA |
| 119.160.244.0/23 | APNIC | No ROA |
| 119.160.244.0/24 | APNIC | No ROA |
| 119.160.245.0/24 | APNIC | No ROA |
| 119.160.246.0/23 | APNIC | No ROA |
| 119.160.246.0/24 | APNIC | No ROA |
| 119.160.247.0/24 | APNIC | No ROA |
| 119.160.248.0/23 | APNIC | No ROA |
| 119.160.248.0/24 | APNIC | No ROA |
| 119.160.249.0/24 | APNIC | No ROA |
| 119.160.250.0/23 | APNIC | No ROA |
| 119.160.250.0/24 | APNIC | No ROA |
| 119.160.251.0/24 | APNIC | No ROA |
| 119.160.252.0/23 | APNIC | No ROA |
| 119.160.252.0/24 | APNIC | No ROA |
| 119.160.253.0/24 | APNIC | No ROA |
| 119.160.254.0/23 | APNIC | No ROA |
| 119.160.254.0/24 | APNIC | No ROA |
| 119.160.255.0/24 | APNIC | No ROA |
| 124.108.72.0/23 | RADB | No ROA |
| 124.108.72.0/24 | RADB | No ROA |
| 124.108.88.0/21 | RADB | No ROA |
| 124.108.92.0/22 | APNIC, RADB | No ROA |
| 124.108.104.0/21 | RADB | No ROA |
| 124.108.105.0/24 | RADB | No ROA |
| 124.108.112.0/21 | APNIC, RADB | No ROA |
| 124.108.112.0/24 | RADB | No ROA |
| 124.108.115.0/24 | RADB | No ROA |
| 124.108.120.0/21 | APNIC, RADB | No ROA |
| 124.108.124.0/24 | RADB | No ROA |
| 180.222.97.0/24 | RADB | No ROA |
| 183.177.64.0/22 | APNIC, RADB | No ROA |
| 183.177.72.0/24 | RADB | No ROA |
| 183.177.73.0/24 | RADB | No ROA |
| 183.177.92.0/22 | RADB | No ROA |
| 183.177.94.0/23 | APNIC, RADB | No ROA |
| 202.43.192.0/21 | APNIC | No ROA |
| 202.43.200.0/23 | APNIC, RADB | No ROA |
| 202.43.212.0/22 | RADB | No ROA |
| 202.43.216.0/23 | APNIC | Valid |
| 202.43.218.0/24 | APNIC | No ROA |
| 202.89.122.0/23 | APNIC, RADB | No ROA |
| 202.174.4.0/24 | APNIC | No ROA |
| 203.14.212.0/24 | RADB | No ROA |
| 203.84.192.0/21 | APNIC, RADB | No ROA |
| 203.84.200.0/21 | APNIC, RADB | No ROA |
| 203.84.202.0/24 | RADB | No ROA |
| 203.99.254.0/24 | RADB | No ROA |
| 203.188.206.0/23 | APNIC | No ROA |
| 2001:4998:1a0::/46 | RADB | No ROA |
| 2001:4998:1a0::/48 | RADB | No ROA |
| 2406:2000:fc::/46 | RADB | No ROA |
| 2406:2000:fc::/48 | RADB | No ROA |
| 2406:2000:1a0::/46 | RADB | No ROA |
| 2406:2000:ef67::/48 | RADB | No ROA |
| 2406:2000:efbc::/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.