Network · data from 2026-11-12
AS48287 RU-CENTER AS48287
Registry name: RU-CENTER JSC "RU-CENTER", RU · PeeringDB
40IPv4 routes
85.0% RPKI valid · 100.0% with a route object
2IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
6No ROA
0 with no route object for this origin
2Low visibility
seen by under 10% of full-table peers
39Route objects not announced
registered with origin AS48287, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS48287, 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.232.130.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 193.232.146.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.85.61.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.226.96.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 195.208.0.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 195.208.1.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 31.177.64.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 31.177.68.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 31.177.76.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.177.78.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 31.177.80.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.177.84.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.177.91.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.177.92.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 89.104.80.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 89.111.128.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.111.130.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.111.132.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 89.111.144.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 89.111.148.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 89.111.156.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 89.111.164.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.189.112.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 91.189.116.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 91.217.20.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.70.24.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 109.70.24.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.70.25.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.70.26.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 109.70.30.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 178.210.64.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 178.210.64.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 178.210.80.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 178.210.88.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 178.210.92.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.26.112.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.76.144.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 195.24.64.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 195.24.68.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 91.189.114.0/23 | Valid | RIR databaseRIPE | 670 100% |
| 2a02:2090::/48 | Valid | RIR databaseRIPE | 17 3%low visibility |
| 2a02:2090:1::/48 | Valid | RIR databaseRIPE | 17 3%low visibility |
AS-SET
AS48287's PeeringDB record names no 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 45 are in fix.csv.
- ROA: none6
- Route object: not announced39
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 193.232.130.0/24 | No ROA covers it. Add a ROA for AS48287, maxLength 24. |
| ROA: none | 193.232.146.0/24 | No ROA covers it. Add a ROA for AS48287, maxLength 24. |
| ROA: none | 194.85.61.0/24 | No ROA covers it. Add a ROA for AS48287, maxLength 24. |
| ROA: none | 194.226.96.0/24 | No ROA covers it. Add a ROA for AS48287, maxLength 24. |
| ROA: none | 195.208.0.0/24 | No ROA covers it. Add a ROA for AS48287, maxLength 24. |
| ROA: none | 195.208.1.0/24 | No ROA covers it. Add a ROA for AS48287, maxLength 24. |
Route objects not announced
Route objects with origin AS48287 whose prefix no peer sees AS48287 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 31.177.64.0/23 | RIPE | Valid |
| 31.177.64.0/24 | RIPE | Valid |
| 31.177.66.0/23 | RIPE | Valid |
| 31.177.72.0/21 | RIPE | Valid |
| 31.177.72.0/22 | RIPE | Valid |
| 31.177.72.0/23 | RIPE | Valid |
| 31.177.80.0/21 | RIPE | Valid |
| 31.177.80.0/23 | RIPE | Valid |
| 31.177.81.0/24 | RIPE | Valid |
| 31.177.83.0/24 | RIPE | Valid |
| 31.177.85.0/24 | RIPE | Valid |
| 31.177.88.0/21 | RIPE | Valid |
| 31.177.88.0/22 | RIPE | Valid |
| 31.177.88.0/24 | RIPE | Invalid: maxLength |
| 31.177.89.0/24 | RIPE | Invalid: maxLength |
| 31.177.90.0/24 | RIPE | Invalid: maxLength |
| 31.177.92.0/23 | RIPE | Invalid: maxLength |
| 31.177.92.0/24 | RIPE | Valid |
| 79.174.72.0/22 | RIPE | Invalid: origin |
| 89.104.76.0/22 | RIPE | Invalid: origin |
| 89.111.128.0/21 | RIPE | Invalid: origin |
| 89.111.128.0/23 | RIPE | Invalid: origin |
| 91.217.21.0/24 | RIPE | Valid |
| 109.70.28.0/23 | RIPE | Valid |
| 109.70.28.0/24 | RIPE | Valid |
| 109.70.31.0/24 | RIPE | Valid |
| 178.210.94.0/23 | RIPE | Valid |
| 178.210.94.0/24 | RIPE | Valid |
| 178.210.95.0/24 | RIPE | Valid |
| 185.26.112.0/23 | RIPE | Invalid: maxLength |
| 185.26.112.0/24 | RIPE | Invalid: maxLength |
| 185.76.147.0/24 | RIPE | Invalid: maxLength |
| 195.24.64.0/21 | RIPE | No ROA |
| 195.24.68.0/22 | RIPE | Valid |
| 195.24.70.0/23 | RIPE | Invalid: maxLength |
| 195.208.0.0/23 | RIPE | No ROA |
| 2a02:2090:e400::/48 | RIPE | Valid |
| 2a02:2090:e800::/48 | RIPE | Valid |
| 2a02:2090:ec00::/48 | RIPE | Valid |
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.