AADT

BGP inherited
Cluster stats
Netblocks10
All fragments 13 blocks across 3 clusters
Cluster ID209098737
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.227.32/29 AADT RIPE ASSIGNED PA ● low
89.118.8.172/30 AADT RIPE ASSIGNED PA ● low
89.118.143.216/29 AADT RIPE ASSIGNED PA ● low
89.119.6.248/30 AADT RIPE ASSIGNED PA ● low
212.17.222.24/29 AADT RIPE ASSIGNED PA ● low
217.221.8.48/28 AADT RIPE ASSIGNED PA ● low
217.221.8.96/28 AADT RIPE ASSIGNED PA ● low
217.221.11.16/29 AADT RIPE ASSIGNED PA ● low
217.221.11.24/29 AADT RIPE ASSIGNED PA ● low
217.221.11.32/29 AADT RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “AADT” — 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 (10 of 10)
No discrepancies found among checked blocks.

NIC Handles

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