RP15937-RIPE

Handle
Cluster stats
Netblocks8
Cluster ID210295925
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution RIR handle
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
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
2a0f:e401:110::/48 RP15937-RIPE RIPE ASSIGNED ● low
2a0f:e401:111::/48 RP15937-RIPE RIPE ASSIGNED ● low
2a0f:e401:113::/48 RP15937-RIPE RIPE ASSIGNED ● low
2a0f:e401:114::/48 RP15937-RIPE RIPE ASSIGNED ● low
2a0f:e401:116::/48 RP15937-RIPE RIPE ASSIGNED ● low
2a0f:e401:118::/48 RP15937-RIPE RIPE ASSIGNED ● low
2a0f:e401:11a::/48 RP15937-RIPE RIPE ASSIGNED ● low
2a0f:e401:11c::/48 RP15937-RIPE RIPE ASSIGNED ● low

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (8 of 8)
RPKI-inferred operator Rishikeshan Lavakumar
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 RK-PUBLIC