bgpreport

Network · data from 2026-11-12

AS11892 PEARSON-NA - NCS Pearson Inc.

Registry name: PEARSON-NA - NCS Pearson Inc., US · not in PeeringDB

5IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
63Route objects not announced registered with origin AS11892, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS11892, 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.12.0/24 Valid RIR databaseARIN, RADB 672 100% 67
168.146.109.0/24 Valid RIR databaseARIN, RADB 672 100% 67
168.146.68.0/22 Valid RIR databaseARIN, RADB 671 100% 67
159.182.14.0/24 Valid RIR databaseARIN, RADB 112 17% 45
168.146.112.0/24 Valid RIR databaseARIN, RADB 40 6%low visibility 18

AS-SET

AS11892 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 63 are in fix.csv.

  • Route object: not announced63

Route objects not announced

Route objects with origin AS11892 whose prefix no peer sees AS11892 announce. Many are kept on purpose (backup routes, space announced only in some places).

159.182.0.0/21RADBNo ROA
159.182.0.0/22RADBNo ROA
159.182.0.0/24RADBNo ROA
159.182.1.0/24RADBNo ROA
159.182.2.0/24RADBNo ROA
159.182.3.0/24RADBNo ROA
159.182.4.0/22RADBNo ROA
159.182.4.0/24RADBNo ROA
159.182.5.0/24RADBNo ROA
159.182.6.0/24RADBNo ROA
159.182.7.0/24RADBNo ROA
159.182.8.0/23RADBNo ROA
159.182.8.0/24RADBNo ROA
159.182.9.0/24RADBNo ROA
159.182.11.0/24RADBNo ROA
159.182.20.0/23RADBNo ROA
159.182.20.0/24RADBNo ROA
159.182.21.0/24RADBNo ROA
159.182.26.0/24RADBNo ROA
159.182.30.0/23RADBNo ROA
159.182.30.0/24RADBNo ROA
159.182.31.0/24RADBNo ROA
159.182.32.0/21RADBNo ROA
159.182.32.0/24RADBNo ROA
159.182.33.0/24RADBNo ROA
159.182.34.0/23RADBNo ROA
159.182.34.0/24RADBNo ROA
159.182.35.0/24RADBNo ROA
159.182.36.0/22RADBNo ROA
159.182.36.0/24RADBNo ROA
159.182.37.0/24RADBNo ROA
159.182.38.0/24RADBNo ROA
159.182.39.0/24RADBNo ROA
159.182.95.0/24RADBNo ROA
159.182.111.0/24RADBNo ROA
159.182.112.0/23RADBNo ROA
159.182.112.0/24RADBNo ROA
159.182.113.0/24RADBNo ROA
159.182.115.0/24RADBNo ROA
159.182.230.0/24RADBNo ROA
159.182.231.0/24RADBNo ROA
159.182.232.0/23RADBNo ROA
159.182.232.0/24RADBNo ROA
159.182.233.0/24RADBNo ROA
159.182.241.0/24RADBNo ROA
168.146.64.0/23RADBNo ROA
168.146.64.0/24RADBNo ROA
168.146.65.0/24RADBNo ROA
168.146.68.0/23RADBValid
168.146.68.0/24RADBValid
168.146.69.0/24RADBValid
168.146.70.0/23RADBValid
168.146.70.0/24RADBValid
168.146.71.0/24RADBValid
168.146.72.0/21RADBNo ROA
168.146.72.0/24RADBNo ROA
168.146.73.0/24RADBNo ROA
168.146.74.0/24RADBNo ROA
168.146.75.0/24RADBNo ROA
168.146.76.0/24RADBNo ROA
168.146.77.0/24RADBNo ROA
168.146.78.0/24RADBNo ROA
168.146.79.0/24RADBNo 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.