AMTEL-SVYAZ
BGP inherited
Cluster stats
| Netblocks | 4 · 1,020 IPv4 addresses |
| Cluster ID | 209515754 |
| 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 | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 81.177.40.0/24 | AMTEL-SVYAZ | RIPE | ASSIGNED PA | ● low |
| 213.24.2.0/24 | AMTEL-SVYAZ | RIPE | ASSIGNED PA | ● low |
| 213.24.3.0/24 | AMTEL-SVYAZ | RIPE | ASSIGNED PA | ● low |
| 213.24.4.0/24 | AMTEL-SVYAZ | 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
PJSC Rostelecom
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
AS8342-MNT
DUMY-RIPE
DUMY-RIPE