bgpreport

Network · data from 2026-11-12

AS44493 CHELYABINSK-SIGNAL-AS Chelyabinsk-Signal LLC

Registry name: CHELYABINSK-SIGNAL-AS Chelyabinsk-Signal LLC, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS44493, 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.
91.202.12.0/22 No ROA RIR databaseRIPE 673 100% 66
91.202.12.0/24 No ROA RIR databaseRIPE 673 100% 66
91.202.13.0/24 No ROA RIR databaseRIPE 673 100% 66
91.202.14.0/23 No ROA RIR databaseRIPE 673 100% 66
91.202.14.0/24 No ROA RIR databaseRIPE 673 100% 66
91.202.15.0/24 No ROA RIR databaseRIPE 673 100% 66
31.192.234.0/24 Valid RIR databaseRIPE 673 100% 67
31.192.235.0/24 Valid RIR databaseRIPE 673 100% 67
31.192.236.0/24 Valid RIR databaseRIPE 673 100% 67
31.192.237.0/24 Valid RIR databaseRIPE 673 100% 66
31.192.238.0/24 Valid RIR databaseRIPE 673 100% 67
31.192.239.0/24 Valid RIR databaseRIPE 673 100% 67
80.85.152.0/23 Valid RIR databaseRIPE 673 100% 66
80.85.156.0/22 Valid RIR databaseRIPE 673 100% 66
185.144.29.0/24 Valid RIR databaseRIPE 673 100% 66
185.144.30.0/23 Valid RIR databaseRIPE 673 100% 66
80.85.154.0/24 Valid RIR databaseRIPE 672 100% 66
185.144.28.0/24 Valid RIR databaseRIPE 671 100% 67
31.192.232.0/24 Valid RIR databaseRIPE 670 100% 67
2a03:a0e0::/32 Valid RIR databaseRIPE 636 100% 67
2a0a:eec0::/48 Valid RIR databaseRIPE 636 100% 67
2a0a:eec0:3::/48 Valid RIR databaseRIPE 636 100% 67
2a0a:eec0:4::/48 Valid RIR databaseRIPE 636 100% 67
2a0a:eec0:5::/48 Valid RIR databaseRIPE 636 100% 69
2a0a:eec0:6::/48 Valid RIR databaseRIPE 636 100% 67
2a0a:eec0:2::/48 Valid RIR databaseRIPE 635 100% 67
2a0a:eec0:7::/48 Valid RIR databaseRIPE 631 99% 67

AS-SET

AS44493 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 8 are in fix.csv.

  • ROA: none6
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none91.202.12.0/22No ROA covers it. Add a ROA for AS44493, maxLength 22.673 of 673
ROA: none91.202.12.0/24No ROA covers it. Add a ROA for AS44493, maxLength 24.673 of 673
ROA: none91.202.13.0/24No ROA covers it. Add a ROA for AS44493, maxLength 24.673 of 673
ROA: none91.202.14.0/23No ROA covers it. Add a ROA for AS44493, maxLength 23.673 of 673
ROA: none91.202.14.0/24No ROA covers it. Add a ROA for AS44493, maxLength 24.673 of 673
ROA: none91.202.15.0/24No ROA covers it. Add a ROA for AS44493, maxLength 24.673 of 673

Route objects not announced

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

91.202.12.0/23RIPENo ROA
185.118.164.0/22RIPENo 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.