SICK-REUTE-NET

Data as of 2026-08-16
BGP inherited
Cluster stats
Netblocks6
IPv6 3 prefixes (largest 2003:106:7013::/48)
Cluster ID223671988
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 · report an issue

Footprint over time

6 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-08-16

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.157.182.48/28 SICK-REUTE-NET RIPE ASSIGNED PA ● low
62.159.241.208/28 SICK-REUTE-NET RIPE ASSIGNED PA ● low
91.25.121.216/29 SICK-REUTE-NET RIPE ASSIGNED PA ● low
2003:53:2011::/48 SICK-REUTE-NET RIPE ASSIGNED ● low
2003:d2:f02e::/48 SICK-REUTE-NET RIPE ASSIGNED ● low
2003:106:7013::/48 SICK-REUTE-NET RIPE ASSIGNED ● low

IPv6 ranges (3)

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (6 of 6)
No discrepancies found among checked blocks.

NIC Handles

DTAG-NIC DUMY-RIPE DUMY-RIPE