PROJEKT

BGP inherited
Cluster stats
Netblocks6
Registered in Poland (5) · Germany (1)
All fragments 54 blocks across 34 clusters
Cluster ID205439203
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 3 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
87.204.112.160/29 AG-PROJEKT RIPE ASSIGNED PA ● low
89.171.33.208/30 PROJEKT RIPE ASSIGNED PA ● low
89.171.36.20/30 PROJEKT RIPE ASSIGNED PA ● low
89.171.79.184/29 AG-PROJEKT RIPE ASSIGNED PA ● low
89.171.141.32/30 PROJEKT RIPE ASSIGNED PA ● low
213.23.180.0/29 PROJEKT-NET RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “PROJEKT” — 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.
Combined view of all 34 name-family clusters →
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 (6 of 6)
No discrepancies found among checked blocks.

NIC Handles

ARCOR-MNT DUMY-RIPE DUMY-RIPE NETIA-MNT