bgpreport

Network · data from 2026-11-12

AS59504 vpsville-AS LLC Vpsville

Registry name: vpsville-AS LLC Vpsville, RU · not in PeeringDB

51IPv4 routes 92.2% RPKI valid · 100.0% with a route object
13IPv6 routes 76.9% RPKI valid · 92.3% with a route object
0RPKI invalid 0 origin · 0 maxLength
7No ROA 1 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
77Route objects not announced registered with origin AS59504, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS59504, 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.
2a0d:e4c4::/32 No ROA None 462 73% 65
45.139.184.0/22 No ROA RIR databaseRIPE 671 100% 68
45.139.186.0/23 No ROA RIR databaseRIPE 671 100% 68
185.42.27.0/24 No ROA RIR databaseRIPE 671 100% 68
194.53.175.0/24 No ROA RIR databaseRIPE 671 100% 68
2a07:14c0:f000::/36 No ROA RIR databaseRIPE 633 100% 67
2a0c:5247:5000::/36 No ROA RIR databaseRIPE 1 0%low visibility 1
45.142.208.0/24 Valid RIR databaseRIPE 671 100% 68
45.142.209.0/24 Valid RIR databaseRIPE 671 100% 68
45.142.211.0/24 Valid RIR databaseRIPE 671 100% 68
45.151.136.0/24 Valid RIR databaseRIPE 671 100% 68
45.151.137.0/24 Valid RIR databaseRIPE 671 100% 68
80.76.40.0/24 Valid RIR databaseRIPE 671 100% 68
83.171.240.0/24 Valid RIR databaseRIPE 671 100% 68
83.171.241.0/24 Valid RIR databaseRIPE 671 100% 68
83.171.242.0/24 Valid RIR databaseRIPE 671 100% 68
84.54.37.0/24 Valid RIR databaseRIPE 671 100% 68
84.54.39.0/24 Valid RIR databaseRIPE 671 100% 68
95.215.110.0/23 Valid RIR databaseRIPE 671 100% 68
138.16.128.0/24 Valid RIR databaseRIPE 671 100% 68
138.16.129.0/24 Valid RIR databaseRIPE 671 100% 68
138.16.130.0/24 Valid RIR databaseRIPE 671 100% 68
185.42.24.0/24 Valid RIR databaseRIPE 671 100% 68
185.42.26.0/24 Valid RIR databaseRIPE 671 100% 68
185.118.64.0/24 Valid RIR databaseRIPE 671 100% 68
185.118.65.0/24 Valid RIR databaseRIPE 671 100% 68
185.118.66.0/24 Valid RIR databaseRIPE 671 100% 68
185.118.67.0/24 Valid RIR databaseRIPE 671 100% 68
185.156.176.0/24 Valid RIR databaseRIPE 671 100% 68
185.156.177.0/24 Valid RIR databaseRIPE 671 100% 68
185.156.178.0/24 Valid RIR databaseRIPE 671 100% 68
185.156.179.0/24 Valid RIR databaseRIPE 671 100% 68
185.177.113.0/24 Valid RIR databaseRIPE 671 100% 68
185.177.115.0/24 Valid RIR databaseRIPE 671 100% 68
185.197.72.0/24 Valid RIR databaseRIPE 671 100% 68
185.197.73.0/24 Valid RIR databaseRIPE 671 100% 68
185.220.32.0/24 Valid RIR databaseRIPE 671 100% 68
185.220.33.0/24 Valid RIR databaseRIPE 671 100% 68
185.220.34.0/24 Valid RIR databaseRIPE 671 100% 68
185.220.35.0/24 Valid RIR databaseRIPE 671 100% 68
185.230.140.0/23 Valid RIR databaseRIPE 671 100% 68
185.230.142.0/24 Valid RIR databaseRIPE 671 100% 68
185.246.116.0/24 Valid RIR databaseRIPE 671 100% 68
185.246.117.0/24 Valid RIR databaseRIPE 671 100% 68
185.246.119.0/24 Valid RIR databaseRIPE 671 100% 68
185.254.188.0/24 Valid RIR databaseRIPE 671 100% 68
185.254.189.0/24 Valid RIR databaseRIPE 671 100% 68
185.254.190.0/24 Valid RIR databaseRIPE 671 100% 68
193.38.232.0/23 Valid RIR databaseRIPE 671 100% 68
193.38.234.0/24 Valid RIR databaseRIPE 671 100% 68
193.150.70.0/24 Valid RIR databaseRIPE 671 100% 68
194.113.104.0/24 Valid RIR databaseRIPE 671 100% 68
194.113.107.0/24 Valid RIR databaseRIPE 671 100% 68
194.26.210.0/24 Valid RIR databaseRIPE 670 100% 68
2a05:fb41::/32 Valid RIR databaseRIPE 633 100% 67
2a05:fb42::/32 Valid RIR databaseRIPE 633 100% 67
2a07:14c0::/48 Valid RIR databaseRIPE 633 100% 67
2a07:14c0:1::/48 Valid RIR databaseRIPE 633 100% 67
2a07:14c0:3000::/36 Valid RIR databaseRIPE 633 100% 67
2a07:14c0:5000::/36 Valid RIR databaseRIPE 633 100% 67
2a07:14c0:6000::/36 Valid RIR databaseRIPE 633 100% 67
2a0c:5241::/32 Valid RIR databaseRIPE 633 100% 67
2a0d:60c0::/32 Valid RIR databaseRIPE 633 100% 67
2a0a:4785::/32 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

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

  • ROA: none7
  • Route object: none1
  • Route object: not announced77
ChangePrefix or setDetailFull-table peers
ROA: none2a0d:e4c4::/32No ROA covers it. Add a ROA for AS59504, maxLength 32.462 of 636
Route object: none2a0d:e4c4::/32No route object for it. Add a route object with origin AS59504 in the RIR database for the space.462 of 636
ROA: none45.139.184.0/22No ROA covers it. Add a ROA for AS59504, maxLength 22.671 of 673
ROA: none45.139.186.0/23No ROA covers it. Add a ROA for AS59504, maxLength 23.671 of 673
ROA: none185.42.27.0/24No ROA covers it. Add a ROA for AS59504, maxLength 24.671 of 673
ROA: none194.53.175.0/24No ROA covers it. Add a ROA for AS59504, maxLength 24.671 of 673
ROA: none2a07:14c0:f000::/36No ROA covers it. Add a ROA for AS59504, maxLength 36.633 of 636
ROA: none2a0c:5247:5000::/36No ROA covers it. Add a ROA for AS59504, maxLength 36.1 of 636

Route objects not announced

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

45.151.136.0/22RIPEValid
83.171.243.0/24RIPEValid
185.118.64.0/22RIPEValid
185.118.66.0/23RIPEValid
185.156.176.0/22RIPEValid
185.156.178.0/23RIPEValid
185.246.118.0/23RIPENo ROA
185.254.190.0/23RIPENo ROA
193.38.232.0/24RIPEInvalid: maxLength
193.38.233.0/24RIPEInvalid: maxLength
2a05:fb40::/32RIPENo ROA
2a05:fb43::/32RIPENo ROA
2a05:fb44::/32RIPEValid
2a05:fb45::/32RIPEValid
2a05:fb46::/32RIPENo ROA
2a05:fb47::/32RIPENo ROA
2a07:14c0:100::/40RIPENo ROA
2a07:14c0:1000::/36RIPEValid
2a07:14c0:2000::/36RIPENo ROA
2a07:14c0:4000::/36RIPEValid
2a07:14c0:7000::/36RIPENo ROA
2a07:14c0:8000::/36RIPENo ROA
2a07:14c0:9000::/36RIPENo ROA
2a07:14c0:a000::/36RIPENo ROA
2a07:14c0:b000::/36RIPENo ROA
2a07:14c0:c000::/36RIPENo ROA
2a07:14c0:d000::/36RIPEValid
2a07:14c0:e000::/36RIPENo ROA
2a07:14c1::/32RIPEValid
2a07:14c2::/32RIPEValid
2a07:14c3::/32RIPENo ROA
2a07:14c4::/32RIPENo ROA
2a07:14c5::/32RIPENo ROA
2a07:14c6::/32RIPEValid
2a07:14c7::/32RIPEValid
2a0a:4780::/32RIPEValid
2a0a:4781::/32RIPEValid
2a0a:4782::/32RIPEValid
2a0a:4787::/32RIPENo ROA
2a0c:2107::/32RIPENo ROA
2a0c:5240::/32RIPENo ROA
2a0c:5242::/32RIPENo ROA
2a0c:5244::/32RIPENo ROA
2a0c:5245::/32RIPEValid
2a0c:5246::/32RIPENo ROA
2a0c:5247::/36RIPENo ROA
2a0c:5247:1000::/36RIPENo ROA
2a0c:5247:2000::/36RIPENo ROA
2a0c:5247:3000::/36RIPENo ROA
2a0c:5247:4000::/36RIPENo ROA
2a0c:5247:6000::/36RIPENo ROA
2a0c:5247:7000::/36RIPEValid
2a0c:5247:8000::/36RIPENo ROA
2a0c:5247:9000::/36RIPENo ROA
2a0c:5247:a000::/36RIPENo ROA
2a0c:5247:b000::/36RIPENo ROA
2a0c:5247:c000::/36RIPEValid
2a0c:5247:d000::/36RIPEValid
2a0c:5247:e000::/36RIPEValid
2a0c:5247:f000::/36RIPEValid
2a0d:60c1::/32RIPEValid
2a0d:60c2::/32RIPENo ROA
2a0d:60c4::/32RIPENo ROA
2a0d:60c6::/32RIPENo ROA
2a0d:60c7::/32RIPENo ROA
2a0d:7740::/32RIPEValid
2a0d:7741::/32RIPENo ROA
2a0d:7742::/32RIPENo ROA
2a0d:7744::/32RIPENo ROA
2a0d:7745::/32RIPENo ROA
2a0d:7746::/32RIPENo ROA
2a0d:7747::/32RIPEValid
2a0d:e4c1::/32RIPENo ROA
2a0d:e4c2::/32RIPENo ROA
2a0d:e4c5::/32RIPENo ROA
2a0d:e4c6::/32RIPENo ROA
2a0d:e4c7::/32RIPENo 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.