bgpreport

Network · data from 2026-11-12

AS202660 BRM-DataCenter "Uzbektelekom" Joint Stock Company

Registry name: BRM-DataCenter "Uzbektelekom" Joint Stock Company, UZ · not in PeeringDB

14IPv4 routes 78.6% RPKI valid · 100.0% with a route object
3IPv6 routes 33.3% RPKI valid · 33.3% with a route object
2RPKI invalid 0 origin · 2 maxLength
3No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS202660, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS202660, 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:45c7:e300::/40 Invalid: maxLength Nonecovered by 2a05:45c7:e000::/36 98 15% 41
2a05:45c7:e200::/40 Invalid: maxLength Nonecovered by 2a05:45c7:e000::/36 97 15% 40
89.126.212.0/22 No ROA RIR databaseRIPE 673 100% 68
89.126.216.0/22 No ROA RIR databaseRIPE 673 100% 66
109.94.173.0/24 No ROA RIR databaseRIPE 673 100% 68
87.192.252.0/24 Valid RIR databaseRIPE 673 100% 68
87.192.253.0/24 Valid RIR databaseRIPE 673 100% 68
89.126.208.0/22 Valid RIR databaseRIPE 673 100% 68
89.126.220.0/23 Valid RIR databaseRIPE 673 100% 68
89.126.222.0/23 Valid RIR databaseRIPE 673 100% 68
92.63.206.0/24 Valid RIR databaseRIPE 673 100% 68
92.63.207.0/24 Valid RIR databaseRIPE 673 100% 68
109.94.172.0/24 Valid RIR databaseRIPE 673 100% 68
185.74.4.0/22 Valid RIR databaseRIPE 673 100% 68
185.100.52.0/22 Valid RIR databaseRIPE 673 100% 68
198.163.207.0/24 Valid RIR databaseRIPE 673 100% 68
2a05:45c7:e000::/36 Valid RIR databaseRIPE 632 99% 70

AS-SET

AS202660 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 11 are in fix.csv.

  • ROA: maxLength2
  • ROA: none3
  • Route object: none2
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: maxLength2a05:45c7:e300::/40ROA 2a05:45c7:e000::/36 AS202660 has maxLength 36; the route is a /40. Raise the maxLength, or add a ROA for 2a05:45c7:e300::/40.98 of 636
Route object: none2a05:45c7:e300::/40No route object for it. A route object for 2a05:45c7:e000::/36 with origin AS202660 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202660 in the RIR database for the space.98 of 636
ROA: maxLength2a05:45c7:e200::/40ROA 2a05:45c7:e000::/36 AS202660 has maxLength 36; the route is a /40. Raise the maxLength, or add a ROA for 2a05:45c7:e200::/40.97 of 636
Route object: none2a05:45c7:e200::/40No route object for it. A route object for 2a05:45c7:e000::/36 with origin AS202660 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202660 in the RIR database for the space.97 of 636
ROA: none89.126.212.0/22No ROA covers it. Add a ROA for AS202660, maxLength 22.673 of 673
ROA: none89.126.216.0/22No ROA covers it. Add a ROA for AS202660, maxLength 22.673 of 673
ROA: none109.94.173.0/24No ROA covers it. Add a ROA for AS202660, maxLength 24.673 of 673

Route objects not announced

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

89.126.220.0/24RIPEInvalid: maxLength
198.163.196.0/22RIPEInvalid: origin
198.163.206.0/23RIPEInvalid: origin
198.163.206.0/24RIPEValid

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.