OPTOSUNET

BGP inherited
Cluster stats
Netblocks7 · 3,098 IPv4 addresses
All fragments 8 blocks across 2 clusters
Cluster ID209263934
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

5 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-19

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
130.242.55.0/24 OPTOSUNET RIPE LEGACY ● low
130.242.56.224/27 OPTOSUNET RIPE LEGACY ● low
130.242.80.0/24 OPTOSUNET RIPE LEGACY ● low
130.242.82.0/24 OPTOSUNET RIPE LEGACY ● low
130.242.94.0/24 OPTOSUNET RIPE LEGACY ● low
130.242.112.0 – 130.242.119.0 OPTOSUNET RIPE LEGACY ● low
193.11.0.0/24 OPTOSUNET RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “OPTOSUNET” — 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.
  • OPTOSUNET-2 via Vetenskapsradet / SUNET sub-allocation

Network trust

what's this?
RPKI hygiene: F how networks compare →
14.3% of checked blocks have valid RPKI ROA coverage (1 of 7)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE SUNET-MNT