bgpreport

Network · data from 2026-11-12

AS15493 RUSCOMP-AS "Russian company" LLC

Registry name: RUSCOMP-AS "Russian company" LLC, RU · not in PeeringDB

62IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 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
0Low visibility seen by under 10% of full-table peers
44Route objects not announced registered with origin AS15493, seen from no peer

Announced routes

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

5.1.48.0/24 Valid RIR databaseRIPE 673 100% 66
5.1.49.0/24 Valid RIR databaseRIPE 673 100% 66
5.1.50.0/24 Valid RIR databaseRIPE 673 100% 66
5.1.51.0/24 Valid RIR databaseRIPE 673 100% 66
5.1.52.0/24 Valid RIR databaseRIPE 673 100% 66
5.1.54.0/24 Valid RIR databaseRIPE 673 100% 66
5.1.55.0/24 Valid RIR databaseRIPE 673 100% 67
80.91.23.0/24 Valid RIR databaseRIPE 673 100% 66
91.203.36.0/24 Valid RIR databaseRIPE 673 100% 66
91.203.39.0/24 Valid RIR databaseRIPE 673 100% 66
91.211.192.0/24 Valid RIR databaseRIPE 673 100% 66
91.211.195.0/24 Valid RIR databaseRIPE 673 100% 66
178.236.210.0/24 Valid RIR databaseRIPE 673 100% 66
178.236.213.0/24 Valid RIR databaseRIPE 673 100% 66
178.236.216.0/24 Valid RIR databaseRIPE 673 100% 66
178.236.217.0/24 Valid RIR databaseRIPE 673 100% 66
178.236.218.0/24 Valid RIR databaseRIPE 673 100% 66
178.236.223.0/24 Valid RIR databaseRIPE 673 100% 66
185.11.4.0/24 Valid RIR databaseRIPE 673 100% 66
185.11.5.0/24 Valid RIR databaseRIPE 673 100% 66
185.11.6.0/24 Valid RIR databaseRIPE 673 100% 66
217.116.48.0/24 Valid RIR databaseRIPE 673 100% 66
217.116.49.0/24 Valid RIR databaseRIPE 673 100% 66
217.116.50.0/24 Valid RIR databaseRIPE 673 100% 66
217.116.51.0/24 Valid RIR databaseRIPE 673 100% 66
217.116.52.0/24 Valid RIR databaseRIPE 673 100% 66
217.116.53.0/24 Valid RIR databaseRIPE 673 100% 66
217.116.54.0/24 Valid RIR databaseRIPE 673 100% 66
217.116.55.0/24 Valid RIR databaseRIPE 673 100% 66
217.116.56.0/24 Valid RIR databaseRIPE 673 100% 66
217.116.57.0/24 Valid RIR databaseRIPE 673 100% 66
217.116.58.0/24 Valid RIR databaseRIPE 673 100% 66
217.116.59.0/24 Valid RIR databaseRIPE 673 100% 66
217.116.60.0/24 Valid RIR databaseRIPE 673 100% 66
217.116.61.0/24 Valid RIR databaseRIPE 673 100% 66
217.116.62.0/24 Valid RIR databaseRIPE 673 100% 66
217.116.63.0/24 Valid RIR databaseRIPE 673 100% 66
77.242.96.0/24 Valid RIR databaseRIPE 672 100% 66
77.242.98.0/24 Valid RIR databaseRIPE 672 100% 66
77.242.99.0/24 Valid RIR databaseRIPE 672 100% 66
77.242.100.0/24 Valid RIR databaseRIPE 672 100% 66
77.242.105.0/24 Valid RIR databaseRIPE 672 100% 66
77.242.107.0/24 Valid RIR databaseRIPE 672 100% 66
77.242.108.0/24 Valid RIR databaseRIPE 672 100% 66
77.242.109.0/24 Valid RIR databaseRIPE 672 100% 66
77.242.110.0/24 Valid RIR databaseRIPE 672 100% 66
77.242.111.0/24 Valid RIR databaseRIPE 672 100% 66
80.91.16.0/24 Valid RIR databaseRIPE 672 100% 66
80.91.17.0/24 Valid RIR databaseRIPE 672 100% 66
80.91.18.0/24 Valid RIR databaseRIPE 672 100% 66
80.91.19.0/24 Valid RIR databaseRIPE 672 100% 66
80.91.20.0/24 Valid RIR databaseRIPE 672 100% 66
80.91.21.0/24 Valid RIR databaseRIPE 672 100% 66
80.91.22.0/24 Valid RIR databaseRIPE 672 100% 66
80.91.24.0/24 Valid RIR databaseRIPE 672 100% 66
80.91.25.0/24 Valid RIR databaseRIPE 672 100% 66
80.91.26.0/24 Valid RIR databaseRIPE 672 100% 66
80.91.27.0/24 Valid RIR databaseRIPE 672 100% 66
80.91.28.0/24 Valid RIR databaseRIPE 672 100% 66
80.91.29.0/24 Valid RIR databaseRIPE 672 100% 66
80.91.30.0/24 Valid RIR databaseRIPE 672 100% 66
80.91.31.0/24 Valid RIR databaseRIPE 672 100% 66
2a02:dc00:1::/48 Valid RIR databaseRIPE 636 100% 69
2a02:dc00:2::/48 Valid RIR databaseRIPE 636 100% 69
2a02:dc00:100::/48 Valid RIR databaseRIPE 636 100% 69

AS-SET

AS15493 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 44 are in fix.csv.

  • Route object: not announced44

Route objects not announced

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

5.1.48.0/21RIPENo ROA
77.242.96.0/20RIPEValid
77.242.97.0/24RIPEValid
77.242.101.0/24RIPEValid
77.242.102.0/24RIPEValid
77.242.103.0/24RIPEValid
77.242.104.0/24RIPEValid
77.242.106.0/24RIPEValid
80.91.16.0/20RIPEValid
91.203.36.0/22RIPENo ROA
91.211.192.0/22RIPEValid
91.211.193.0/24RIPEValid
91.211.194.0/24RIPEValid
145.224.112.0/23RIPEInvalid: origin
171.25.244.0/22RIPENo ROA
171.25.244.0/24RIPENo ROA
171.25.245.0/24RIPENo ROA
171.25.246.0/24RIPENo ROA
171.25.247.0/24RIPENo ROA
171.25.252.0/22RIPENo ROA
171.25.252.0/24RIPENo ROA
171.25.253.0/24RIPENo ROA
171.25.254.0/24RIPENo ROA
171.25.255.0/24RIPENo ROA
178.236.208.0/20RIPEValid
178.236.208.0/24RIPEValid
178.236.209.0/24RIPEValid
178.236.211.0/24RIPEValid
178.236.212.0/24RIPEValid
178.236.214.0/24RIPEValid
178.236.215.0/24RIPEValid
178.236.219.0/24RIPEValid
178.236.220.0/24RIPEValid
178.236.221.0/24RIPEValid
178.236.222.0/24RIPEValid
185.11.4.0/22RIPENo ROA
185.11.4.0/23RIPEValid
185.11.6.0/23RIPEValid
185.11.7.0/24RIPEValid
217.116.48.0/20RIPEValid
2a02:dc00::/29RIPENo ROA
2a02:dc00:200::/48RIPENo ROA
2a02:dc00:202::/48RIPENo ROA
2a02:dc00:400::/48RIPENo 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.