bgpreport

Network · data from 2026-11-12

AS1942 FR-TIGRE - Renater

Registry name: FR-TIGRE - Renater, FR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS1942, 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.
134.158.40.0/21 Invalid: origin Other origin only 1 0%low visibility 1
193.48.85.0/24 Invalid: origin None 1 0%low visibility 1
130.190.0.0/16 No ROA RIR databaseRIPE 672 100% 68
192.93.174.0/24 No ROA RIR databaseRIPE 672 100% 68
192.93.175.0/24 No ROA RIR databaseRIPE 672 100% 68
192.93.176.0/22 No ROA RIR databaseRIPE 672 100% 68
45.149.140.0/22 Valid RIR databaseRIPE 672 100% 68
129.88.0.0/16 Valid RIR databaseRIPE 672 100% 68
147.173.0.0/16 Valid RIR databaseRIPE 672 100% 68
152.77.0.0/16 Valid RIR databaseRIPE 672 100% 68
160.103.0.0/16 Valid RIR databaseRIPE 672 100% 68
192.33.171.0/24 Valid RIR databaseRIPE 672 100% 68
147.171.0.0/16 Valid RIR databaseRIPE 658 98% 68
193.48.83.0/24 Valid RIR databaseRIPE 20 3%low visibility 18

AS-SET

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

  • ROA: origin2
  • ROA: none4
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: origin134.158.40.0/21ROAs covering it name AS789, not AS1942. If AS1942 should announce it, add a ROA for AS1942.1 of 673
Route object: none134.158.40.0/21Route objects for it name AS789. Add a route object with origin AS1942 in the RIR database for the space.1 of 673
ROA: origin193.48.85.0/24ROAs covering it name AS2200, not AS1942. If AS1942 should announce it, add a ROA for AS1942.1 of 673
Route object: none193.48.85.0/24No route object for it. Add a route object with origin AS1942 in the RIR database for the space.1 of 673
ROA: none130.190.0.0/16No ROA covers it. Add a ROA for AS1942, maxLength 16.672 of 673
ROA: none192.93.174.0/24No ROA covers it. Add a ROA for AS1942, maxLength 24.672 of 673
ROA: none192.93.175.0/24No ROA covers it. Add a ROA for AS1942, maxLength 24.672 of 673
ROA: none192.93.176.0/22No ROA covers it. Add a ROA for AS1942, maxLength 22.672 of 673

Route objects not announced

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