JUDZ

BGP inherited
Cluster stats
Netblocks7
Cluster ID209881261
RegistryRIPE
Customersfind customers using 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

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
78.5.66.52/30 JUDZ RIPE ASSIGNED PA ● low
78.5.68.211/32 JUDZ RIPE ASSIGNED PA ● low
78.7.76.192/29 JUDZ RIPE ASSIGNED PA ● low
78.7.76.220/30 JUDZ RIPE ASSIGNED PA ● low
78.7.120.140/32 JUDZ RIPE ASSIGNED PA ● low
78.7.166.184/30 JUDZ RIPE ASSIGNED PA ● low
217.220.123.203/32 JUDZ RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
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

ALBACOM-MNT BTI-MNT DUMY-RIPE DUMY-RIPE