Altagen

Registry

Cluster stats

Netblocks	8
All fragments	47 blocks across 2 clusters
Cluster ID	208803842
Registry	PEERINGDB
Customers	find 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
31.44.186.230/32	Altagen	PEERINGDB	ASSIGNED	● high
37.9.49.37/32	Altagen	PEERINGDB	ASSIGNED	● high
185.0.12.44/32	Altagen	PEERINGDB	ASSIGNED	● high
185.1.152.167/32	Altagen	PEERINGDB	ASSIGNED	● high
185.232.60.247/32	Altagen	PEERINGDB	ASSIGNED	● high
193.27.37.34/32	Altagen	PEERINGDB	ASSIGNED	● high
193.27.39.49/32	Altagen	PEERINGDB	ASSIGNED	● high
195.208.209.113/32	Altagen	PEERINGDB	ASSIGNED	● high

Possibly related to this organisation

what's this?

Same name family

Separately-registered clusters whose names share “Altagen” — 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.

Altagen JSC 39 blocks

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.

Altagen 20130318 1 via Altagen JSC sub-allocation
Altagen 20130318 2 via Altagen JSC sub-allocation
Altagen 20130318 3 via Altagen JSC sub-allocation
Altagen 20130318 4 via Altagen JSC sub-allocation

Network trust

what's this?

RPKI hygiene: F how networks compare →

12.5% of checked blocks have valid RPKI ROA coverage (1 of 8)

No discrepancies found among checked blocks.

NIC Handles

AS50473