Run River

RunRiver
Registry
Cluster stats
Netblocks10
Registered in Indonesia (2) · Japan (2) · Singapore (1)
Cluster ID213186231
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-07-19

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
103.162.254.130/32 RunRiver PEERINGDB ASSIGNED ● high
119.11.187.44/32 RunRiver PEERINGDB ASSIGNED ● high
123.108.11.208/32 RunRiver PEERINGDB ASSIGNED ● high
210.171.225.136/32 RunRiver PEERINGDB ASSIGNED ● high
210.173.177.192/32 RunRiver PEERINGDB ASSIGNED ● high
2001:7fa:2:5::3e0/128 RunRiver PEERINGDB ASSIGNED ● high
2001:7fa:7:1:0:13:3182:1/128 RunRiver PEERINGDB ASSIGNED ● high
2001:de8:8::13:3182:1/128 RunRiver PEERINGDB ASSIGNED ● high
2001:df6:480:0:2:83e:0:1/128 RunRiver PEERINGDB ASSIGNED ● high
2404:c8:0:a:0:13:3182:1/128 RunRiver PEERINGDB ASSIGNED ● high

Network trust

what's this?
RPKI hygiene: B how networks compare →
90.0% of checked blocks have valid RPKI ROA coverage (9 of 10)
No discrepancies found among checked blocks.

NIC Handles

AS133182