bgpreport

Network · data from 2026-11-12

AS14731 BEAUCE-TELECOM - Beauce Telecom

Registry name: BEAUCE-TELECOM - Beauce Telecom, CA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS14731, 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.

172.99.210.0/24 Valid Nonecovered by 172.99.208.0/22 673 100% 67
172.99.211.0/24 Valid Nonecovered by 172.99.208.0/22 673 100% 67
23.154.208.0/24 Valid RIR databaseALTDB, ARIN 673 100% 67
104.224.24.0/22 Valid RIR databaseARIN 673 100% 67
139.64.212.0/24 Valid RIR databaseARIN 673 100% 67
139.64.213.0/24 Valid RIR databaseARIN 673 100% 67
139.64.214.0/24 Valid RIR databaseARIN 673 100% 67
139.64.215.0/24 Valid RIR databaseARIN 673 100% 67
172.99.208.0/24 Valid RIR databaseARIN 673 100% 67
172.99.209.0/24 Valid RIR databaseARIN 673 100% 67

AS-SET

AS14731 isn't in PeeringDB, where networks name their 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 6 are in fix.csv.

  • Route object: none2
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none172.99.210.0/24No route object for it. A route object for 172.99.208.0/22 with origin AS14731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14731 in the RIR database for the space.673 of 673
Route object: none172.99.211.0/24No route object for it. A route object for 172.99.208.0/22 with origin AS14731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14731 in the RIR database for the space.673 of 673

Route objects not announced

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

64.254.238.0/24ALTDBNo ROA
139.64.212.0/22RADBValid
172.99.208.0/22ARIN, RADBValid
2602:fd69::/36ARINValid

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.