Network · data from 2026-11-12

AS1712 FR-RENATER-ENST - Renater

Registry name: FR-RENATER-ENST - Renater, FR · not in PeeringDB

31IPv4 routes 90.3% RPKI valid · 100.0% with a route object

2IPv6 routes 100.0% RPKI valid · 100.0% with a route object

3RPKI invalid 0 origin · 3 maxLength

0No ROA 0 with no route object for this origin

3Low visibility seen by under 10% of full-table peers

15Route objects not announced registered with origin AS1712, seen from no peer

Announced routes

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


137.194.8.0/21	Invalid: maxLength	RIR databaseRIPE	27 4%low visibility	20
137.194.12.0/22	Invalid: maxLength	RIR databaseRIPE	27 4%low visibility	20
137.194.69.0/24	Invalid: maxLength	RIR databaseRIPE	2 0%low visibility	2
137.194.28.0/23	Valid	RIR databaseRIPE	673 100%	67
137.194.30.0/24	Valid	RIR databaseRIPE	673 100%	67
137.194.62.0/24	Valid	RIR databaseRIPE	673 100%	67
137.194.68.0/24	Valid	RIR databaseRIPE	673 100%	67
137.194.0.0/16	Valid	RIR databaseRIPE	672 100%	68
137.194.0.0/23	Valid	RIR databaseRIPE	670 100%	68
137.194.19.0/24	Valid	RIR databaseRIPE	670 100%	68
137.194.20.0/24	Valid	RIR databaseRIPE	670 100%	68
137.194.47.0/24	Valid	RIR databaseRIPE	670 100%	68
137.194.52.0/23	Valid	RIR databaseRIPE	670 100%	68
137.194.54.0/23	Valid	RIR databaseRIPE	670 100%	68
137.194.57.0/24	Valid	RIR databaseRIPE	670 100%	68
137.194.104.0/21	Valid	RIR databaseRIPE	670 100%	68
137.194.112.0/21	Valid	RIR databaseRIPE	670 100%	68
137.194.132.0/22	Valid	RIR databaseRIPE	670 100%	68
137.194.136.0/22	Valid	RIR databaseRIPE	670 100%	68
137.194.140.0/22	Valid	RIR databaseRIPE	670 100%	68
137.194.144.0/20	Valid	RIR databaseRIPE	670 100%	68
137.194.172.0/23	Valid	RIR databaseRIPE	670 100%	68
137.194.174.0/23	Valid	RIR databaseRIPE	670 100%	68
137.194.176.0/20	Valid	RIR databaseRIPE	670 100%	68
137.194.192.0/23	Valid	RIR databaseRIPE	670 100%	68
137.194.196.0/22	Valid	RIR databaseRIPE	670 100%	68
137.194.206.0/23	Valid	RIR databaseRIPE	670 100%	68
137.194.216.0/21	Valid	RIR databaseRIPE	670 100%	68
137.194.224.0/21	Valid	RIR databaseRIPE	670 100%	68
137.194.240.0/20	Valid	RIR databaseRIPE	670 100%	68
137.194.2.0/23	Valid	RIR databaseRIPE	667 99%	68
2a04:8ec0::/48	Valid	RIR databaseRIPE	635 100%	68
2a04:8ec0:1::/48	Valid	RIR databaseRIPE	635 100%	67

137.194.8.0/21

Invalid: maxLength

RIR databaseRIPE

27 4%low visibility

137.194.12.0/22

Invalid: maxLength

RIR databaseRIPE

27 4%low visibility

137.194.69.0/24

Invalid: maxLength

RIR databaseRIPE

2 0%low visibility

137.194.28.0/23

Valid

RIR databaseRIPE

673 100%

137.194.30.0/24

Valid

RIR databaseRIPE

673 100%

137.194.62.0/24

Valid

RIR databaseRIPE

673 100%

137.194.68.0/24

Valid

RIR databaseRIPE

673 100%

137.194.0.0/16

Valid

RIR databaseRIPE

672 100%

137.194.0.0/23

Valid

RIR databaseRIPE

670 100%

137.194.19.0/24

Valid

RIR databaseRIPE

670 100%

137.194.20.0/24

Valid

RIR databaseRIPE

670 100%

137.194.47.0/24

Valid

RIR databaseRIPE

670 100%

137.194.52.0/23

Valid

RIR databaseRIPE

670 100%

137.194.54.0/23

Valid

RIR databaseRIPE

670 100%

137.194.57.0/24

Valid

RIR databaseRIPE

670 100%

137.194.104.0/21

Valid

RIR databaseRIPE

670 100%

137.194.112.0/21

Valid

RIR databaseRIPE

670 100%

137.194.132.0/22

Valid

RIR databaseRIPE

670 100%

137.194.136.0/22

Valid

RIR databaseRIPE

670 100%

137.194.140.0/22

Valid

RIR databaseRIPE

670 100%

137.194.144.0/20

Valid

RIR databaseRIPE

670 100%

137.194.172.0/23

Valid

RIR databaseRIPE

670 100%

137.194.174.0/23

Valid

RIR databaseRIPE

670 100%

137.194.176.0/20

Valid

RIR databaseRIPE

670 100%

137.194.192.0/23

Valid

RIR databaseRIPE

670 100%

137.194.196.0/22

Valid

RIR databaseRIPE

670 100%

137.194.206.0/23

Valid

RIR databaseRIPE

670 100%

137.194.216.0/21

Valid

RIR databaseRIPE

670 100%

137.194.224.0/21

Valid

RIR databaseRIPE

670 100%

137.194.240.0/20

Valid

RIR databaseRIPE

670 100%

137.194.2.0/23

Valid

RIR databaseRIPE

667 99%

2a04:8ec0::/48

Valid

RIR databaseRIPE

635 100%

2a04:8ec0:1::/48

Valid

RIR databaseRIPE

635 100%

AS-SET

AS1712 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 18 are in fix.csv.

ROA: maxLength3
Route object: not announced15

Change	Prefix or set	Detail	Full-table peers
ROA: maxLength	137.194.8.0/21	ROA 137.194.0.0/16 AS1712 has maxLength 16; the route is a /21. Raise the maxLength, or add a ROA for 137.194.8.0/21.	27 of 673
ROA: maxLength	137.194.12.0/22	ROA 137.194.0.0/16 AS1712 has maxLength 16; the route is a /22. Raise the maxLength, or add a ROA for 137.194.12.0/22.	27 of 673
ROA: maxLength	137.194.69.0/24	ROA 137.194.0.0/16 AS1712 has maxLength 16; the route is a /24. Raise the maxLength, or add a ROA for 137.194.69.0/24.	2 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: maxLength

137.194.8.0/21

ROA 137.194.0.0/16 AS1712 has maxLength 16; the route is a /21. Raise the maxLength, or add a ROA for 137.194.8.0/21.

27 of 673

ROA: maxLength

137.194.12.0/22

ROA 137.194.0.0/16 AS1712 has maxLength 16; the route is a /22. Raise the maxLength, or add a ROA for 137.194.12.0/22.

27 of 673

ROA: maxLength

137.194.69.0/24

ROA 137.194.0.0/16 AS1712 has maxLength 16; the route is a /24. Raise the maxLength, or add a ROA for 137.194.69.0/24.

2 of 673

Route objects not announced

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


137.194.8.0/22	RIPE	Invalid: maxLength
137.194.21.0/24	RIPE	Invalid: maxLength
137.194.37.0/24	RIPE	Invalid: maxLength
137.194.46.0/24	RIPE	Invalid: maxLength
137.194.56.0/24	RIPE	Invalid: maxLength
137.194.58.0/23	RIPE	Invalid: maxLength
137.194.61.0/24	RIPE	Invalid: maxLength
137.194.63.0/24	RIPE	Invalid: maxLength
137.194.164.0/23	RIPE	Invalid: maxLength
137.194.208.0/21	RIPE	Invalid: maxLength
192.33.155.0/24	RIPE	Invalid: origin
2a04:8ec0::/32	RIPE	No ROA
2a09:6847::/32	RIPE	Valid
2a09:6847:bb00::/48	RIPE	Valid
2a09:6847:fa10::/44	RIPE	Valid

137.194.8.0/22

RIPE

Invalid: maxLength

137.194.21.0/24

RIPE

Invalid: maxLength

137.194.37.0/24

RIPE

Invalid: maxLength

137.194.46.0/24

RIPE

Invalid: maxLength

137.194.56.0/24

RIPE

Invalid: maxLength

137.194.58.0/23

RIPE

Invalid: maxLength

137.194.61.0/24

RIPE

Invalid: maxLength

137.194.63.0/24

RIPE

Invalid: maxLength

137.194.164.0/23

RIPE

Invalid: maxLength

137.194.208.0/21

RIPE

Invalid: maxLength

192.33.155.0/24

RIPE

Invalid: origin

2a04:8ec0::/32

RIPE

No ROA

2a09:6847::/32

RIPE

Valid

2a09:6847:bb00::/48

RIPE

Valid

2a09:6847:fa10::/44

RIPE

Valid

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.