RAJALA-NET

BGP inherited
Cluster stats
Netblocks9 · 483 IPv4 addresses
All fragments 10 blocks across 2 clusters
Cluster ID208874759
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
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-19

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
192.89.10.0/26 RAJALA-NET RIPE ASSIGNED PA ● low
192.130.245.160/27 RAJALA-NET RIPE ASSIGNED PA ● low
192.194.237.128/28 RAJALA-NET RIPE ASSIGNED PA ● low
194.111.213.0/24 RAJALA-NET RIPE ASSIGNED PA ● low
194.215.57.64/26 RAJALA-NET RIPE ASSIGNED PA ● low
194.215.57.160/27 RAJALA-NET RIPE ASSIGNED PA ● low
195.165.148.120/29 RAJALA-NET RIPE ASSIGNED PA ● low
195.165.148.136/30 RAJALA-NET RIPE ASSIGNED PA ● low
212.213.141.80/28 RAJALA-NET RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “RAJALA” — 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 (9 of 9)
No discrepancies found among checked blocks.

NIC Handles

DATANET-NOC DUMY-RIPE DUMY-RIPE