WAVE-TELECOM-IF

Handle
Cluster stats
Netblocks5
All fragments 11 blocks across 4 clusters
Cluster ID205119434
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution RIR handle
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

IP Ranges (5)

⬇ export CSV
CIDR Org name Registry Status Confidence
93.187.0.0/24 WAVE-TELECOM-IF RIPE ASSIGNED PA ● low
93.187.1.0/24 WAVE-TELECOM-IF RIPE ASSIGNED PA ● low
93.187.2.0/24 WAVE-TELECOM-IF RIPE ASSIGNED PA ● low
93.187.3.0/24 WAVE-TELECOM-IF RIPE ASSIGNED PA ● low
93.187.4.0/24 WAVE-TELECOM-IF RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “WAVE TELECOM” — 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 (5 of 5)
RPKI-inferred operator JT (Jersey) Limited
Nearly all of this network's RPKI-covered space is cryptographically authorized for this single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE JE-TEL-MNT WAVE-TEL-MNT