bgpreport

Network · data from 2026-11-12

AS198430 vSolutions

Registry name: VBIZ-PL vSolutions Pawel Gruszecki, PL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS198430, 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.
2a11:1bc1:da00::/44 No ROA None 2 0%low visibility 2
46.174.168.0/22 Valid Other IRR onlyRADB 673 100% 66
46.174.168.0/21 Valid RIR databaseRIPE 673 100% 66
194.28.228.0/22 Valid RIR databaseRIPE 673 100% 66
46.174.170.0/23 Valid RIR databaseRIPE 671 100% 68
91.234.252.0/23 Valid RIR databaseRIPE 671 100% 68
91.237.172.0/23 Valid RIR databaseRIPE 671 100% 68
91.239.28.0/22 Valid RIR databaseRIPE 671 100% 68
91.246.168.0/22 Valid RIR databaseRIPE 671 100% 68
193.150.50.0/23 Valid RIR databaseRIPE 671 100% 68
2a11:1bc1:1000::/46 Valid RIR databaseRIPE 634 100% 67
2a11:1bc1:2a00::/46 Valid RIR databaseRIPE 634 100% 67
2a11:1bc1:da00::/46 Valid RIR databaseRIPE 634 100% 67
2a11:1bc1:1100::/46 Valid RIR databaseRIPE 633 100% 67
2a11:1bc1:1b00::/46 Valid RIR databaseRIPE 633 100% 67
46.174.168.0/23 Valid RIR databaseRIPE 116 17% 40
46.174.172.0/23 Valid RIR databaseRIPE 116 17% 40
194.28.228.0/23 Valid RIR databaseRIPE 116 17% 40
194.28.230.0/23 Valid RIR databaseRIPE 116 17% 40
2a11:1bc1:2a00::/47 Valid RIR databaseRIPE 68 11% 31
2a11:1bc1:da00::/47 Valid RIR databaseRIPE 68 11% 31
2a11:1bc1:1b00::/47 Valid RIR databaseRIPE 67 11% 30
2a11:1bc1:1100::/47 Valid RIR databaseRIPE 61 10%low visibility 31
2a11:1bc1:1000::/47 Valid RIR databaseRIPE 55 9%low visibility 28
46.174.168.0/24 Valid RIR databaseRIPE 22 3%low visibility 23
194.28.228.0/24 Valid RIR databaseRIPE 22 3%low visibility 23
194.28.229.0/24 Valid RIR databaseRIPE 22 3%low visibility 23
194.28.230.0/24 Valid RIR databaseRIPE 22 3%low visibility 23
194.28.231.0/24 Valid RIR databaseRADB, RIPE 22 3%low visibility 23
2a11:1bc1:1000::/48 Valid RIR databaseRIPE 14 2%low visibility 14
2a11:1bc1:1100::/48 Valid RIR databaseRIPE 14 2%low visibility 14
2a11:1bc1:1b00::/48 Valid RIR databaseRIPE 14 2%low visibility 14
2a11:1bc1:2a00::/48 Valid RIR databaseRIPE 14 2%low visibility 14
2a11:1bc1:da00::/48 Valid RIR databaseRIPE 14 2%low visibility 14
2001:678:d40::/48 Valid RIR databaseRADB, RIPE 1 0%low visibility 1

AS-SET

AS198430'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 17 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
ROA: none2a11:1bc1:da00::/44No ROA covers it. Add a ROA for AS198430, maxLength 44.2 of 636
Route object: none2a11:1bc1:da00::/44No route object for it. Add a route object with origin AS198430 in the RIR database for the space.2 of 636
Route object: RIR46.174.168.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

46.174.169.0/24RIPEValid
46.174.170.0/24RIPEValid
46.174.171.0/24RIPEValid
46.174.172.0/22RIPEValid
46.174.174.0/23RIPEValid
91.234.252.0/24RIPEValid
91.234.253.0/24RIPEValid
91.237.172.0/24RIPEValid
91.237.173.0/24RIPEValid
91.239.28.0/23RIPEValid
91.239.30.0/23RIPEValid
193.150.50.0/24RIPEValid
193.150.51.0/24RIPEValid
2a10:f781:10:22b6::/64RIPENo 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.