bgpreport

Network · data from 2026-11-12

AS30860 Virtual Systems AS30860

Registry name: YURTEH-AS Virtual Systems LLC, UA · PeeringDB

92IPv4 routes 88.0% RPKI valid · 88.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
7RPKI invalid 7 origin · 0 maxLength
4No ROA 11 with no route object for this origin
42Low visibility seen by under 10% of full-table peers
46Route objects not announced registered with origin AS30860, seen from no peer

Announced routes

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

185.34.42.0/24 Invalid: origin Other origin only 2 0%low visibility 2
185.174.63.0/24 Invalid: origin Other origin only 2 0%low visibility 2
191.96.69.0/24 Invalid: origin Other origin only 2 0%low visibility 2
191.96.171.0/24 Invalid: origin Other origin only 2 0%low visibility 2
191.96.173.0/24 Invalid: origin Other origin only 2 0%low visibility 2
202.51.57.0/24 Invalid: origin Other origin only 2 0%low visibility 2
202.51.58.0/23 Invalid: origin Other origin only 2 0%low visibility 2
5.252.154.0/24 No ROA None 2 0%low visibility 2
149.18.45.0/24 No ROA Other IRR onlyRADB 671 100% 68
154.6.163.0/24 No ROA Other IRR onlyRADB 667 99% 67
185.255.120.0/24 No ROA RIR databaseRIPE 671 100% 68
152.89.62.0/24 Valid Nonecovered by 152.89.60.0/22 671 100% 68
152.89.61.0/24 Valid Nonecovered by 152.89.60.0/22 667 99% 68
152.89.63.0/24 Valid Nonecovered by 152.89.60.0/22 667 99% 68
31.42.184.0/23 Valid RIR databaseRIPE 671 100% 68
45.134.172.0/24 Valid RIR databaseRIPE 671 100% 68
62.182.80.0/23 Valid RIR databaseRIPE 671 100% 68
62.182.82.0/23 Valid RIR databaseRIPE 671 100% 68
62.182.85.0/24 Valid RIR databaseRIPE 671 100% 68
62.182.86.0/24 Valid RIR databaseRIPE 671 100% 68
91.234.6.0/23 Valid RIR databaseRIPE 671 100% 68
91.235.142.0/24 Valid RIR databaseRIPE 671 100% 68
95.214.234.0/23 Valid RIR databaseRIPE 671 100% 68
176.119.29.0/24 Valid RIR databaseRIPE 671 100% 68
185.66.88.0/23 Valid RIR databaseRIPE 671 100% 68
185.254.196.0/23 Valid RIR databaseRIPE 671 100% 68
194.42.205.0/24 Valid RIR databaseRIPE 671 100% 68
195.66.214.0/23 Valid RIR databaseRIPE 671 100% 68
62.182.87.0/24 Valid RIR databaseRIPE 670 100% 68
91.234.4.0/24 Valid RIR databaseRIPE 670 100% 68
95.214.233.0/24 Valid RIR databaseRIPE 670 100% 68
152.89.60.0/24 Valid RIR databaseRIPE 670 100% 68
176.119.24.0/24 Valid RIR databaseRIPE 670 100% 68
176.119.25.0/24 Valid RIR databaseRIPE 670 100% 68
176.119.26.0/24 Valid RIR databaseRIPE 670 100% 68
176.119.27.0/24 Valid RIR databaseRIPE 670 100% 68
193.23.181.0/24 Valid RIR databaseRIPE 670 100% 68
31.42.186.0/24 Valid RIR databaseRIPE 667 99% 68
31.42.187.0/24 Valid RIR databaseRIPE 667 99% 68
45.11.58.0/24 Valid RIR databaseRIPE 667 99% 68
45.12.1.0/24 Valid RIR databaseRIPE 667 99% 68
45.12.2.0/24 Valid RIR databaseRIPE 667 99% 68
45.134.173.0/24 Valid RIR databaseRIPE 667 99% 68
62.182.84.0/24 Valid RIR databaseRIPE 667 99% 68
91.208.115.0/24 Valid RIR databaseRIPE 667 99% 68
95.214.232.0/24 Valid RIR databaseRIPE 667 99% 68
176.119.28.0/24 Valid RIR databaseRIPE 667 99% 68
185.66.90.0/24 Valid RIR databaseRIPE 667 99% 68
185.66.91.0/24 Valid RIR databaseRIPE 667 99% 68
185.254.198.0/24 Valid RIR databaseRIPE 667 99% 68
176.119.30.0/24 Valid RIR databaseRIPE 666 99% 68
2a09:2dc0::/29 Valid RIR databaseRIPE 634 100% 69
176.97.114.0/24 Valid RIR databaseRIPE 89 13% 37
85.137.57.0/24 Valid RIR databaseRIPE 88 13% 37
176.97.124.0/24 Valid RIR databaseRIPE 88 13% 37
85.137.49.0/24 Valid RIR databaseRIPE 86 13% 37
213.111.148.0/24 Valid RIR databaseRIPE 86 13% 37
213.111.149.0/24 Valid RIR databaseRIPE 86 13% 37
213.111.150.0/24 Valid RIR databaseRIPE 86 13% 37
23.27.138.0/24 Valid RIR databaseARIN 2 0%low visibility 2
23.27.184.0/24 Valid RIR databaseARIN 2 0%low visibility 2
46.203.159.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
46.203.186.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
66.63.180.0/24 Valid RIR databaseARIN 2 0%low visibility 2
82.21.219.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
82.21.223.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
82.21.224.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
82.22.210.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
82.22.217.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
82.22.220.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
82.22.227.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
82.23.209.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
82.24.224.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
82.24.225.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
82.25.216.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
82.25.228.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
82.25.237.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
82.25.238.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
82.26.221.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
82.26.239.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
82.27.214.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
82.27.233.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
82.27.235.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
82.27.239.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
82.29.225.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
82.29.226.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
82.29.229.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
82.29.230.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
91.234.5.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
91.235.143.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
92.112.135.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
92.112.138.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
188.95.89.0/24 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS30860: AS-VSYS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS30860 isn't in the set, or no route object for AS30860 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS30860 in itNot covered
AS-VSYS RIPElists itself further down1 member set in no database: AS-WINTELECOM 111271,440 Yes 8

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

  • ROA: origin7
  • ROA: none4
  • Route object: none11
  • Route object: RIR2
  • AS-SET: missing member1
  • Route object: not announced46
ChangePrefix or setDetailFull-table peers
ROA: origin185.34.42.0/24ROAs covering it name AS834, not AS30860. If AS30860 should announce it, add a ROA for AS30860.2 of 673
Route object: none185.34.42.0/24Route objects for it name AS834. Add a route object with origin AS30860 in the RIR database for the space.2 of 673
ROA: origin185.174.63.0/24ROAs covering it name AS834, not AS30860. If AS30860 should announce it, add a ROA for AS30860.2 of 673
Route object: none185.174.63.0/24Route objects for it name AS834. Add a route object with origin AS30860 in the RIR database for the space.2 of 673
ROA: origin191.96.69.0/24ROAs covering it name AS834, not AS30860. If AS30860 should announce it, add a ROA for AS30860.2 of 673
Route object: none191.96.69.0/24Route objects for it name AS834. Add a route object with origin AS30860 in the RIR database for the space.2 of 673
ROA: origin191.96.171.0/24ROAs covering it name AS834, not AS30860. If AS30860 should announce it, add a ROA for AS30860.2 of 673
Route object: none191.96.171.0/24Route objects for it name AS834. Add a route object with origin AS30860 in the RIR database for the space.2 of 673
ROA: origin191.96.173.0/24ROAs covering it name AS834, not AS30860. If AS30860 should announce it, add a ROA for AS30860.2 of 673
Route object: none191.96.173.0/24Route objects for it name AS834. Add a route object with origin AS30860 in the RIR database for the space.2 of 673
ROA: origin202.51.57.0/24ROAs covering it name AS141898, not AS30860. If AS30860 should announce it, add a ROA for AS30860.2 of 673
Route object: none202.51.57.0/24Route objects for it name AS38509. Add a route object with origin AS30860 in the RIR database for the space.2 of 673
ROA: origin202.51.58.0/23ROAs covering it name AS141898, not AS30860. If AS30860 should announce it, add a ROA for AS30860.2 of 673
Route object: none202.51.58.0/23Route objects for it name AS38509, AS133809. Add a route object with origin AS30860 in the RIR database for the space.2 of 673
ROA: none5.252.154.0/24No ROA covers it. Add a ROA for AS30860, maxLength 24.2 of 673
Route object: none5.252.154.0/24No route object for it. Add a route object with origin AS30860 in the RIR database for the space.2 of 673
ROA: none149.18.45.0/24No ROA covers it. Add a ROA for AS30860, maxLength 24.671 of 673
Route object: RIR149.18.45.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none154.6.163.0/24No ROA covers it. Add a ROA for AS30860, maxLength 24.667 of 673
Route object: RIR154.6.163.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none185.255.120.0/24No ROA covers it. Add a ROA for AS30860, maxLength 24.671 of 673
Route object: none152.89.62.0/24No route object for it. A route object for 152.89.60.0/22 with origin AS30860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30860 in the RIR database for the space.671 of 673
Route object: none152.89.61.0/24No route object for it. A route object for 152.89.60.0/22 with origin AS30860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30860 in the RIR database for the space.667 of 673
Route object: none152.89.63.0/24No route object for it. A route object for 152.89.60.0/22 with origin AS30860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30860 in the RIR database for the space.667 of 673
AS-SET: missing memberAS-VSYSAS-VSYS (RIPE) lists AS-WINTELECOM; no IRR database read has it.

Route objects not announced

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

31.42.184.0/24RIPEInvalid: maxLength
31.42.185.0/24RIPEInvalid: maxLength
45.11.57.0/24RIPEValid
45.12.0.0/22RIPEValid
45.12.0.0/24RIPEValid
45.12.3.0/24RIPEValid
45.134.172.0/22RIPEValid
62.182.80.0/21RIPEInvalid: origin
82.21.236.0/24RADB, RIPEValid
82.22.216.0/24RADB, RIPEValid
82.24.210.0/24RADB, RIPEValid
82.24.234.0/24RADB, RIPEValid
82.26.226.0/24RADB, RIPEValid
82.29.221.0/24RADB, RIPEValid
82.158.197.0/24RIPEValid
91.213.175.0/24RIPEInvalid: origin
91.224.10.0/24RIPENo ROA
91.230.121.0/24RIPEValid
91.235.142.0/23RIPEValid
91.237.250.0/24RIPEInvalid: origin
95.214.232.0/22RIPENo ROA
138.226.248.0/23RIPENo ROA
152.89.60.0/22RIPEInvalid: origin
176.119.24.0/21RIPEInvalid: origin
176.119.26.0/23RIPEValid
176.119.31.0/24RIPEValid
185.66.88.0/22RIPEInvalid: origin
194.42.204.0/22RIPEValid
194.42.204.0/24RIPEValid
195.66.210.0/24RIPEValid
212.90.164.224/29RIPEInvalid: origin
2001:470:174::/48ARINValid
2001:470:23d::/48ARINValid
2001:470:2a1::/48ARINValid
2001:470:2b4::/48ARINValid
2001:470:38e::/48ARINValid
2001:470:427::/48ARINValid
2001:470:43a::/48ARINValid
2001:470:44c::/48ARINValid
2001:470:4bd::/48ARINValid
2001:470:542::/48ARINValid
2001:470:647::/48ARINValid
2a09:2dc1::/32RIPEValid
2a0f:9400:20::/48RIPENo ROA
2a0f:9400:21::/48RIPENo ROA
2a0f:9400:22::/48RIPENo 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.