bgpreport

Network · data from 2026-11-12

AS208677 CLOUDRU-AS "Cloud Technologies" LLC trading as Cloud.ru

Registry name: CLOUDRU-AS "Cloud Technologies" LLC trading as Cloud.ru, RU · not in PeeringDB

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

Announced routes

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

45.132.176.0/22 Valid RIR databaseRIPE 673 100% 66
85.235.82.0/24 Valid RIR databaseRIPE 673 100% 66
131.222.134.0/24 Valid RIR databaseRIPE 673 100% 66
213.178.154.0/24 Valid RIR databaseRIPE 673 100% 66
45.151.30.0/23 Valid RIR databaseRIPE 672 100% 66
45.155.204.0/23 Valid RIR databaseRIPE 672 100% 66
62.233.43.0/24 Valid RIR databaseRIPE 672 100% 66
82.202.136.0/21 Valid RIR databaseRIPE 672 100% 66
82.202.156.0/22 Valid RIR databaseRIPE 672 100% 66
84.54.56.0/22 Valid RIR databaseRIPE 672 100% 66
85.208.85.0/24 Valid RIR databaseRIPE 672 100% 66
85.208.86.0/23 Valid RIR databaseRIPE 672 100% 66
85.209.150.0/23 Valid RIR databaseRIPE 672 100% 66
85.235.83.0/24 Valid RIR databaseRIPE 672 100% 66
87.242.100.0/22 Valid RIR databaseRIPE 672 100% 66
88.218.66.0/23 Valid RIR databaseRIPE 672 100% 66
91.224.86.0/23 Valid RIR databaseRIPE 672 100% 66
95.174.88.0/21 Valid RIR databaseRIPE 672 100% 66
152.89.196.0/24 Valid RIR databaseRIPE 672 100% 66
168.113.252.0/22 Valid RIR databaseRIPE 672 100% 66
168.222.176.0/24 Valid RIR databaseRIPE 672 100% 66
168.222.179.0/24 Valid RIR databaseRIPE 672 100% 66
176.108.240.0/20 Valid RIR databaseRIPE 672 100% 66
176.109.96.0/24 Valid RIR databaseRIPE 672 100% 66
176.123.160.0/21 Valid RIR databaseRIPE 672 100% 66
185.234.11.0/24 Valid RIR databaseRIPE 672 100% 66
185.241.57.0/24 Valid RIR databaseRIPE 672 100% 66
188.72.96.0/24 Valid RIR databaseRIPE 672 100% 66
192.144.12.0/22 Valid RIR databaseRIPE 672 100% 66
193.42.116.0/23 Valid RIR databaseRIPE 672 100% 66
194.5.92.0/23 Valid RIR databaseRIPE 672 100% 66
194.50.72.0/24 Valid RIR databaseRIPE 672 100% 66
194.113.34.0/23 Valid RIR databaseRIPE 672 100% 66
195.128.152.0/24 Valid RIR databaseRIPE 672 100% 67
213.171.24.0/21 Valid RIR databaseRIPE 672 100% 66
37.18.22.0/24 Valid RIR databaseRIPE 671 100% 66
37.18.102.0/24 Valid RIR databaseRIPE 671 100% 66
37.44.198.0/24 Valid RIR databaseRIPE 671 100% 66
46.16.36.0/24 Valid RIR databaseRIPE 671 100% 66
46.243.226.0/23 Valid RIR databaseRIPE 671 100% 66
46.253.132.0/24 Valid RIR databaseRIPE 671 100% 66
87.242.88.0/21 Valid RIR databaseRIPE 671 100% 66
89.232.160.0/21 Valid RIR databaseRIPE 671 100% 66
131.222.134.0/23 Valid RIR databaseRIPE 671 100% 66
178.170.196.0/23 Valid RIR databaseRIPE 671 100% 66
178.170.242.0/24 Valid RIR databaseRIPE 671 100% 66
188.72.106.0/23 Valid RIR databaseRIPE 671 100% 66
188.72.118.0/24 Valid RIR databaseRIPE 671 100% 66
31.40.248.0/23 Valid RIR databaseRIPE 670 100% 66
37.18.8.0/23 Valid RIR databaseRIPE 670 100% 66
37.18.72.0/23 Valid RIR databaseRIPE 670 100% 66
37.18.100.0/23 Valid RIR databaseRIPE 670 100% 66
37.18.108.0/22 Valid RIR databaseRIPE 670 100% 66
37.18.112.0/23 Valid RIR databaseRIPE 670 100% 66
37.18.116.0/22 Valid RIR databaseRIPE 670 100% 66
37.18.120.0/23 Valid RIR databaseRIPE 670 100% 66
37.18.122.0/24 Valid RIR databaseRIPE 670 100% 66
37.44.196.0/23 Valid RIR databaseRIPE 670 100% 66
37.230.180.0/23 Valid RIR databaseRIPE 670 100% 66
37.230.184.0/23 Valid RIR databaseRIPE 670 100% 66
37.230.192.0/21 Valid RIR databaseRIPE 670 100% 66
45.9.24.0/22 Valid RIR databaseRIPE 670 100% 66
45.89.224.0/22 Valid RIR databaseRIPE 670 100% 66
45.136.146.0/23 Valid RIR databaseRIPE 670 100% 66
46.243.142.0/23 Valid RIR databaseRIPE 670 100% 66
46.243.244.0/23 Valid RIR databaseRIPE 670 100% 66
85.208.209.0/24 Valid RIR databaseRIPE 670 100% 66
85.208.210.0/23 Valid RIR databaseRIPE 670 100% 66
85.209.149.0/24 Valid RIR databaseRIPE 670 100% 66
87.242.84.0/22 Valid RIR databaseRIPE 670 100% 66
87.242.116.0/22 Valid RIR databaseRIPE 670 100% 66
87.242.120.0/21 Valid RIR databaseRIPE 670 100% 66
88.218.65.0/24 Valid RIR databaseRIPE 670 100% 66
89.232.168.0/22 Valid RIR databaseRIPE 670 100% 66
89.232.176.0/22 Valid RIR databaseRIPE 670 100% 66
94.139.252.0/22 Valid RIR databaseRIPE 670 100% 66
94.158.22.0/23 Valid RIR databaseRIPE 670 100% 66
141.101.151.0/24 Valid RIR databaseRIPE 670 100% 66
141.101.152.0/24 Valid RIR databaseRIPE 670 100% 66
141.101.201.0/24 Valid RIR databaseRIPE 670 100% 66
176.109.96.0/20 Valid RIR databaseRIPE 670 100% 66
178.170.191.0/24 Valid RIR databaseRIPE 670 100% 66
178.170.192.0/22 Valid RIR databaseRIPE 670 100% 66
185.50.200.0/22 Valid RIR databaseRIPE 670 100% 66
188.72.108.0/23 Valid RIR databaseRIPE 670 100% 66
188.72.117.0/24 Valid RIR databaseRIPE 670 100% 66
193.105.4.0/24 Valid RIR databaseRIPE 670 100% 66
194.190.108.0/24 Valid RIR databaseRIPE 670 100% 66
37.18.10.0/24 Valid RIR databaseRIPE 669 99% 66
37.18.107.0/24 Valid RIR databaseRIPE 669 99% 66
37.18.114.0/24 Valid RIR databaseRIPE 669 99% 66
37.18.115.0/24 Valid RIR databaseRIPE 669 99% 66
37.230.139.0/24 Valid RIR databaseRIPE 669 99% 66
37.230.179.0/24 Valid RIR databaseRIPE 669 99% 66
37.230.186.0/24 Valid RIR databaseRIPE 669 99% 66
37.230.224.0/24 Valid RIR databaseRIPE 669 99% 66
37.230.233.0/24 Valid RIR databaseRIPE 669 99% 66
46.243.141.0/24 Valid RIR databaseRIPE 669 99% 66
46.243.172.0/24 Valid RIR databaseRIPE 669 99% 66
46.243.201.0/24 Valid RIR databaseRIPE 669 99% 66
46.243.205.0/24 Valid RIR databaseRIPE 669 99% 66
46.243.206.0/24 Valid RIR databaseRIPE 669 99% 66
2a0c:2b80::/29 Valid RIR databaseRIPE 635 100% 67
194.26.228.0/24 Valid RIR databaseRIPE 3 0%low visibility 3

AS-SET

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

  • Route object: not announced13

Route objects not announced

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

85.235.82.0/23RIPEValid
91.214.120.0/23RIPEValid
129.101.84.0/24RIPEValid
129.101.88.0/22RIPEValid
131.222.135.0/24RIPEValid
159.200.128.0/18RIPEValid
168.222.176.0/22RIPEValid
168.222.177.0/24RIPEValid
168.222.178.0/24RIPEValid
192.144.28.0/24RIPEValid
193.163.94.0/24RIPEValid
193.201.8.0/24RIPEValid
213.178.153.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.