bgpreport

Network · data from 2026-11-12

AS201052 GOVCERT-RU-AS Autonomous nonprofit organisation "Computer Incident Response Center"

Registry name: GOVCERT-RU-AS Autonomous nonprofit organisation "Computer Incident Response Center", RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS201052, 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.
144.206.64.0/20 No ROA Nonecovered by 144.206.64.0/19 672 100% 67
144.206.80.0/21 No ROA Nonecovered by 144.206.64.0/19 672 100% 67
144.206.88.0/24 No ROA RIR databaseRIPE 673 100% 67
144.206.89.0/24 No ROA RIR databaseRIPE 673 100% 67
144.206.90.0/24 No ROA RIR databaseRIPE 673 100% 67
144.206.91.0/24 No ROA RIR databaseRIPE 673 100% 67
144.206.92.0/24 No ROA RIR databaseRIPE 673 100% 67
144.206.93.0/24 No ROA RIR databaseRIPE 673 100% 67
144.206.94.0/24 No ROA RIR databaseRIPE 673 100% 67
144.206.95.0/24 No ROA RIR databaseRIPE 673 100% 67
194.85.25.0/24 No ROA RIR databaseRIPE 673 100% 67

AS-SET

AS201052 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 38 are in fix.csv.

  • ROA: none11
  • Route object: none2
  • Route object: not announced25
ChangePrefix or setDetailFull-table peers
ROA: none144.206.64.0/20No ROA covers it. Add a ROA for AS201052, maxLength 20.672 of 673
Route object: none144.206.64.0/20No route object for it. A route object for 144.206.64.0/19 with origin AS201052 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201052 in the RIR database for the space.672 of 673
ROA: none144.206.80.0/21No ROA covers it. Add a ROA for AS201052, maxLength 21.672 of 673
Route object: none144.206.80.0/21No route object for it. A route object for 144.206.64.0/19 with origin AS201052 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201052 in the RIR database for the space.672 of 673
ROA: none144.206.88.0/24No ROA covers it. Add a ROA for AS201052, maxLength 24.673 of 673
ROA: none144.206.89.0/24No ROA covers it. Add a ROA for AS201052, maxLength 24.673 of 673
ROA: none144.206.90.0/24No ROA covers it. Add a ROA for AS201052, maxLength 24.673 of 673
ROA: none144.206.91.0/24No ROA covers it. Add a ROA for AS201052, maxLength 24.673 of 673
ROA: none144.206.92.0/24No ROA covers it. Add a ROA for AS201052, maxLength 24.673 of 673
ROA: none144.206.93.0/24No ROA covers it. Add a ROA for AS201052, maxLength 24.673 of 673
ROA: none144.206.94.0/24No ROA covers it. Add a ROA for AS201052, maxLength 24.673 of 673
ROA: none144.206.95.0/24No ROA covers it. Add a ROA for AS201052, maxLength 24.673 of 673
ROA: none194.85.25.0/24No ROA covers it. Add a ROA for AS201052, maxLength 24.673 of 673

Route objects not announced

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

144.206.64.0/19RIPENo ROA
144.206.64.0/24RIPENo ROA
144.206.65.0/24RIPENo ROA
144.206.66.0/24RIPENo ROA
144.206.67.0/24RIPENo ROA
144.206.68.0/24RIPENo ROA
144.206.69.0/24RIPENo ROA
144.206.70.0/24RIPENo ROA
144.206.71.0/24RIPENo ROA
144.206.72.0/24RIPENo ROA
144.206.73.0/24RIPENo ROA
144.206.74.0/24RIPENo ROA
144.206.75.0/24RIPENo ROA
144.206.76.0/24RIPENo ROA
144.206.77.0/24RIPENo ROA
144.206.78.0/24RIPENo ROA
144.206.79.0/24RIPENo ROA
144.206.80.0/24RIPENo ROA
144.206.81.0/24RIPENo ROA
144.206.82.0/24RIPENo ROA
144.206.83.0/24RIPENo ROA
144.206.84.0/24RIPENo ROA
144.206.85.0/24RIPENo ROA
144.206.86.0/24RIPENo ROA
144.206.87.0/24RIPENo 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.