XLIS-OS2

BGP inherited
Cluster stats
Netblocks12 · 12,276 IPv4 addresses
All fragments 13 blocks across 2 clusters
Cluster ID205293607
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

4 weekly snapshots · JSON
12 0 netblocks since 2026-07-05
2026-07-05 peak 12 2026-07-13

IP Ranges (12)

⬇ export CSV
CIDR Org name Registry Status Confidence
81.4.84.0/22 XLIS-OS2 RIPE ASSIGNED PA ● low
83.96.200.0/22 XLIS-OS2 RIPE ASSIGNED PA ● low
83.96.212.0/22 XLIS-OS2 RIPE ASSIGNED PA ● low
83.96.216.0/22 XLIS-OS2 RIPE ASSIGNED PA ● low
83.96.220.0/22 XLIS-OS2 RIPE ASSIGNED PA ● low
83.96.236.0/22 XLIS-OS2 RIPE ASSIGNED PA ● low
83.96.240.0/22 XLIS-OS2 RIPE ASSIGNED PA ● low
83.96.244.0/22 XLIS-OS2 RIPE ASSIGNED PA ● low
83.96.252.0/22 XLIS-OS2 RIPE ASSIGNED PA ● low
85.10.176.0/22 XLIS-OS2 RIPE ASSIGNED PA ● low
85.10.184.0/22 XLIS-OS2 RIPE ASSIGNED PA ● low
85.10.188.0/22 XLIS-OS2 RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “XLIS OS2” — 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: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (12 of 12)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE XLIS-NL-MNT XLIS-RIPE