AGAT

BGP inherited
Cluster stats
Netblocks7
Registered in KZ (3) · Russia (2) · Italy (1) · Poland (1)
All fragments 13 blocks across 6 clusters
Cluster ID209913377
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 6 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
78.4.99.17/32 AGAT RIPE ASSIGNED PA ● low
82.200.140.116/30 AGAT RIPE ASSIGNED PA ● low
82.200.240.196/30 AGAT RIPE ASSIGNED PA ● low
88.199.89.160/27 AGAT RIPE ASSIGNED PA ● low
89.175.13.192/29 AGAT RIPE ASSIGNED PA ● low
89.175.177.176/30 AGAT RIPE ASSIGNED PA ● low
95.56.240.112/28 AGAT RIPE ASSIGNED PA ● low

Possibly related to this organisation

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

NIC Handles

BTI-MNT DUMY-RIPE DUMY-RIPE KNIC-MNT MTU-NOC NETIA-MNT