bgpreport

Network · data from 2026-11-12

AS29301 Karavel

Registry name: KARAVEL-AS Karavel SAS, FR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS29301, 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.
2001:678:bf8::/48 No ROA None 635 100% 67
193.46.206.0/24 No ROA RIR databaseRIPE 672 100% 66
195.149.66.0/24 No ROA RIR databaseRIPE 672 100% 66

AS-SET

AS29301's PeeringDB record names no 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 4 are in fix.csv.

  • ROA: none3
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none2001:678:bf8::/48No ROA covers it. Add a ROA for AS29301, maxLength 48.635 of 636
Route object: none2001:678:bf8::/48No route object for it. Add a route object with origin AS29301 in the RIR database for the space.635 of 636
ROA: none193.46.206.0/24No ROA covers it. Add a ROA for AS29301, maxLength 24.672 of 673
ROA: none195.149.66.0/24No ROA covers it. Add a ROA for AS29301, maxLength 24.672 of 673

Route objects not announced

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