AMAG-NET

BGP inherited
Cluster stats
Netblocks9 · 496 IPv4 addresses
All fragments 17 blocks across 4 clusters
Cluster ID208852537
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
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-19

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
195.65.30.0/24 AMAG-NET RIPE ASSIGNED PA ● low
195.144.52.192/29 AMAG-NET RIPE ASSIGNED PA ● low
212.243.136.160/29 AMAG-NET RIPE ASSIGNED PA ● low
212.243.156.184/29 AMAG-NET RIPE ASSIGNED PA ● low
212.243.169.0/25 AMAG-NET RIPE ASSIGNED PA ● low
212.243.169.128/28 AMAG-NET RIPE ASSIGNED PA ● low
212.243.177.80/28 AMAG-NET RIPE ASSIGNED PA ● low
212.243.213.64/26 AMAG-NET RIPE ASSIGNED PA ● low
217.193.145.64/32 AMAG-NET RIPE ASSIGNED PA ● low

Possibly related to this organisation

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

NIC Handles

CH-UNISOURCE-MNT DUMY-RIPE DUMY-RIPE