i LOL

iLOL
Registry
Cluster stats
Netblocks8
Registered in SI (3) · Austria (1)
All fragments 10 blocks across 2 clusters
Cluster ID209974167
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 8 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names 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
91.220.194.24/32 iLOL PEERINGDB ASSIGNED ● high
91.220.194.124/32 iLOL PEERINGDB ASSIGNED ● high
193.203.0.64/32 iLOL PEERINGDB ASSIGNED ● high
2001:7f8:30:0:2:1:19:8524/128 iLOL PEERINGDB ASSIGNED ● high
2001:7f8:46::19:8524/128 iLOL PEERINGDB ASSIGNED ● high
2001:7f8:46:0:1:0:19:8524/128 iLOL PEERINGDB ASSIGNED ● high
91.236.1.0/24 iLOL RIPE ASSIGNED PI ● medium
2001:67c:2730::/48 iLOL6 RIPE ASSIGNED PI ● medium

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “iLOL” — 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

AS198524 DUMY-RIPE DUMY-RIPE MEGA-M-MNT MNT-ILOL MNT-SGN ORG-id28-RIPE RIPE-NCC-END-MNT