bgpreport

Network · data from 2026-11-12

AS8904 BANK_OF_RUSSIA Bank of Russia

Registry name: BANK_OF_RUSSIA Bank of Russia, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS8904, 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.
212.40.223.0/24 No ROA Nonecovered by 212.40.222.0/23 668 99% 67
212.40.202.0/23 No ROA RIR databaseRIPE 672 100% 67
212.40.192.0/21 No ROA RIR databaseRIPE 668 99% 67
212.40.208.0/21 No ROA RIR databaseRIPE 668 99% 66
212.40.222.0/23 No ROA RIR databaseRIPE 668 99% 66
212.40.204.0/22 No ROA RIR databaseRIPE 2 0%low visibility 2

AS-SET

AS8904 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: none6
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none212.40.223.0/24No ROA covers it. Add a ROA for AS8904, maxLength 24.668 of 673
Route object: none212.40.223.0/24No route object for it. A route object for 212.40.222.0/23 with origin AS8904 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8904 in the RIR database for the space.668 of 673
ROA: none212.40.202.0/23No ROA covers it. Add a ROA for AS8904, maxLength 23.672 of 673
ROA: none212.40.192.0/21No ROA covers it. Add a ROA for AS8904, maxLength 21.668 of 673
ROA: none212.40.208.0/21No ROA covers it. Add a ROA for AS8904, maxLength 21.668 of 673
ROA: none212.40.222.0/23No ROA covers it. Add a ROA for AS8904, maxLength 23.668 of 673
ROA: none212.40.204.0/22No ROA covers it. Add a ROA for AS8904, maxLength 22.2 of 673

Route objects not announced

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

212.40.192.0/20RIPENo ROA

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.