bgpreport

Network · data from 2026-11-12

AS36291 SANOFI - Sanofi

Registry name: SANOFI - Sanofi, US · not in PeeringDB

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

Announced routes

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

137.174.156.32/29 Invalid: origin None 1 0%low visibility 1
155.65.0.0/16 No ROA None 673 100% 67
155.65.251.0/24 No ROA Other origin only 673 100% 67
157.206.0.0/16 No ROA None 673 100% 67
168.124.0.0/16 No ROA None 673 100% 67
192.234.110.0/24 No ROA None 673 100% 67
192.234.111.0/24 No ROA None 673 100% 67
205.137.76.0/24 No ROA None 673 100% 67
205.137.77.0/24 No ROA None 673 100% 67
205.137.78.0/23 No ROA None 673 100% 67
205.137.79.0/24 No ROA RIR databaseARIN 673 100% 67

AS-SET

AS36291 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: origin1
  • ROA: none10
  • Route object: none10
ChangePrefix or setDetailFull-table peers
ROA: origin137.174.156.32/29ROAs covering it name AS12085, AS15830, not AS36291. If AS36291 should announce it, add a ROA for AS36291.1 of 673
Route object: none137.174.156.32/29No route object for it. Add a route object with origin AS36291 in the RIR database for the space.1 of 673
ROA: none155.65.0.0/16No ROA covers it. Add a ROA for AS36291, maxLength 16.673 of 673
Route object: none155.65.0.0/16No route object for it. Add a route object with origin AS36291 in the RIR database for the space.673 of 673
ROA: none155.65.251.0/24No ROA covers it. Add a ROA for AS36291, maxLength 24.673 of 673
Route object: none155.65.251.0/24Route objects for it name AS7922. Add a route object with origin AS36291 in the RIR database for the space.673 of 673
ROA: none157.206.0.0/16No ROA covers it. Add a ROA for AS36291, maxLength 16.673 of 673
Route object: none157.206.0.0/16No route object for it. Add a route object with origin AS36291 in the RIR database for the space.673 of 673
ROA: none168.124.0.0/16No ROA covers it. Add a ROA for AS36291, maxLength 16.673 of 673
Route object: none168.124.0.0/16No route object for it. Add a route object with origin AS36291 in the RIR database for the space.673 of 673
ROA: none192.234.110.0/24No ROA covers it. Add a ROA for AS36291, maxLength 24.673 of 673
Route object: none192.234.110.0/24No route object for it. Add a route object with origin AS36291 in the RIR database for the space.673 of 673
ROA: none192.234.111.0/24No ROA covers it. Add a ROA for AS36291, maxLength 24.673 of 673
Route object: none192.234.111.0/24No route object for it. Add a route object with origin AS36291 in the RIR database for the space.673 of 673
ROA: none205.137.76.0/24No ROA covers it. Add a ROA for AS36291, maxLength 24.673 of 673
Route object: none205.137.76.0/24No route object for it. Add a route object with origin AS36291 in the RIR database for the space.673 of 673
ROA: none205.137.77.0/24No ROA covers it. Add a ROA for AS36291, maxLength 24.673 of 673
Route object: none205.137.77.0/24No route object for it. Add a route object with origin AS36291 in the RIR database for the space.673 of 673
ROA: none205.137.78.0/23No ROA covers it. Add a ROA for AS36291, maxLength 23.673 of 673
Route object: none205.137.78.0/23No route object for it. Add a route object with origin AS36291 in the RIR database for the space.673 of 673
ROA: none205.137.79.0/24No ROA covers it. Add a ROA for AS36291, maxLength 24.673 of 673

Route objects not announced

Every route object with origin AS36291 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.