AO ALMAZ
Data as of 2026-09-20
BGP inherited
Limited data: only 2 ranges found registered
under this exact name. This may not reflect the organisation's full internet footprint — many companies'
web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.
This organisation
| Netblocks | 2 · 256 IPv4 addresses |
| IPv6 | 1 prefix (largest 2001:67c:29c::/48) |
| Record ID | 243843409 |
| Registry | BGP |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 8 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2001:67c:29c::/48 | AO ALMAZ | RIPE | ASSIGNED PI | ● high |
| 185.136.15.0/24 | AO ALMAZ | BGP | ANNOUNCED | ● low |
IPv6 ranges (1)
| CIDR |
|---|
| 2001:67c:29c::/48 |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
50.0%
of checked blocks have valid RPKI ROA coverage
(1 of 2)
Possible discrepancies (1)
These blocks are registered to AO ALMAZ 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.
| 185.136.15.0/24 /24 | authorized for AS205997 — Vlad Cojuhari |
NIC Handles
ALMAZ-MNT
AS205997
AS210328
DUMY-RIPE
DUMY-RIPE
MNT-TELEPATIYA
ORG-ZA238-RIPE
RIPE-NCC-END-MNT