bgpreport

Network · data from 2026-11-12

AS24954 HAVAS Havas SAS

Registry name: HAVAS Havas SAS, FR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS24954, 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.
194.5.74.0/24 Valid RIR databaseRIPE 673 100% 67
194.5.75.0/24 Valid RIR databaseRIPE 673 100% 67
194.5.76.0/24 Valid RIR databaseRIPE 673 100% 67
194.5.77.0/24 Valid RIR databaseRIPE 673 100% 67
194.5.150.0/24 Valid RIR databaseRIPE 673 100% 67
194.5.151.0/24 Valid RIR databaseRIPE 673 100% 67
194.5.166.0/24 Valid RIR databaseRIPE 673 100% 67
194.5.167.0/24 Valid RIR databaseRIPE 673 100% 67
193.57.12.0/24 Valid RIR databaseRIPE 672 100% 67
193.57.13.0/24 Valid RIR databaseRIPE 672 100% 67
193.57.34.0/24 Valid RIR databaseRIPE 672 100% 67
193.57.176.0/24 Valid RIR databaseRIPE 672 100% 67
193.57.177.0/24 Valid RIR databaseRIPE 672 100% 67
193.57.178.0/24 Valid RIR databaseRIPE 672 100% 67
193.57.179.0/24 Valid RIR databaseRIPE 672 100% 67
193.57.180.0/24 Valid RIR databaseRIPE 672 100% 67
2001:67c:8a0::/48 Valid RIR databaseRIPE 635 100% 68

AS-SET

AS24954 isn't in PeeringDB, where networks name their AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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