bgpreport

Network · data from 2026-11-12

AS25591 BCLAN-AS BCLan LLC

Registry name: BCLAN-AS BCLan LLC, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS25591, 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.
217.175.0.0/20 No ROA RIR databaseRIPE 672 100% 66
5.101.208.0/22 Valid RIR databaseRIPE 672 100% 66
5.101.212.0/22 Valid RIR databaseRIPE 672 100% 66
5.183.64.0/22 Valid RIR databaseRIPE 672 100% 66
5.183.68.0/22 Valid RIR databaseRIPE 672 100% 66
5.188.144.0/22 Valid RIR databaseRIPE 672 100% 66
31.3.24.0/22 Valid RIR databaseRIPE 672 100% 66
31.3.28.0/22 Valid RIR databaseRIPE 672 100% 66
37.75.216.0/22 Valid RIR databaseRIPE 672 100% 66
37.75.220.0/22 Valid RIR databaseRIPE 672 100% 66
45.84.60.0/22 Valid RIR databaseRIPE 672 100% 66
80.242.96.0/20 Valid RIR databaseRIPE 672 100% 66
80.242.96.0/22 Valid RIR databaseRIPE 672 100% 66
80.242.100.0/22 Valid RIR databaseRIPE 672 100% 66
80.242.104.0/22 Valid RIR databaseRIPE 672 100% 66
80.242.108.0/22 Valid RIR databaseRIPE 672 100% 66
91.243.36.0/22 Valid RIR databaseRIPE 672 100% 66
92.118.200.0/22 Valid RIR databaseRIPE 672 100% 66
93.190.176.0/22 Valid RIR databaseRIPE 672 100% 66
93.190.180.0/22 Valid RIR databaseRIPE 672 100% 66
185.14.16.0/22 Valid RIR databaseRIPE 672 100% 66
185.104.4.0/22 Valid RIR databaseRIPE 672 100% 66
185.140.134.0/23 Valid RIR databaseRIPE 672 100% 66
217.175.0.0/22 Valid RIR databaseRIPE 672 100% 66
217.175.4.0/22 Valid RIR databaseRIPE 672 100% 66
217.175.8.0/22 Valid RIR databaseRIPE 672 100% 66
217.175.12.0/22 Valid RIR databaseRIPE 672 100% 66

AS-SET

AS25591 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 1 are in fix.csv.

  • ROA: none1
ChangePrefix or setDetailFull-table peers
ROA: none217.175.0.0/20No ROA covers it. Add a ROA for AS25591, maxLength 20.672 of 673

Route objects not announced

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