bgpreport

Network · data from 2026-11-12

AS32472 LEXIS2-AS - RELX inc.

Registry name: LEXIS2-AS - RELX inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS32472, 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.

138.12.0.0/17 No ROA None 673 100% 67
192.73.216.0/24 No ROA None 673 100% 67
198.137.148.0/24 No ROA None 673 100% 67
198.176.64.0/22 No ROA None 673 100% 67
198.185.23.0/24 No ROA None 673 100% 67
198.185.24.0/24 No ROA None 673 100% 67
198.185.25.0/24 No ROA None 673 100% 67
198.187.130.0/24 No ROA None 673 100% 67
207.24.132.0/24 No ROA None 673 100% 67
207.25.180.0/24 No ROA None 673 100% 67

AS-SET

AS32472 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 20 are in fix.csv.

  • ROA: none10
  • Route object: none10
ChangePrefix or setDetailFull-table peers
ROA: none138.12.0.0/17No ROA covers it. Add a ROA for AS32472, maxLength 17.673 of 673
Route object: none138.12.0.0/17No route object for it. Add a route object with origin AS32472 in the RIR database for the space.673 of 673
ROA: none192.73.216.0/24No ROA covers it. Add a ROA for AS32472, maxLength 24.673 of 673
Route object: none192.73.216.0/24No route object for it. Add a route object with origin AS32472 in the RIR database for the space.673 of 673
ROA: none198.137.148.0/24No ROA covers it. Add a ROA for AS32472, maxLength 24.673 of 673
Route object: none198.137.148.0/24No route object for it. Add a route object with origin AS32472 in the RIR database for the space.673 of 673
ROA: none198.176.64.0/22No ROA covers it. Add a ROA for AS32472, maxLength 22.673 of 673
Route object: none198.176.64.0/22No route object for it. Add a route object with origin AS32472 in the RIR database for the space.673 of 673
ROA: none198.185.23.0/24No ROA covers it. Add a ROA for AS32472, maxLength 24.673 of 673
Route object: none198.185.23.0/24No route object for it. Add a route object with origin AS32472 in the RIR database for the space.673 of 673
ROA: none198.185.24.0/24No ROA covers it. Add a ROA for AS32472, maxLength 24.673 of 673
Route object: none198.185.24.0/24No route object for it. Add a route object with origin AS32472 in the RIR database for the space.673 of 673
ROA: none198.185.25.0/24No ROA covers it. Add a ROA for AS32472, maxLength 24.673 of 673
Route object: none198.185.25.0/24No route object for it. Add a route object with origin AS32472 in the RIR database for the space.673 of 673
ROA: none198.187.130.0/24No ROA covers it. Add a ROA for AS32472, maxLength 24.673 of 673
Route object: none198.187.130.0/24No route object for it. Add a route object with origin AS32472 in the RIR database for the space.673 of 673
ROA: none207.24.132.0/24No ROA covers it. Add a ROA for AS32472, maxLength 24.673 of 673
Route object: none207.24.132.0/24No route object for it. Add a route object with origin AS32472 in the RIR database for the space.673 of 673
ROA: none207.25.180.0/24No ROA covers it. Add a ROA for AS32472, maxLength 24.673 of 673
Route object: none207.25.180.0/24No route object for it. Add a route object with origin AS32472 in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS32472 is announced.

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.