bgpreport

Network · data from 2026-11-12

AS12844 Bouygues Telecom

Registry name: BOUYGTEL-B2B Bouygues Telecom SA, FR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS12844, 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.
159.31.0.0/16 No ROA Other origin only 666 99% 68
192.70.82.0/24 No ROA Other origin only 666 99% 68
5.253.152.0/23 No ROA RIR databaseRIPE 672 100% 67
163.108.144.0/24 No ROA RIR databaseRIPE 672 100% 67
193.178.138.0/24 No ROA RIR databaseRIPE 672 100% 67
62.100.208.0/24 Valid RIR databaseRIPE 672 100% 67
78.105.164.0/22 Valid RIR databaseRADB, RIPE 672 100% 67
85.203.32.0/24 Valid RIR databaseRIPE 672 100% 67
124.198.146.0/23 Valid RIR databaseRIPE 672 100% 67
158.173.26.0/23 Valid RIR databaseRIPE 672 100% 67
158.173.28.0/22 Valid RIR databaseRIPE 672 100% 67
158.173.148.0/22 Valid RIR databaseRIPE 672 100% 67
158.173.248.0/21 Valid RIR databaseRIPE 672 100% 67
185.71.220.0/23 Valid RIR databaseRIPE 672 100% 67
185.102.170.0/24 Valid RIR databaseRIPE 672 100% 67
185.183.0.0/22 Valid RIR databaseRIPE 672 100% 67
185.217.119.0/24 Valid RIR databaseRIPE 672 100% 67
194.34.173.0/24 Valid RIR databaseRIPE 672 100% 67
212.32.74.0/24 Valid RIR databaseRIPE 672 100% 67
45.84.215.0/24 Valid RIR databaseRIPE 671 100% 67
45.85.107.0/24 Valid RIR databaseRIPE 671 100% 67
45.128.197.0/24 Valid RIR databaseRIPE 671 100% 67
45.154.137.0/24 Valid RIR databaseRIPE 671 100% 67

AS-SET

AS12844'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 8 are in fix.csv.

  • ROA: none5
  • Route object: none2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none159.31.0.0/16No ROA covers it. Add a ROA for AS12844, maxLength 16.666 of 673
Route object: none159.31.0.0/16Route objects for it name AS2067, AS2200. Add a route object with origin AS12844 in the RIR database for the space.666 of 673
ROA: none192.70.82.0/24No ROA covers it. Add a ROA for AS12844, maxLength 24.666 of 673
Route object: none192.70.82.0/24Route objects for it name AS2067. Add a route object with origin AS12844 in the RIR database for the space.666 of 673
ROA: none5.253.152.0/23No ROA covers it. Add a ROA for AS12844, maxLength 23.672 of 673
ROA: none163.108.144.0/24No ROA covers it. Add a ROA for AS12844, maxLength 24.672 of 673
ROA: none193.178.138.0/24No ROA covers it. Add a ROA for AS12844, maxLength 24.672 of 673

Route objects not announced

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

62.100.196.0/22RIPEValid

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.