eyeblaster

Registry

Cluster stats

Netblocks	6
All fragments	11 blocks across 5 clusters
Cluster ID	209024781
Registry	RIPE
Customers	find customers using this network →

Evidence & provenance ?

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

Footprint over time

3 weekly snapshots · JSON

6 0 netblocks since 2026-07-05

2026-07-05 peak 6 2026-07-12

IP Ranges (6)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
81.218.12.128/27	EYEBLASTER-LTD	RIPE	ASSIGNED PA	● low
82.80.118.224/28	EYEBLASTER-LTD	RIPE	ASSIGNED PA	● low
82.80.124.56/29	EYEBLASTER-LTD	RIPE	ASSIGNED PA	● low
192.114.168.16/29	eyeblaster	RIPE	ASSIGNED PA	● low
192.114.178.128/26	eyeblaster	RIPE	ASSIGNED PA	● low
192.117.176.16/28	eyeblaster	RIPE	ASSIGNED PA	● low

Possibly related to this organisation

what's this?

Same name family

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

EYEBLASTER-UK 2 blocks
Eyeblaster-Lan 1 blocks
Eyeblaster-WAN 1 blocks
Eyeblaster-WAN-LND 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.

Eyeblaster-Lan via Cellcom Fixed Line Communication L.P sub-allocation
Eyeblaster-WAN via Cellcom Fixed Line Communication L.P sub-allocation
Eyeblaster-WAN-LND via Cellcom Fixed Line Communication L.P 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

AS5486-MNT AS8551-MNT DUMY-RIPE DUMY-RIPE