bgpreport

Network · data from 2026-11-12

AS50223 Alfa Telecom

Registry name: Alfa Alfa Telecom CJSC, KG · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS50223, 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.
109.71.228.0/24 Valid Nonecovered by 109.71.228.0/22 673 100% 66
46.251.192.0/19 Valid RIR databaseRIPE 673 100% 66
109.71.224.0/21 Valid RIR databaseRIPE 673 100% 66
109.71.224.0/24 Valid RIR databaseRIPE 673 100% 66
109.71.226.0/24 Valid RIR databaseRIPE 673 100% 66
109.71.229.0/24 Valid RIR databaseRIPE 673 100% 66
109.71.230.0/24 Valid RIR databaseRIPE 673 100% 66
109.71.231.0/24 Valid RIR databaseRIPE 673 100% 66
185.48.136.0/22 Valid RIR databaseRIPE 673 100% 66
185.48.136.0/24 Valid RIR databaseRIPE 673 100% 66
185.48.139.0/24 Valid RIR databaseRIPE 673 100% 66
46.251.192.0/24 Valid RIR databaseRIPE 672 100% 66
46.251.193.0/24 Valid RIR databaseRIPE 672 100% 66
46.251.194.0/24 Valid RIR databaseRIPE 672 100% 66
46.251.195.0/24 Valid RIR databaseRIPE 672 100% 66
46.251.196.0/24 Valid RIR databaseRIPE 672 100% 66
46.251.197.0/24 Valid RIR databaseRIPE 672 100% 66
46.251.198.0/24 Valid RIR databaseRIPE 672 100% 66
46.251.199.0/24 Valid RIR databaseRIPE 672 100% 66
46.251.200.0/24 Valid RIR databaseRIPE 672 100% 66
46.251.201.0/24 Valid RIR databaseRIPE 672 100% 66
46.251.202.0/24 Valid RIR databaseRIPE 672 100% 66
46.251.203.0/24 Valid RIR databaseRIPE 672 100% 66
46.251.204.0/24 Valid RIR databaseRIPE 672 100% 66
46.251.205.0/24 Valid RIR databaseRIPE 672 100% 66
46.251.206.0/24 Valid RIR databaseRIPE 672 100% 66
46.251.207.0/24 Valid RIR databaseRIPE 672 100% 66
46.251.208.0/24 Valid RIR databaseRIPE 672 100% 66
46.251.209.0/24 Valid RIR databaseRIPE 672 100% 66
46.251.210.0/24 Valid RIR databaseRIPE 672 100% 66
46.251.211.0/24 Valid RIR databaseRIPE 672 100% 66
46.251.212.0/24 Valid RIR databaseRIPE 672 100% 66
46.251.213.0/24 Valid RIR databaseRIPE 672 100% 66
46.251.214.0/24 Valid RIR databaseRIPE 672 100% 66
46.251.215.0/24 Valid RIR databaseRIPE 672 100% 66
46.251.216.0/24 Valid RIR databaseRIPE 672 100% 66
46.251.217.0/24 Valid RIR databaseRIPE 672 100% 66
46.251.218.0/24 Valid RIR databaseRIPE 672 100% 66
46.251.221.0/24 Valid RIR databaseRIPE 672 100% 66

AS-SET

AS50223's PeeringDB record names no 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.

  • Route object: none1
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
Route object: none109.71.228.0/24No route object for it. A route object for 109.71.228.0/22 with origin AS50223 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50223 in the RIR database for the space.673 of 673

Route objects not announced

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

46.251.194.0/23RIPEInvalid: maxLength
46.251.196.0/22RIPEValid
46.251.200.0/22RIPEValid
46.251.216.0/23RIPEInvalid: maxLength
46.251.219.0/24RIPEInvalid: maxLength
109.71.224.0/22RIPEInvalid: maxLength
109.71.228.0/22RIPEInvalid: maxLength
185.48.137.0/24RIPEInvalid: maxLength
185.48.138.0/24RIPEInvalid: maxLength
2a04:b340::/29RIPENo 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.