CTTC-Ryazan
Data as of 2026-09-06
BGP inherited
This organisation
| Netblocks | 4 · 640 IPv4 addresses |
| Also registered under this name | 5 netblocks across 2 separate records |
| Record ID | 236268613 |
| Registry | RIPE |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 4 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 |
|---|---|---|---|---|
| 213.137.237.0/25 | CTTC-Ryazan | RIPE | ASSIGNED PA | ● low |
| 213.137.238.0/24 | CTTC-Ryazan | RIPE | ASSIGNED PA | ● low |
| 213.137.239.0 – 213.137.239.191 | CTTC-Ryazan | RIPE | ASSIGNED PA | ● low |
| 213.137.239.192/26 | CTTC-Ryazan | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
Possible discrepancies (1)
These blocks are registered to CTTC-Ryazan but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 213.137.238.0/24 /24 | authorized for AS20485 — Joint Stock Company TransTeleCom |
NIC Handles
CTTC-MNT
DUMY-RIPE
DUMY-RIPE
TRANSTELECOM-MNT