SYNEVO

BGP inherited
Cluster stats
Netblocks9
Registered in Poland (8) · MD (1)
All fragments 18 blocks across 8 clusters
Cluster ID210036483
RegistryRIPE
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

Footprint over time

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

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
5.226.124.224/28 SYNEVO RIPE ASSIGNED PA ● low
62.233.139.108/30 SYNEVO RIPE ASSIGNED PA ● low
81.219.230.164/30 SYNEVO RIPE ASSIGNED PA ● low
81.219.237.72/30 SYNEVO RIPE ASSIGNED PA ● low
85.128.74.128/30 SYNEVO RIPE ASSIGNED PA ● low
195.205.240.84/30 SYNEVO RIPE ASSIGNED PA ● low
213.216.109.144/30 SYNEVO RIPE ASSIGNED PA ● low
213.241.94.132/30 SYNEVO RIPE ASSIGNED PA ● low
217.12.123.192/29 Synevo-Net RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “SYNEVO” — 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.

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 NETIA-MNT ORANGE-MD-NOC TPNET