Lily Network

Data as of 2026-07-26
BGP inherited
Cluster stats
Netblocks11
IPv6 11 prefixes (largest 2406:840:9ef0::/44)
All fragments 13 blocks across 3 clusters
Cluster ID213850522
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
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 · report an issue

Footprint over time

6 weekly snapshots · JSON
11 -1 netblocks since 2026-07-05
2026-07-05 peak 12 2026-07-26

IP Ranges (11)

⬇ 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
2404:f4c0:f70e:1980::203:236/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

IPv6 ranges (11)

Network trust

what's this?
RPKI hygiene: C how networks compare →
54.5% of checked blocks have valid RPKI ROA coverage (6 of 11)
Possible discrepancies (1)

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

NIC Handles

AS203236 LE106-AP LE106-AP MAINT-NBDHM-CN