SSCS B.V.

Data as of 2026-08-23
BGP inherited
Cluster stats
Netblocks11 · 1,029 IPv4 addresses
IPv6 5 prefixes (largest 2001:13c7:6004::a505:2389:1/128)
Registered in Netherlands (2) · BQ (1) · CW (1) · France (1) · United States (1)
Cluster ID229143947
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

Footprint over time

9 weekly snapshots · JSON
11 -5 netblocks since 2026-07-05
2026-07-05 peak 18 2026-08-23

IP Ranges (11)

⬇ export CSV
CIDR Org name Registry Status Confidence
80.249.208.91/32 SSCS B.V. PEERINGDB ASSIGNED ● high
93.187.109.174/32 SSCS B.V. PEERINGDB ASSIGNED ● high
149.112.32.8/32 SSCS B.V. PEERINGDB ASSIGNED ● high
200.0.20.7/32 SSCS B.V. PEERINGDB ASSIGNED ● high
206.41.108.221/32 SSCS B.V. PEERINGDB ASSIGNED ● high
2001:504:40:108::1:221/128 SSCS B.V. PEERINGDB ASSIGNED ● high
2001:504:118::8/128 SSCS B.V. PEERINGDB ASSIGNED ● high
2001:7f8:1::a505:2389:1/128 SSCS B.V. PEERINGDB ASSIGNED ● high
2001:13c7:6004::a505:2389:1/128 SSCS B.V. PEERINGDB ASSIGNED ● high
2a02:4b60::a505:2389:1/128 SSCS B.V. PEERINGDB ASSIGNED ● high
190.123.16.0/22 SSCS BV LACNIC ALLOCATED ● low

IPv6 ranges (5)

Network trust

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

These blocks are registered to SSCS B.V. 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.

190.123.16.0/22 /22 authorized for AS52389 — AS52389

NIC Handles

AS52389 BQ-SSBV-LACNIC BVB BVB BVB