bgpreport

Network · data from 2026-11-12

AS59754 BIM Bank of Industry and Mine PJSC

Registry name: BIM Bank of Industry and Mine PJSC, IR · not in PeeringDB

4IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
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
3Route objects not announced registered with origin AS59754, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS59754, 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.
2a05:3e40::/29 No ROA RIR databaseRIPE 633 100% 68
185.73.76.0/24 Valid RIR databaseRIPE 670 100% 66
185.73.77.0/24 Valid RIR databaseRIPE 670 100% 66
185.73.78.0/24 Valid RIR databaseRIPE 669 99% 67
185.73.79.0/24 Valid RIR databaseRIPE 669 99% 67

AS-SET

AS59754 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 4 are in fix.csv.

  • ROA: none1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none2a05:3e40::/29No ROA covers it. Add a ROA for AS59754, maxLength 29.633 of 636

Route objects not announced

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

185.73.76.0/22RADB, RIPEValid
185.73.76.0/23RIPEValid
185.73.78.0/23RIPEValid

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.