AO ALMAZ

Data as of 2026-10-04
BGP inherited
Limited data: only 3 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
Netblocks3 · 512 IPv4 addresses
IPv6 1 prefix (largest 2001:67c:29c::/48)
Record ID248399921
RegistryBGP
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 11 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 (3)

⬇ export CSV
CIDR Org name Registry Status Confidence
2001:67c:29c::/48 AO ALMAZ RIPE ASSIGNED PI ● high
77.91.65.0/24 AO ALMAZ BGP ANNOUNCED ● low
185.136.15.0/24 AO ALMAZ BGP ANNOUNCED ● low

IPv6 ranges (1)

Network trust

what's this?
RPKI hygiene: C how networks compare →
66.7% of checked blocks have valid RPKI ROA coverage (2 of 3)
Possible discrepancies (2)

These blocks are registered to AO ALMAZ but cryptographically authorized for a different, unrelated network (2 distinct holders) — 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
77.91.65.0/24 /24 authorized for AS205775 — NEON CORE NETWORK LLC

NIC Handles

ALMAZ-MNT AS205997 AS210328 AS42861 DUMY-RIPE DUMY-RIPE MNT-TELEPATIYA ORG-ZA238-RIPE RIPE-NCC-END-MNT lir-ge-fast-1-MNT lir-ru-ooomir-1-MNT