Network · data from 2026-11-12
AS9823 PEARSON-APAC - Pearson Group
Registry name: PEARSON-APAC - Pearson Group, AU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS9823, 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.
| 159.182.67.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 159.182.52.0/23 | Valid | RIR databaseARIN, RADB | 672 100% |
| 159.182.64.0/22 | Valid | RIR databaseARIN, RADB | 671 100% |
| 168.146.111.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 168.146.112.0/24 | Valid | RIR databaseARIN, RADB | 605 90% |
AS-SET
AS9823 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 19 are in fix.csv.
- Route object: RIR1
- Route object: not announced18
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 159.182.67.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS9823 whose prefix no peer sees AS9823 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 159.182.49.0/24 | RADB | No ROA |
| 159.182.52.0/24 | RADB | Valid |
| 159.182.53.0/24 | RADB | Valid |
| 159.182.60.0/22 | RADB | No ROA |
| 159.182.60.0/24 | RADB | No ROA |
| 159.182.61.0/24 | RADB | No ROA |
| 159.182.62.0/24 | RADB | No ROA |
| 159.182.63.0/24 | RADB | No ROA |
| 159.182.64.0/24 | RADB | Valid |
| 168.146.98.0/23 | RADB | No ROA |
| 168.146.98.0/24 | RADB | No ROA |
| 168.146.99.0/24 | RADB | No ROA |
| 202.91.224.0/19 | NTTCOM | No ROA |
| 203.19.96.0/22 | APNIC, RADB | No ROA |
| 203.19.96.0/24 | RADB | No ROA |
| 203.19.97.0/24 | RADB | No ROA |
| 203.19.98.0/24 | RADB | No ROA |
| 203.19.99.0/24 | 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.