FNS-MOSKVA

Data as of 2026-08-30
BGP inherited
Cluster stats
Netblocks11
Cluster ID232063863
RegistryRIPE
Customersfind customers using 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

Footprint over time

10 weekly snapshots · JSON
11 0 netblocks since 2026-07-05
2026-07-05 peak 11 2026-08-30

IP Ranges (11)

⬇ export CSV
CIDR Org name Registry Status Confidence
213.24.62.96/28 FNS-MOSKVA RIPE ASSIGNED PA ● low
213.24.62.112/28 FNS-MOSKVA RIPE ASSIGNED PA ● low
213.24.62.128/28 FNS-MOSKVA RIPE ASSIGNED PA ● low
213.24.62.144/28 FNS-MOSKVA RIPE ASSIGNED PA ● low
213.24.62.160/28 FNS-MOSKVA RIPE ASSIGNED PA ● low
213.24.62.176/28 FNS-MOSKVA RIPE ASSIGNED PA ● low
213.24.62.192/28 FNS-MOSKVA RIPE ASSIGNED PA ● low
213.24.62.208/28 FNS-MOSKVA RIPE ASSIGNED PA ● low
213.24.62.224/28 FNS-MOSKVA RIPE ASSIGNED PA ● low
213.24.62.240/28 FNS-MOSKVA RIPE ASSIGNED PA ● low
213.24.63.0/28 FNS-MOSKVA 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 (11 of 11)
No discrepancies found among checked blocks.

NIC Handles

AS8342-MNT DUMY-RIPE DUMY-RIPE ROSTELECOM-MNT