bgpreport

Network · data from 2026-11-12

AS13798 LOREAL-USA - L'Oreal USA

Registry name: LOREAL-USA - L'Oreal USA, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS13798, 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.
161.241.27.0/24 No ROA Other IRR onlyRADB 673 100% 67
161.241.28.0/22 No ROA Other IRR onlyRADB 670 100% 67
161.241.24.0/22 No ROA RIR databaseARIN, RADB 673 100% 67
161.241.24.0/23 No ROA RIR databaseARIN, RADB 673 100% 70
161.241.26.0/23 No ROA RIR databaseARIN, RADB 673 100% 70
161.241.28.0/23 No ROA RIR databaseARIN, RADB 673 100% 70
161.241.30.0/23 No ROA RIR databaseARIN, RADB 673 100% 70

AS-SET

AS13798 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 21 are in fix.csv.

  • ROA: none7
  • Route object: RIR2
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none161.241.27.0/24No ROA covers it. Add a ROA for AS13798, maxLength 24.673 of 673
Route object: RIR161.241.27.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none161.241.28.0/22No ROA covers it. Add a ROA for AS13798, maxLength 22.670 of 673
Route object: RIR161.241.28.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none161.241.24.0/22No ROA covers it. Add a ROA for AS13798, maxLength 22.673 of 673
ROA: none161.241.24.0/23No ROA covers it. Add a ROA for AS13798, maxLength 23.673 of 673
ROA: none161.241.26.0/23No ROA covers it. Add a ROA for AS13798, maxLength 23.673 of 673
ROA: none161.241.28.0/23No ROA covers it. Add a ROA for AS13798, maxLength 23.673 of 673
ROA: none161.241.30.0/23No ROA covers it. Add a ROA for AS13798, maxLength 23.673 of 673

Route objects not announced

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

63.250.0.0/19ALTDBNo ROA
63.250.0.0/20ALTDBNo ROA
63.250.16.0/20ALTDBNo ROA
161.241.24.0/24RADBNo ROA
161.241.25.0/24RADBNo ROA
161.241.26.0/24RADBNo ROA
161.241.28.0/24RADBNo ROA
161.241.29.0/24RADBNo ROA
161.241.30.0/24RADBNo ROA
161.241.31.0/24RADBNo ROA
198.16.0.0/23ARINNo ROA
198.16.2.0/23ARINNo 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.