phaeton

PHAETON

Registry

Cluster stats

Netblocks	6
Registered in	KZ (5) · Romania (1)
All fragments	42 blocks across 3 clusters
Cluster ID	208905822
Registry	RIPE
Customers	find customers using this network →

Evidence & provenance ?

Attribution	Registry record
Shared handles	clustered on 5 shared RIR contact/maintainer handles
Registry names	2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

4 weekly snapshots · JSON

6 0 netblocks since 2026-07-05

2026-07-05 peak 6 2026-07-13

IP Ranges (6)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
82.200.240.236/30	PHAETON	RIPE	ASSIGNED PA	● low
89.218.151.136/30	PHAETON	RIPE	ASSIGNED PA	● low
92.46.234.176/30	PHAETON	RIPE	ASSIGNED PA	● low
178.88.66.88/30	PHAETON	RIPE	ASSIGNED PA	● low
212.116.242.124/30	phaeton	RIPE	ASSIGNED PA	● low
213.233.119.96/27	phaeton	RIPE	ASSIGNED PA	● low

Possibly related to this organisation

what's this?

Same name family

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

PHAETON PLUS d.o.o 35 blocks
PHAETON-TAXI-NET 1 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.

PHAETON-TAXI-NET via Telefonica Germany GmbH & Co.OHG sub-allocation
TOOPHAETONDC via JSC Kazakhtelecom sub-allocation
TOOPHAETON via JSC Kazakhtelecom sub-allocation
TOOPHAETONKZ via JSC Kazakhtelecom sub-allocation

Network trust

what's this?

RPKI hygiene: A how networks compare →

100.0% of checked blocks have valid RPKI ROA coverage (6 of 6)

No discrepancies found among checked blocks.

NIC Handles

AS12302-MNT DUMY-RIPE DUMY-RIPE KNIC-MNT RATEL-MNT