bgpreport

Network · data from 2026-11-12

AS25117 Bouygues Telecom Business-Distribution

Registry name: EI-TELECOM Euro-Information-Europeenne de Traitement de l'Information SAS, FR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS25117, 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.
193.56.244.0/24 Valid Nonecovered by 193.56.244.0/23 673 100% 67
193.56.245.0/24 Valid Nonecovered by 193.56.244.0/23 673 100% 67
2a04:cec0:1300::/41 Valid Nonecovered by 2a04:cec0:1300::/40 636 100% 67
2a04:cec0:1380::/41 Valid Nonecovered by 2a04:cec0:1300::/40 636 100% 67
185.228.228.0/24 Valid RIR databaseRIPE 673 100% 67
185.228.229.0/24 Valid RIR databaseRIPE 673 100% 67
185.228.230.0/24 Valid RIR databaseRIPE 673 100% 67
185.228.231.0/24 Valid RIR databaseRIPE 673 100% 67
193.56.242.0/24 Valid RIR databaseRIPE 673 100% 67
193.56.243.0/24 Valid RIR databaseRIPE 673 100% 67
193.57.120.0/24 Valid RIR databaseRIPE 672 100% 67
193.57.121.0/24 Valid RIR databaseRIPE 672 100% 67
193.57.124.0/24 Valid RIR databaseRIPE 672 100% 67
193.57.125.0/24 Valid RIR databaseRIPE 672 100% 67

AS-SET

AS25117'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 10 are in fix.csv.

  • Route object: none4
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
Route object: none193.56.244.0/24No route object for it. A route object for 193.56.244.0/23 with origin AS25117 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25117 in the RIR database for the space.673 of 673
Route object: none193.56.245.0/24No route object for it. A route object for 193.56.244.0/23 with origin AS25117 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25117 in the RIR database for the space.673 of 673
Route object: none2a04:cec0:1300::/41No route object for it. A route object for 2a04:cec0:1300::/40 with origin AS25117 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25117 in the RIR database for the space.636 of 636
Route object: none2a04:cec0:1380::/41No route object for it. A route object for 2a04:cec0:1300::/40 with origin AS25117 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25117 in the RIR database for the space.636 of 636

Route objects not announced

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

185.228.228.0/22RIPEValid
193.56.244.0/23RIPEValid
193.57.124.0/23RADBValid
2a03:7787:fffc::/47RIPEValid
2a03:7787:fffe::/47RIPEValid
2a04:cec0:1300::/40RIPEInvalid: origin

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.