Alarig

Registry
Cluster stats
Netblocks8
All fragments 12 blocks across 3 clusters
Cluster ID213185611
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
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
185.1.89.23/32 Alarig PEERINGDB ASSIGNED ● high
185.1.169.22/32 Alarig PEERINGDB ASSIGNED ● high
193.34.197.135/32 Alarig PEERINGDB ASSIGNED ● high
195.13.37.133/32 Alarig PEERINGDB ASSIGNED ● high
2001:7f8:4f::20:8627:1/128 Alarig PEERINGDB ASSIGNED ● high
2001:7f8:6d::20:8627:1/128 Alarig PEERINGDB ASSIGNED ● high
2001:7f8:b1::19/128 Alarig PEERINGDB ASSIGNED ● high
2001:7f8:f4::20:8627:1/128 Alarig PEERINGDB ASSIGNED ● high

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “Alarig” — 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: C how networks compare →
75.0% of checked blocks have valid RPKI ROA coverage (6 of 8)
No discrepancies found among checked blocks.

NIC Handles

AS208627