Lily Network
Cluster stats
Netblocks12
All fragments 24 blocks across 9 clusters
Cluster ID193389410
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 7 shared RIR contact/maintainer handles
Registry names 4 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (12)

⬇ export CSV
CIDR Org name Registry Status Confidence
2001:7f8:d0::3:19e4:1/128 Lily Network PEERINGDB ASSIGNED ● high
2001:7f8:d0:4742:0:3:19e4:1/128 Lily Network PEERINGDB ASSIGNED ● high
2001:7f8:d0:5553:0:3:19e4:1/128 Lily Network PEERINGDB ASSIGNED ● high
2406:840:1f:1000:0:20:3236:1/128 Lily Network PEERINGDB ASSIGNED ● high
2406:840:e240:1:2032:36::/128 Lily Network PEERINGDB ASSIGNED ● high
2602:f9f6:7f0:5:0:20:3236:1/128 Lily Network PEERINGDB ASSIGNED ● high
2a0a:280:f000:3:0:20:3236:0/128 Lily Network PEERINGDB ASSIGNED ● high
2a0e:b107:1b20::20:3236:1/128 Lily Network PEERINGDB ASSIGNED ● high
2a12:3fc2:aa12:cafe::101/128 Lily Network PEERINGDB ASSIGNED ● high
2406:840:9ef0::/44 Lily-Network-Asia APNIC ALLOCATED NON-PORTABLE ● low
2a0a:280:1500::/48 Lily-Network-TR RIPE ASSIGNED ● low
2a0a:280:1501::/48 Lily-Network-AR RIPE ASSIGNED ● low

Network trust

what's this?
RPKI hygiene: C how networks compare →
58.3% of checked blocks have valid RPKI ROA coverage (7 of 12)
Possible discrepancies (3)

These blocks are registered to Lily Network but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

2406:840:9ef0::/44 /44 authorized for AS203236 — Mingyang Shen
2a0a:280:1500::/48 /48 authorized for AS203236 — Mingyang Shen
2a0a:280:1501::/48 /48 authorized for AS203236 — Mingyang Shen

NIC Handles

AS203236 DUMY-RIPE DUMY-RIPE LE106-AP LE106-AP LILY-MNT MAINT-NBDHM-CN