INCOM-SERVICE-LAN
BGP inherited
Cluster stats
Netblocks9
All fragments 37 blocks across 12 clusters
Cluster ID192209516
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
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
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-06

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
79.142.84.128/27 INCOM-SERVICE-LAN RIPE ASSIGNED PA ● low
79.142.86.128/25 INCOM-SERVICE-LAN RIPE ASSIGNED PA ● low
85.114.4.252/30 INCOM-SERVICE-LAN RIPE ASSIGNED PA ● low
85.114.5.128/30 INCOM-SERVICE-LAN RIPE ASSIGNED PA ● low
85.114.5.196/30 INCOM-SERVICE-LAN RIPE ASSIGNED PA ● low
85.114.7.132/30 INCOM-SERVICE-LAN RIPE ASSIGNED PA ● low
85.114.9.168/30 INCOM-SERVICE-LAN RIPE ASSIGNED PA ● low
85.114.13.64/30 INCOM-SERVICE-LAN RIPE ASSIGNED PA ● low
85.114.23.204/30 INCOM-SERVICE-LAN 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 (9 of 9)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE OBIT-MNT