bgpreport

Network · data from 2026-11-12

AS30919 ESTHER - AFETI

Registry name: EXPERTISEFRANCE Expertise France SAS, FR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS30919, 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.
2a00:c2e0::/48 No ROA Nonecovered by 2a00:c2e0::/32 605 95% 67
2a00:c2e0:100::/48 No ROA Nonecovered by 2a00:c2e0::/32 605 95% 67
185.101.64.0/22 No ROA RIR databaseRIPE 673 100% 66
185.101.64.0/23 No ROA RIR databaseRIPE 673 100% 66
185.101.64.0/24 No ROA RIR databaseRIPE 673 100% 66
185.101.65.0/24 No ROA RIR databaseRIPE 673 100% 66
2a00:c2e0::/32 No ROA RIR databaseRIPE 605 95% 67

AS-SET

AS30919'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 11 are in fix.csv.

  • ROA: none7
  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2a00:c2e0::/48No ROA covers it. Add a ROA for AS30919, maxLength 48.605 of 636
Route object: none2a00:c2e0::/48No route object for it. A route object for 2a00:c2e0::/32 with origin AS30919 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30919 in the RIR database for the space.605 of 636
ROA: none2a00:c2e0:100::/48No ROA covers it. Add a ROA for AS30919, maxLength 48.605 of 636
Route object: none2a00:c2e0:100::/48No route object for it. A route object for 2a00:c2e0::/32 with origin AS30919 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30919 in the RIR database for the space.605 of 636
ROA: none185.101.64.0/22No ROA covers it. Add a ROA for AS30919, maxLength 22.673 of 673
ROA: none185.101.64.0/23No ROA covers it. Add a ROA for AS30919, maxLength 23.673 of 673
ROA: none185.101.64.0/24No ROA covers it. Add a ROA for AS30919, maxLength 24.673 of 673
ROA: none185.101.65.0/24No ROA covers it. Add a ROA for AS30919, maxLength 24.673 of 673
ROA: none2a00:c2e0::/32No ROA covers it. Add a ROA for AS30919, maxLength 32.605 of 636

Route objects not announced

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

185.101.66.0/24RIPENo ROA
185.101.67.0/24RIPENo 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.