RU-BASHRTCOMM
Data as of 2026-07-26
BGP inherited
Cluster stats
| Netblocks | 4 · 1,024 IPv4 addresses |
| Cluster ID | 217112718 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 94.229.20.0/24 | RU-BASHRTCOMM | RIPE | ASSIGNED PA | ● low |
| 94.229.21.0/24 | RU-BASHRTCOMM | RIPE | ASSIGNED PA | ● low |
| 94.229.22.0/24 | RU-BASHRTCOMM | RIPE | ASSIGNED PA | ● low |
| 94.229.23.0/24 | RU-BASHRTCOMM | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
75.0%
of checked blocks have valid RPKI ROA coverage
(3 of 4)
RPKI-inferred operator
RTK-Volga-Ural LLC
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
BRTC-mnt
DUMY-RIPE
DUMY-RIPE