bgpreport

Network · data from 2026-11-12

AS60641 HEXATEL HEXATEL SAS

Registry name: HEXATEL HEXATEL SAS, FR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS60641, 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.
185.45.172.0/23 No ROA None 671 100% 67
82.138.96.0/22 No ROA RIR databaseRIPE 671 100% 67
5.39.234.0/24 Valid None 671 100% 67
5.39.236.0/24 Valid None 671 100% 67
5.39.233.0/24 Valid RIR databaseRIPE 671 100% 67
38.126.212.0/22 Valid RIR databaseARIN 671 100% 67
185.24.156.0/24 Valid RIR databaseRIPE 671 100% 67
185.24.157.0/24 Valid RIR databaseRIPE 671 100% 67
185.24.158.0/24 Valid RIR databaseRIPE 671 100% 67
185.24.159.0/24 Valid RIR databaseRIPE 671 100% 67
185.52.44.0/22 Valid RIR databaseRIPE 671 100% 67

AS-SET

AS60641 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 5 are in fix.csv.

  • ROA: none2
  • Route object: none3
ChangePrefix or setDetailFull-table peers
ROA: none185.45.172.0/23No ROA covers it. Add a ROA for AS60641, maxLength 23.671 of 673
Route object: none185.45.172.0/23No route object for it. Add a route object with origin AS60641 in the RIR database for the space.671 of 673
ROA: none82.138.96.0/22No ROA covers it. Add a ROA for AS60641, maxLength 22.671 of 673
Route object: none5.39.234.0/24No route object for it. Add a route object with origin AS60641 in the RIR database for the space.671 of 673
Route object: none5.39.236.0/24No route object for it. Add a route object with origin AS60641 in the RIR database for the space.671 of 673

Route objects not announced

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