DEAC-COLOCATION-DC-NET

BGP inherited
Cluster stats
Netblocks7 · 1,785 IPv4 addresses
All fragments 10 blocks across 2 clusters
Cluster ID209585445
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
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-19

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
89.111.36.0/24 DEAC-COLOCATION-DC-NET RIPE ASSIGNED PA ● low
89.111.37.0/24 DEAC-COLOCATION-DC-NET RIPE ASSIGNED PA ● low
89.111.38.0/24 DEAC-COLOCATION-DC-NET RIPE ASSIGNED PA ● low
89.111.39.0/24 DEAC-COLOCATION-DC-NET RIPE ASSIGNED PA ● low
89.111.40.0/24 DEAC-COLOCATION-DC-NET RIPE ASSIGNED PA ● low
89.111.41.0/24 DEAC-COLOCATION-DC-NET RIPE ASSIGNED PA ● low
89.111.42.0/24 DEAC-COLOCATION-DC-NET RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “DEAC COLOCATION DC” — 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.

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (7 of 7)
RPKI-inferred operator Sabiedriba ar ierobezotu atbildibu DELSKA Latvia
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

DEAC-MNT DUMY-RIPE DUMY-RIPE