bgpreport

Network · data from 2026-11-12

AS39494 RU-CENTER-AS JSC "RU-CENTER"

Registry name: RU-CENTER-AS JSC "RU-CENTER", RU · not in PeeringDB

28IPv4 routes 100.0% RPKI valid · 100.0% with a route object
6IPv6 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
15Route objects not announced registered with origin AS39494, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS39494, 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.
31.177.72.0/22 Valid RIR databaseRIPE 673 100% 66
31.177.76.0/23 Valid RIR databaseRIPE 673 100% 66
31.177.80.0/23 Valid RIR databaseRIPE 673 100% 66
31.177.84.0/23 Valid RIR databaseRIPE 673 100% 66
31.177.85.0/24 Valid RIR databaseRIPE 673 100% 67
31.177.86.0/24 Valid RIR databaseRIPE 673 100% 66
31.177.87.0/24 Valid RIR databaseRIPE 673 100% 66
31.177.88.0/24 Valid RIR databaseRIPE 673 100% 66
31.177.89.0/24 Valid RIR databaseRIPE 673 100% 66
31.177.90.0/24 Valid RIR databaseRIPE 673 100% 66
77.222.33.0/24 Valid RIR databaseRIPE 673 100% 66
77.222.34.0/24 Valid RIR databaseRIPE 673 100% 66
79.174.64.0/21 Valid RIR databaseRIPE 673 100% 66
79.174.72.0/22 Valid RIR databaseRIPE 673 100% 66
79.174.76.0/24 Valid RIR databaseRIPE 673 100% 66
80.93.56.0/22 Valid RIR databaseRIPE 673 100% 66
89.104.76.0/23 Valid RIR databaseRIPE 673 100% 66
89.104.78.0/23 Valid RIR databaseRIPE 673 100% 66
89.104.88.0/22 Valid RIR databaseRIPE 673 100% 66
89.104.92.0/24 Valid RIR databaseRIPE 673 100% 66
89.111.161.0/24 Valid RIR databaseRIPE 673 100% 67
89.111.166.0/24 Valid RIR databaseRIPE 673 100% 66
89.111.176.0/20 Valid RIR databaseRIPE 673 100% 66
91.217.21.0/24 Valid RIR databaseRIPE 673 100% 66
89.111.160.0/24 Valid RIR databaseRIPE 670 100% 67
89.111.128.0/20 Valid RIR databaseRIPE 669 99% 66
89.111.162.0/23 Valid RIR databaseRIPE 669 99% 67
89.111.164.0/22 Valid RIR databaseRIPE 669 99% 67
2a02:2090:e400::/48 Valid RIR databaseRIPE 636 100% 68
2a02:2090:e800::/48 Valid RIR databaseRIPE 636 100% 69
2a02:2090:ec00::/48 Valid RIR databaseRIPE 636 100% 69
2a01:d8::/32 Valid RIR databaseRIPE 635 100% 69
2a02:2090::/48 Valid RIR databaseRIPE 619 97% 69
2a02:2090:1::/48 Valid RIR databaseRIPE 619 97% 69

AS-SET

AS39494 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 15 are in fix.csv.

  • Route object: not announced15

Route objects not announced

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

31.177.86.0/23RIPEValid
89.104.64.0/19RIPEValid
89.104.64.0/20RIPEInvalid: maxLength
89.104.76.0/22RIPEInvalid: maxLength
89.104.76.0/24RIPEValid
89.104.77.0/24RIPEInvalid: maxLength
89.104.80.0/20RIPEInvalid: maxLength
89.104.88.0/24RIPEInvalid: maxLength
89.111.128.0/18RIPEValid
89.111.144.0/20RIPEValid
89.111.160.0/20RIPEValid
89.111.176.0/22RIPEValid
89.111.177.0/24RIPEValid
2a02:2090:9800::/48RIPEValid
2a02:2090:a800::/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.