SIBNET-IPTV
Cluster stats
Netblocks7
All fragments 8 blocks across 2 clusters
Cluster ID192372216
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

2 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-06

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
87.103.132.0/25 SIBNET-IPTV RIPE ASSIGNED PA ● low
90.188.23.128/25 SIBNET-IPTV RIPE ASSIGNED PA ● low
90.189.121.0/25 SIBNET-IPTV RIPE ASSIGNED PA ● low
92.127.153.128/25 SIBNET-IPTV RIPE ASSIGNED PA ● low
195.112.230.0/24 SIBNET-IPTV RIPE ASSIGNED PA ● low
195.162.45.128/25 SIBNET-IPTV RIPE ASSIGNED PA ● low
213.210.72.128/25 SIBNET-IPTV RIPE ASSIGNED PA ● low

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (7 of 7)
Possible discrepancies (1)

These blocks are registered to SIBNET-IPTV 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.

195.112.230.0/24 /24 authorized for AS5573 — PJSC Rostelecom

NIC Handles

DUMY-RIPE DUMY-RIPE ROSTELECOM-MNT