Network · data from 2026-11-12

AS51664 Bilendi Technology

Registry name: AS-BILENDI-TECH Bilendi Technology SARL, FR · PeeringDB

8IPv4 routes 100.0% RPKI valid · 100.0% with a route object

6IPv6 routes 100.0% RPKI valid · 66.7% with a route object

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

5Route objects not announced registered with origin AS51664, seen from no peer

Announced routes

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


2a12:a7c0::/29	Valid	None	602 95%	67
2a12:a7c4::/30	Valid	None	602 95%	67
78.40.88.0/24	Valid	RIR databaseRIPE	673 100%	67
78.40.89.0/24	Valid	RIR databaseRIPE	673 100%	67
78.40.90.0/24	Valid	RIR databaseRIPE	673 100%	67
78.40.91.0/24	Valid	RIR databaseRIPE	673 100%	67
78.40.92.0/24	Valid	RIR databaseRIPE	673 100%	67
78.40.93.0/24	Valid	RIR databaseRIPE	673 100%	67
78.40.94.0/24	Valid	RIR databaseRIPE	673 100%	67
78.40.95.0/24	Valid	RIR databaseRIPE	673 100%	67
2a12:a7c0::/32	Valid	RIR databaseRIPE	603 95%	67
2a12:a7c1::/32	Valid	RIR databaseRIPE	603 95%	67
2a12:a7c2::/32	Valid	RIR databaseRIPE	603 95%	67
2a12:a7c3::/32	Valid	RIR databaseRIPE	603 95%	67

AS-SET

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

Route object: none2
Route object: not announced5

Change	Prefix or set	Detail	Full-table peers
Route object: none	2a12:a7c0::/29	No route object for it. Add a route object with origin AS51664 in the RIR database for the space.	602 of 636
Route object: none	2a12:a7c4::/30	No route object for it. Add a route object with origin AS51664 in the RIR database for the space.	602 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

2a12:a7c0::/29

No route object for it. Add a route object with origin AS51664 in the RIR database for the space.

602 of 636

Route object: none

2a12:a7c4::/30

No route object for it. Add a route object with origin AS51664 in the RIR database for the space.

602 of 636

Route objects not announced

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


78.40.88.0/21	RIPE	No ROA
2a12:a7c4::/32	RIPE	Invalid: maxLength
2a12:a7c5::/32	RIPE	Invalid: maxLength
2a12:a7c6::/32	RIPE	Invalid: maxLength
2a12:a7c7::/32	RIPE	Invalid: maxLength

78.40.88.0/21

RIPE

No ROA

2a12:a7c4::/32

RIPE

Invalid: maxLength

2a12:a7c5::/32

RIPE

Invalid: maxLength

2a12:a7c6::/32

RIPE

Invalid: maxLength

2a12:a7c7::/32

RIPE

Invalid: maxLength

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.