DAAA

BGP inherited
Cluster stats
Netblocks10
Cluster ID208835197
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

Footprint over time

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

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
78.5.143.224/27 DAAA RIPE ASSIGNED PA ● low
85.20.72.16/30 DAAA RIPE ASSIGNED PA ● low
85.20.72.104/30 DAAA RIPE ASSIGNED PA ● low
89.118.248.44/30 DAAA RIPE ASSIGNED PA ● low
89.118.248.96/30 DAAA RIPE ASSIGNED PA ● low
89.118.248.128/26 DAAA RIPE ASSIGNED PA ● low
213.213.84.188/30 DAAA RIPE ASSIGNED PA ● low
213.255.41.96/28 DAAA RIPE ASSIGNED PA ● low
217.221.87.160/27 DAAA RIPE ASSIGNED PA ● low
217.221.207.0/27 DAAA RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
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 (10 of 10)
No discrepancies found among checked blocks.

NIC Handles

ALBACOM-MNT BTI-MNT DUMY-RIPE DUMY-RIPE