SYN-NL-200

BGP inherited
Cluster stats
Netblocks16
Cluster ID205444557
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

4 weekly snapshots · JSON
16 0 netblocks since 2026-07-05
2026-07-05 peak 16 2026-07-13

IP Ranges (16)

⬇ export CSV
CIDR Org name Registry Status Confidence
43.239.88.0/23 SYN-NL-200 RIPE ASSIGNED PA ● low
43.239.90.0/23 SYN-NL-200 RIPE ASSIGNED PA ● low
103.206.232.0/23 SYN-NL-200 RIPE ASSIGNED PA ● low
103.206.234.0/23 SYN-NL-200 RIPE ASSIGNED PA ● low
107.181.156.0/22 SYN-NL-200 RIPE ASSIGNED PA ● low
155.254.40.0/22 SYN-NL-200 RIPE ASSIGNED PA ● low
155.254.44.0/22 SYN-NL-200 RIPE ASSIGNED PA ● low
155.254.50.0/23 SYN-NL-200 RIPE ASSIGNED PA ● low
155.254.52.0/22 SYN-NL-200 RIPE ASSIGNED PA ● low
155.254.56.0/22 SYN-NL-200 RIPE ASSIGNED PA ● low
185.135.212.0/23 SYN-NL-200 RIPE ASSIGNED PA ● low
185.135.214.0/23 SYN-NL-200 RIPE ASSIGNED PA ● low
198.105.96.0/22 SYN-NL-200 RIPE ASSIGNED PA ● low
198.105.104.0/22 SYN-NL-200 RIPE ASSIGNED PA ● low
2a02:2ca6::/32 SYN-NL-200 RIPE ASSIGNED ● low
2a02:2ca7::/32 SYN-NL-200 RIPE ASSIGNED ● low

Network trust

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

These blocks are registered to SYN-NL-200 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.

2a02:2ca6::/32 /32 authorized for AS43350 — NForce Entertainment B.V.
2a02:2ca7::/32 /32 authorized for AS43350 — NForce Entertainment B.V.

NIC Handles

DUMY-RIPE DUMY-RIPE MNT-SYN