INRES

BGP inherited
Cluster stats
Netblocks6
All fragments 10 blocks across 3 clusters
Cluster ID204982231
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

4 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-13

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
80.204.66.64/28 INRES RIPE ASSIGNED PA ● low
178.237.2.72/29 INRES-NET RIPE ASSIGNED PA ● low
178.237.3.224/28 INRES-NET RIPE ASSIGNED PA ● low
194.184.38.224/30 INRES RIPE ASSIGNED PA ● low
212.131.135.192/28 INRES RIPE ASSIGNED PA ● low
217.57.30.136/29 INRES RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “INRES” — 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.

NIC Handles

BRT-MNT DUMY-RIPE DUMY-RIPE INTERB-MNT TIG-MNT