INGA

BGP inherited
Cluster stats
Netblocks7
Registered in Portugal (4) · Russia (2) · Poland (1)
All fragments 8 blocks across 2 clusters
Cluster ID208847932
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 6 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names 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
194.65.115.208/28 INGA RIPE ASSIGNED PA ● low
195.151.30.32/27 INGA-NET RIPE ASSIGNED PA ● low
195.151.167.216/29 INGA-NET RIPE ASSIGNED PA ● low
212.244.156.32/28 INGA RIPE ASSIGNED PA ● low
213.58.140.112/28 INGA RIPE ASSIGNED PA ● low
213.58.141.112/28 INGA RIPE ASSIGNED PA ● low
213.58.156.144/28 INGA RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “INGA” — 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: C how networks compare →
71.4% of checked blocks have valid RPKI ROA coverage (5 of 7)
No discrepancies found among checked blocks.

NIC Handles

AS9186-MNT DUMY-RIPE DUMY-RIPE ROSPRINT-NCC TELEPAC-MNT TPNET