ORG-iEWA1-RIPE

Data as of 2026-08-30
BGP inherited
This organisation
Netblocks9 · 2,304 IPv4 addresses
Record ID236099543
RegistryRIPE
Customerssee who runs inside 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 · report an issue

Footprint over time

10 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-08-30

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
80.243.172.0/24 UNKNOWN RIPE ASSIGNED PA ● medium
80.243.173.0/24 UNKNOWN RIPE ASSIGNED PA ● medium
80.243.174.0/24 UNKNOWN RIPE ASSIGNED PA ● medium
194.112.221.0/24 UNKNOWN RIPE ASSIGNED PA ● medium
194.112.223.0/24 UNKNOWN RIPE ASSIGNED PA ● medium
194.112.229.0/24 UNKNOWN RIPE ASSIGNED PA ● medium
194.112.238.0/24 UNKNOWN RIPE ASSIGNED PA ● medium
194.112.246.0/24 UNKNOWN RIPE ASSIGNED PA ● medium
194.112.249.0/24 UNKNOWN RIPE ASSIGNED PA ● medium

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (9 of 9)
RPKI-inferred operator eww ag
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

AS3330-MNT DUMY-RIPE DUMY-RIPE ITANDTEL-MNT