INVI

BGP inherited
Cluster stats
Netblocks7
All fragments 10 blocks across 4 clusters
Cluster ID210845799
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
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
82.200.128.56/30 INVI RIPE ASSIGNED PA ● low
82.200.142.8/30 INVI RIPE ASSIGNED PA ● low
82.200.241.136/30 INVI RIPE ASSIGNED PA ● low
92.46.57.156/30 INVI RIPE ASSIGNED PA ● low
178.88.69.152/30 INVI RIPE ASSIGNED PA ● low
178.88.112.168/30 INVI RIPE ASSIGNED PA ● low
178.88.162.184/30 INVI RIPE ASSIGNED PA ● low

Possibly related to this organisation

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

DUMY-RIPE DUMY-RIPE KNIC-MNT