bgpreport

Network · data from 2026-11-12

AS62217 Vinters

Registry name: VooServers Vinters IT Ltd, GB · PeeringDB

18IPv4 routes 83.3% RPKI valid · 94.4% with a route object
17IPv6 routes 58.8% RPKI valid · 88.2% with a route object
0RPKI invalid 0 origin · 0 maxLength
10No ROA 3 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
16Route objects not announced registered with origin AS62217, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS62217, 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.
2c0f:f7e8::/47 No ROA None 635 100% 67
204.10.120.0/22 No ROA Other IRR onlyRADB 668 99% 67
2605:45c0::/36 No ROA Other IRR onlyRADB 634 100% 67
2605:45c0:1000::/36 No ROA Other IRR onlyRADB 634 100% 67
2607:6980::/44 No ROA Other IRR onlyRADB 634 100% 67
2607:6980:10::/44 No ROA Other IRR onlyRADB 634 100% 67
185.157.48.0/24 No ROA RIR databaseRIPE 673 100% 67
195.60.164.0/23 No ROA RIR databaseRIPE 673 100% 67
2001:67c:2e68::/47 No ROA RIR databaseRIPE 633 100% 68
2a07:a340::/32 No ROA RIR databaseRIPE 633 100% 68
185.184.157.0/24 Valid Nonecovered by 185.184.156.0/22 669 99% 67
2a01:6c62::/32 Valid None 633 100% 68
82.22.33.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
91.212.182.0/24 Valid RIR databaseRIPE 673 100% 67
91.216.93.0/24 Valid RIR databaseRIPE 673 100% 67
91.220.127.0/24 Valid RIR databaseRIPE 673 100% 67
91.227.220.0/22 Valid RIR databaseRIPE 673 100% 67
185.43.108.0/22 Valid RIR databaseRIPE 673 100% 67
185.43.109.0/24 Valid RIR databaseRIPE 673 100% 67
185.43.111.0/24 Valid RIR databaseRIPE 673 100% 67
185.184.156.0/22 Valid RIR databaseRIPE 673 100% 67
185.184.156.0/24 Valid RIR databaseRIPE 673 100% 67
185.184.158.0/24 Valid RIR databaseRIPE 673 100% 67
185.184.159.0/24 Valid RIR databaseRIPE 673 100% 67
194.0.252.0/24 Valid RIR databaseRIPE 673 100% 67
185.43.108.0/24 Valid RIR databaseRIPE 669 99% 67
2a01:6c60:1000::/36 Valid RIR databaseRADB, RIPE 634 100% 67
2a01:6c60::/32 Valid RIR databaseRIPE 633 100% 68
2a01:6c61::/32 Valid RIR databaseRIPE 633 100% 68
2a01:6c63::/32 Valid RIR databaseRADB, RIPE 633 100% 68
2a04:a140::/32 Valid RIR databaseRIPE 633 100% 68
2a05:2d00::/32 Valid RIR databaseRIPE 633 100% 68
2a06:3e80::/32 Valid RIR databaseRIPE 633 100% 68
2a0b:3880::/32 Valid RIR databaseRIPE 633 100% 68
2a01:6c60:2000::/36 Valid RIR databaseRIPE 628 99% 67

AS-SET

AS62217'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 34 are in fix.csv.

  • ROA: none10
  • Route object: none3
  • Route object: RIR5
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
ROA: none2c0f:f7e8::/47No ROA covers it. Add a ROA for AS62217, maxLength 47.635 of 636
Route object: none2c0f:f7e8::/47No route object for it. Add a route object with origin AS62217 in the RIR database for the space.635 of 636
ROA: none204.10.120.0/22No ROA covers it. Add a ROA for AS62217, maxLength 22.668 of 673
Route object: RIR204.10.120.0/22Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none2605:45c0::/36No ROA covers it. Add a ROA for AS62217, maxLength 36.634 of 636
Route object: RIR2605:45c0::/36Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2605:45c0:1000::/36No ROA covers it. Add a ROA for AS62217, maxLength 36.634 of 636
Route object: RIR2605:45c0:1000::/36Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2607:6980::/44No ROA covers it. Add a ROA for AS62217, maxLength 44.634 of 636
Route object: RIR2607:6980::/44Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2607:6980:10::/44No ROA covers it. Add a ROA for AS62217, maxLength 44.634 of 636
Route object: RIR2607:6980:10::/44Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none185.157.48.0/24No ROA covers it. Add a ROA for AS62217, maxLength 24.673 of 673
ROA: none195.60.164.0/23No ROA covers it. Add a ROA for AS62217, maxLength 23.673 of 673
ROA: none2001:67c:2e68::/47No ROA covers it. Add a ROA for AS62217, maxLength 47.633 of 636
ROA: none2a07:a340::/32No ROA covers it. Add a ROA for AS62217, maxLength 32.633 of 636
Route object: none185.184.157.0/24No route object for it. A route object for 185.184.156.0/22 with origin AS62217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62217 in the RIR database for the space.669 of 673
Route object: none2a01:6c62::/32No route object for it. Add a route object with origin AS62217 in the RIR database for the space.633 of 636

Route objects not announced

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

45.58.62.0/24RADBNo ROA
91.228.0.0/22RIPENo ROA
91.238.214.0/23RIPENo ROA
104.128.230.0/24RADBNo ROA
104.128.230.11/32RADBNo ROA
104.128.234.0/24RADBNo ROA
185.43.108.0/23RIPEValid
185.43.110.0/23RIPEValid
185.43.110.0/24RIPEValid
185.184.167.0/24RADBNo ROA
216.189.148.0/24RADBNo ROA
2607:6980::/32RADBNo ROA
2a01:6c60:3::/48RIPEValid
2a01:6c60:4::/48RIPEValid
2a01:6c60:12::/48RIPEValid
2a01:6c60:2c::/48RIPEValid

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.