bgpreport

Network · data from 2026-11-12

AS25206 UNACS-AS-BG Unacs - Yuri Jordanov Ltd.

Registry name: UNACS-AS-BG Unacs - Yuri Jordanov Ltd., BG · not in PeeringDB

56IPv4 routes 85.7% RPKI valid · 39.3% with a route object
0IPv6 routes
3RPKI invalid 0 origin · 3 maxLength
5No ROA 34 with no route object for this origin
19Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS25206, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS25206, 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.

83.97.64.87/32 Invalid: maxLength Nonecovered by 83.97.64.0/21 3 0%low visibility 7
84.201.206.150/32 Invalid: maxLength Nonecovered by 84.201.192.0/20 3 0%low visibility 7
89.252.234.110/32 Invalid: maxLength Nonecovered by 89.252.234.0/24 3 0%low visibility 7
79.134.172.0/24 No ROA RIR databaseRIPE 673 100% 66
79.134.173.0/24 No ROA RIR databaseRIPE 673 100% 66
79.134.174.0/24 No ROA RIR databaseRIPE 673 100% 66
79.134.175.0/24 No ROA RIR databaseRIPE 673 100% 66
79.134.183.0/24 No ROA RIR databaseRIPE 673 100% 66
83.97.65.0/24 Valid Nonecovered by 83.97.64.0/21 673 100% 66
83.97.66.0/24 Valid Nonecovered by 83.97.64.0/21 673 100% 66
83.97.67.0/24 Valid Nonecovered by 83.97.64.0/21 673 100% 66
89.252.216.0/24 Valid Nonecovered by 89.252.216.0/22 673 100% 66
89.252.217.0/24 Valid Nonecovered by 89.252.216.0/22 673 100% 66
89.252.218.0/24 Valid Nonecovered by 89.252.216.0/22 673 100% 66
89.252.219.0/24 Valid Nonecovered by 89.252.216.0/22 673 100% 66
83.97.64.0/24 Valid Nonecovered by 83.97.64.0/21 672 100% 66
83.97.68.0/24 Valid Nonecovered by 83.97.64.0/21 95 14% 33
83.97.69.0/24 Valid Nonecovered by 83.97.64.0/21 95 14% 33
89.252.248.0/24 Valid Nonecovered by 89.252.248.0/22 95 14% 33
89.252.249.0/24 Valid Nonecovered by 89.252.248.0/22 95 14% 33
89.252.251.0/24 Valid Nonecovered by 89.252.248.0/22 95 14% 33
83.97.70.0/24 Valid Nonecovered by 83.97.64.0/21 94 14% 33
83.97.71.0/24 Valid Nonecovered by 83.97.64.0/21 94 14% 33
84.201.197.0/24 Valid Nonecovered by 84.201.192.0/20 66 10%low visibility 31
84.201.198.0/24 Valid Nonecovered by 84.201.192.0/20 66 10%low visibility 31
84.201.199.0/24 Valid Nonecovered by 84.201.192.0/20 66 10%low visibility 31
84.201.203.0/24 Valid Nonecovered by 84.201.192.0/20 66 10%low visibility 31
84.201.205.0/24 Valid Nonecovered by 84.201.192.0/20 66 10%low visibility 31
84.201.206.0/24 Valid Nonecovered by 84.201.192.0/20 66 10%low visibility 31
84.201.207.0/24 Valid Nonecovered by 84.201.192.0/20 66 10%low visibility 31
84.201.193.0/24 Valid Nonecovered by 84.201.192.0/20 7 1%low visibility 5
84.201.194.0/24 Valid Nonecovered by 84.201.192.0/20 7 1%low visibility 5
84.201.195.0/24 Valid Nonecovered by 84.201.192.0/20 7 1%low visibility 5
84.201.196.0/24 Valid Nonecovered by 84.201.192.0/20 7 1%low visibility 5
84.201.200.0/24 Valid Nonecovered by 84.201.192.0/20 7 1%low visibility 5
84.201.201.0/24 Valid Nonecovered by 84.201.192.0/20 7 1%low visibility 5
84.201.202.0/24 Valid Nonecovered by 84.201.192.0/20 7 1%low visibility 5
84.201.204.0/24 Valid Nonecovered by 84.201.192.0/20 7 1%low visibility 5
89.252.250.0/24 Valid Nonecovered by 89.252.248.0/22 5 1%low visibility 4
83.97.64.0/21 Valid RIR databaseRIPE 673 100% 66
84.201.192.0/20 Valid RIR databaseRIPE 673 100% 66
89.252.216.0/22 Valid RIR databaseRIPE 673 100% 66
89.252.232.0/21 Valid RIR databaseRIPE 673 100% 66
89.252.232.0/24 Valid RIR databaseRIPE 673 100% 66
89.252.233.0/24 Valid RIR databaseRIPE 673 100% 66
89.252.234.0/24 Valid RIR databaseRIPE 673 100% 66
89.252.235.0/24 Valid RIR databaseRIPE 673 100% 66
89.252.236.0/24 Valid RIR databaseRIPE 673 100% 66
89.252.237.0/24 Valid RIR databaseRIPE 673 100% 66
89.252.238.0/24 Valid RIR databaseRIPE 673 100% 66
89.252.239.0/24 Valid RIR databaseRIPE 673 100% 66
89.252.248.0/22 Valid RIR databaseRIPE 673 100% 66
95.158.168.0/24 Valid RIR databaseRIPE 673 100% 66
185.230.244.0/24 Valid RIR databaseRIPE 673 100% 66
46.35.170.0/24 Valid RIR databaseRIPE 672 100% 66
46.35.171.0/24 Valid RIR databaseRIPE 672 100% 66

AS-SET

AS25206 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 42 are in fix.csv.

  • ROA: maxLength3
  • ROA: none5
  • Route object: none34
ChangePrefix or setDetailFull-table peers
ROA: maxLength83.97.64.87/32ROA 83.97.64.0/21 AS25206 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 83.97.64.87/32.3 of 673
Route object: none83.97.64.87/32No route object for it. A route object for 83.97.64.0/21 with origin AS25206 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS25206 in the RIR database for the space.3 of 673
ROA: maxLength84.201.206.150/32ROA 84.201.192.0/20 AS25206 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 84.201.206.150/32.3 of 673
Route object: none84.201.206.150/32No route object for it. A route object for 84.201.192.0/20 with origin AS25206 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS25206 in the RIR database for the space.3 of 673
ROA: maxLength89.252.234.110/32ROA 89.252.232.0/21 AS25206 has maxLength 21; ROA 89.252.232.0/22 AS25206 has maxLength 22; ROA 89.252.234.0/24 AS25206 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 89.252.234.110/32.3 of 673
Route object: none89.252.234.110/32No route object for it. A route object for 89.252.234.0/24 with origin AS25206 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS25206 in the RIR database for the space.3 of 673
ROA: none79.134.172.0/24No ROA covers it. Add a ROA for AS25206, maxLength 24.673 of 673
ROA: none79.134.173.0/24No ROA covers it. Add a ROA for AS25206, maxLength 24.673 of 673
ROA: none79.134.174.0/24No ROA covers it. Add a ROA for AS25206, maxLength 24.673 of 673
ROA: none79.134.175.0/24No ROA covers it. Add a ROA for AS25206, maxLength 24.673 of 673
ROA: none79.134.183.0/24No ROA covers it. Add a ROA for AS25206, maxLength 24.673 of 673
Route object: none83.97.65.0/24No route object for it. A route object for 83.97.64.0/21 with origin AS25206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25206 in the RIR database for the space.673 of 673
Route object: none83.97.66.0/24No route object for it. A route object for 83.97.64.0/21 with origin AS25206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25206 in the RIR database for the space.673 of 673
Route object: none83.97.67.0/24No route object for it. A route object for 83.97.64.0/21 with origin AS25206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25206 in the RIR database for the space.673 of 673
Route object: none89.252.216.0/24No route object for it. A route object for 89.252.216.0/22 with origin AS25206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25206 in the RIR database for the space.673 of 673
Route object: none89.252.217.0/24No route object for it. A route object for 89.252.216.0/22 with origin AS25206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25206 in the RIR database for the space.673 of 673
Route object: none89.252.218.0/24No route object for it. A route object for 89.252.216.0/22 with origin AS25206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25206 in the RIR database for the space.673 of 673
Route object: none89.252.219.0/24No route object for it. A route object for 89.252.216.0/22 with origin AS25206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25206 in the RIR database for the space.673 of 673
Route object: none83.97.64.0/24No route object for it. A route object for 83.97.64.0/21 with origin AS25206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25206 in the RIR database for the space.672 of 673
Route object: none83.97.68.0/24No route object for it. A route object for 83.97.64.0/21 with origin AS25206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25206 in the RIR database for the space.95 of 673
Route object: none83.97.69.0/24No route object for it. A route object for 83.97.64.0/21 with origin AS25206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25206 in the RIR database for the space.95 of 673
Route object: none89.252.248.0/24No route object for it. A route object for 89.252.248.0/22 with origin AS25206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25206 in the RIR database for the space.95 of 673
Route object: none89.252.249.0/24No route object for it. A route object for 89.252.248.0/22 with origin AS25206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25206 in the RIR database for the space.95 of 673
Route object: none89.252.251.0/24No route object for it. A route object for 89.252.248.0/22 with origin AS25206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25206 in the RIR database for the space.95 of 673
Route object: none83.97.70.0/24No route object for it. A route object for 83.97.64.0/21 with origin AS25206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25206 in the RIR database for the space.94 of 673
Route object: none83.97.71.0/24No route object for it. A route object for 83.97.64.0/21 with origin AS25206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25206 in the RIR database for the space.94 of 673
Route object: none84.201.197.0/24No route object for it. A route object for 84.201.192.0/20 with origin AS25206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25206 in the RIR database for the space.66 of 673
Route object: none84.201.198.0/24No route object for it. A route object for 84.201.192.0/20 with origin AS25206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25206 in the RIR database for the space.66 of 673
Route object: none84.201.199.0/24No route object for it. A route object for 84.201.192.0/20 with origin AS25206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25206 in the RIR database for the space.66 of 673
Route object: none84.201.203.0/24No route object for it. A route object for 84.201.192.0/20 with origin AS25206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25206 in the RIR database for the space.66 of 673
Route object: none84.201.205.0/24No route object for it. A route object for 84.201.192.0/20 with origin AS25206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25206 in the RIR database for the space.66 of 673
Route object: none84.201.206.0/24No route object for it. A route object for 84.201.192.0/20 with origin AS25206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25206 in the RIR database for the space.66 of 673
Route object: none84.201.207.0/24No route object for it. A route object for 84.201.192.0/20 with origin AS25206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25206 in the RIR database for the space.66 of 673
Route object: none84.201.193.0/24No route object for it. A route object for 84.201.192.0/20 with origin AS25206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25206 in the RIR database for the space.7 of 673
Route object: none84.201.194.0/24No route object for it. A route object for 84.201.192.0/20 with origin AS25206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25206 in the RIR database for the space.7 of 673
Route object: none84.201.195.0/24No route object for it. A route object for 84.201.192.0/20 with origin AS25206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25206 in the RIR database for the space.7 of 673
Route object: none84.201.196.0/24No route object for it. A route object for 84.201.192.0/20 with origin AS25206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25206 in the RIR database for the space.7 of 673
Route object: none84.201.200.0/24No route object for it. A route object for 84.201.192.0/20 with origin AS25206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25206 in the RIR database for the space.7 of 673
Route object: none84.201.201.0/24No route object for it. A route object for 84.201.192.0/20 with origin AS25206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25206 in the RIR database for the space.7 of 673
Route object: none84.201.202.0/24No route object for it. A route object for 84.201.192.0/20 with origin AS25206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25206 in the RIR database for the space.7 of 673
Route object: none84.201.204.0/24No route object for it. A route object for 84.201.192.0/20 with origin AS25206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25206 in the RIR database for the space.7 of 673
Route object: none89.252.250.0/24No route object for it. A route object for 89.252.248.0/22 with origin AS25206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25206 in the RIR database for the space.5 of 673

Route objects not announced

Every route object with origin AS25206 is announced.

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.