bgpreport

Network · data from 2026-11-12

AS216334 LandVPS-AS New Hosting Technologies LLC

Registry name: LandVPS-AS New Hosting Technologies LLC, RU · not in PeeringDB

37IPv4 routes 83.8% RPKI valid · 83.8% with a route object
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
6RPKI invalid 6 origin · 0 maxLength
0No ROA 6 with no route object for this origin
5Low visibility seen by under 10% of full-table peers
16Route objects not announced registered with origin AS216334, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS216334, 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.
193.160.142.0/24 Invalid: origin Other origin only 125 19% 45
45.152.196.0/24 Invalid: origin None 2 0%low visibility 2
45.158.198.0/24 Invalid: origin Other origin only 2 0%low visibility 2
193.5.250.0/24 Invalid: origin None 2 0%low visibility 2
193.160.143.0/24 Invalid: origin Other origin only 0 0%low visibility 1
193.223.105.0/24 Invalid: origin Other origin only 0 0%low visibility 1
31.77.169.0/24 Valid RIR databaseRIPE 673 100% 66
89.125.28.0/24 Valid RIR databaseRIPE 673 100% 66
94.159.115.0/24 Valid RIR databaseRIPE 673 100% 66
94.159.116.0/24 Valid RIR databaseRIPE 673 100% 66
167.150.18.0/24 Valid RIR databaseRIPE 673 100% 66
185.80.91.0/24 Valid RIR databaseRIPE 673 100% 66
194.55.236.0/24 Valid RIR databaseRIPE 673 100% 66
194.55.238.0/24 Valid RIR databaseRIPE 673 100% 66
194.117.80.0/24 Valid RIR databaseRIPE 673 100% 66
77.105.131.0/24 Valid RIR databaseRIPE 672 100% 66
77.105.163.0/24 Valid RIR databaseRIPE 672 100% 66
109.107.161.0/24 Valid RIR databaseRIPE 672 100% 66
13.143.243.0/24 Valid RIR databaseRIPE 671 100% 68
13.143.244.0/24 Valid RIR databaseRIPE 671 100% 68
31.77.78.0/24 Valid RIR databaseRIPE 671 100% 68
31.77.173.0/24 Valid RIR databaseRIPE 671 100% 68
37.221.110.0/24 Valid RIR databaseRIPE 671 100% 68
45.154.246.0/24 Valid RIR databaseRIPE 671 100% 68
77.105.133.0/24 Valid RIR databaseRIPE 671 100% 68
77.105.144.0/24 Valid RIR databaseRIPE 671 100% 68
83.136.50.0/24 Valid RIR databaseRIPE 671 100% 68
89.125.29.0/24 Valid RIR databaseRIPE 671 100% 68
89.125.34.0/24 Valid RIR databaseRIPE 671 100% 68
91.193.43.0/24 Valid RIR databaseRIPE 671 100% 68
94.159.113.0/24 Valid RIR databaseRIPE 671 100% 68
94.159.117.0/24 Valid RIR databaseRIPE 671 100% 68
109.120.144.0/24 Valid RIR databaseRIPE 671 100% 68
194.55.237.0/24 Valid RIR databaseRIPE 671 100% 68
194.55.239.0/24 Valid RIR databaseRIPE 671 100% 68
212.22.90.0/24 Valid RIR databaseRIPE 671 100% 68
77.105.162.0/24 Valid RIR databaseRIPE 664 99% 68
2a00:f9a0::/32 Valid RIR databaseRIPE 636 100% 69
2a12:b3c0:1::/48 Valid RIR databaseRIPE 636 100% 69

AS-SET

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

  • ROA: origin6
  • Route object: none6
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
ROA: origin193.160.142.0/24ROAs covering it name AS218261, not AS216334. If AS216334 should announce it, add a ROA for AS216334.125 of 673
Route object: none193.160.142.0/24Route objects for it name AS218261. Add a route object with origin AS216334 in the RIR database for the space.125 of 673
ROA: origin45.152.196.0/24ROAs covering it name AS213334, not AS216334. If AS216334 should announce it, add a ROA for AS216334.2 of 673
Route object: none45.152.196.0/24No route object for it. Add a route object with origin AS216334 in the RIR database for the space.2 of 673
ROA: origin45.158.198.0/24ROAs covering it name AS218568, not AS216334. If AS216334 should announce it, add a ROA for AS216334.2 of 673
Route object: none45.158.198.0/24Route objects for it name AS218568. Add a route object with origin AS216334 in the RIR database for the space.2 of 673
ROA: origin193.5.250.0/24ROAs covering it name AS213334, not AS216334. If AS216334 should announce it, add a ROA for AS216334.2 of 673
Route object: none193.5.250.0/24No route object for it. Add a route object with origin AS216334 in the RIR database for the space.2 of 673
ROA: origin193.160.143.0/24ROAs covering it name AS218261, AS218568, not AS216334. If AS216334 should announce it, add a ROA for AS216334.0 of 673
Route object: none193.160.143.0/24Route objects for it name AS218568. Add a route object with origin AS216334 in the RIR database for the space.0 of 673
ROA: origin193.223.105.0/24ROAs covering it name AS218261, AS218568, not AS216334. If AS216334 should announce it, add a ROA for AS216334.0 of 673
Route object: none193.223.105.0/24Route objects for it name AS218568. Add a route object with origin AS216334 in the RIR database for the space.0 of 673

Route objects not announced

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

94.159.96.0/24RIPEValid
94.159.97.0/24RIPEValid
94.159.98.0/24RIPEValid
94.159.99.0/24RIPEValid
94.159.100.0/24RIPEValid
94.159.101.0/24RIPEValid
94.159.102.0/24RIPEValid
94.159.103.0/24RIPEValid
94.159.104.0/24RIPEValid
94.159.105.0/24RIPEValid
94.159.106.0/24RIPEValid
94.159.107.0/24RIPEValid
94.159.108.0/24RIPEValid
94.159.109.0/24RIPEValid
94.159.110.0/24RIPEValid
94.159.111.0/24RIPEValid

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.