ACVYSKOV-NET

BGP inherited
Cluster stats
Netblocks8 · 872 IPv4 addresses
All fragments 11 blocks across 3 clusters
Cluster ID209609878
RegistryRIPE
Customersfind 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

Footprint over time

5 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
94.199.192.128/28 ACVYSKOV-NET RIPE ASSIGNED PA ● low
94.199.192.160/28 ACVYSKOV-NET RIPE ASSIGNED PA ● low
94.199.192.176/28 ACVYSKOV-NET RIPE ASSIGNED PA ● low
94.199.192.192/27 ACVYSKOV-NET RIPE ASSIGNED PA ● low
94.199.192.224/27 ACVYSKOV-NET RIPE ASSIGNED PA ● low
94.199.193.0/24 ACVYSKOV-NET RIPE ASSIGNED PA ● low
94.199.196.0/24 ACVYSKOV-NET RIPE ASSIGNED PA ● low
94.199.197.0/24 ACVYSKOV-NET RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “ACVYSKOV” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.
  • ACVYSKOV-CZ via T-Mobile Czech Republic a.s. sub-allocation

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (8 of 8)
No discrepancies found among checked blocks.

NIC Handles

ACVYSKOV-MNT DUMY-RIPE DUMY-RIPE