XiaoLi Network

Data as of 2026-10-11
BGP inherited
This organisation
Netblocks13
IPv6 13 prefixes (largest 2001:7f8:aa::221/128)
Record ID246759878
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (13)

⬇ export CSV
CIDR Org name Registry Status Confidence
2001:7f8:aa::221/128 XiaoLi Network PEERINGDB ASSIGNED ● high
2602:f429:31::22/128 XiaoLi Network PEERINGDB ASSIGNED ● high
2602:f92a:1315:1::10/128 XiaoLi Network PEERINGDB ASSIGNED ● high
2602:f92a:1315:2::39/128 XiaoLi Network PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:7::16b/128 XiaoLi Network PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:9::142/128 XiaoLi Network PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:10::1bc/128 XiaoLi Network PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:11::209/128 XiaoLi Network PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:14::14e/128 XiaoLi Network PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:16::146/128 XiaoLi Network PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:24::252/128 XiaoLi Network PEERINGDB ASSIGNED ● high
2a0f:1cc7:fff0:1::21/128 XiaoLi Network PEERINGDB ASSIGNED ● high
2a0f:7803:fc60:aaaa::2017:5/128 XiaoLi Network PEERINGDB ASSIGNED ● high

IPv6 ranges (13)

Footprint over time

16 weekly snapshots · JSON
13 +5 netblocks since 2026-07-05
2026-07-05 peak 13 2026-10-11

Network trust

what's this?
RPKI hygiene: D how networks compare →
23.1% of checked blocks have valid RPKI ROA coverage (3 of 13)
No discrepancies found among checked blocks.

NIC Handles

AS201705