Network · data from 2026-11-12
AS29016 PEARSON-EMEA Pearson Shared Services Ltd
Registry name: PEARSON-EMEA Pearson Shared Services Ltd, GB · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS29016, 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.
| 195.69.214.0/24 | No ROA | RIR databaseRADB, RIPE | 673 100% |
| 195.69.215.0/24 | No ROA | RIR databaseRADB, RIPE | 673 100% |
| 159.182.79.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 159.182.127.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 168.146.80.0/23 | Valid | RIR databaseARIN, RADB, RIPE-NONAUTH | 673 100% |
| 168.146.82.0/23 | Valid | RIR databaseARIN, RADB, RIPE-NONAUTH | 673 100% |
| 159.182.72.0/21 | Valid | RIR databaseARIN, RADB, RIPE-NONAUTH | 672 100% |
| 159.182.120.0/21 | Valid | RIR databaseARIN, RADB, RIPE-NONAUTH | 672 100% |
| 168.146.110.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 159.182.14.0/24 | Valid | RIR databaseARIN, RADB | 561 83% |
| 168.146.112.0/24 | Valid | RIR databaseARIN, RADB | 27 4%low visibility |
AS-SET
AS29016 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 30 are in fix.csv.
- ROA: none2
- Route object: RIR2
- Route object: not announced26
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 195.69.214.0/24 | No ROA covers it. Add a ROA for AS29016, maxLength 24. |
| ROA: none | 195.69.215.0/24 | No ROA covers it. Add a ROA for AS29016, maxLength 24. |
| Route object: RIR | 159.182.79.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 159.182.127.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS29016 whose prefix no peer sees AS29016 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 159.182.13.0/24 | RADB | No ROA |
| 159.182.41.0/24 | RIPE-NONAUTH | No ROA |
| 159.182.42.0/24 | RIPE-NONAUTH | No ROA |
| 159.182.72.0/24 | RADB | Valid |
| 159.182.73.0/24 | RADB | Valid |
| 159.182.74.0/24 | RADB | Valid |
| 159.182.75.0/24 | RADB | Valid |
| 159.182.76.0/24 | RADB | Valid |
| 159.182.77.0/24 | RADB | Valid |
| 159.182.78.0/24 | RADB | Valid |
| 159.182.94.0/24 | RIPE-NONAUTH | No ROA |
| 159.182.120.0/24 | RADB | Valid |
| 159.182.121.0/24 | RADB | Valid |
| 159.182.122.0/24 | RADB | Valid |
| 159.182.123.0/24 | RADB | Valid |
| 159.182.124.0/24 | RADB | Valid |
| 159.182.125.0/24 | RADB | Valid |
| 159.182.126.0/24 | RADB | Valid |
| 159.182.214.0/24 | RIPE-NONAUTH | No ROA |
| 168.146.80.0/22 | RADB | No ROA |
| 168.146.80.0/24 | RADB | Valid |
| 168.146.81.0/24 | RADB | Valid |
| 168.146.82.0/24 | RADB | Valid |
| 168.146.83.0/24 | RADB | Valid |
| 195.47.223.0/24 | RIPE | No ROA |
| 195.69.212.0/22 | RIPE | 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.