SERVERPLAN

BGP inherited
Cluster stats
Netblocks10 · 10,230 IPv4 addresses
All fragments 13 blocks across 4 clusters
Cluster ID209628871
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
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-07-19

Domains hosted in this network

what's this?

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
46.16.88.0/22 SERVERPLAN RIPE ASSIGNED PA ● low
46.16.92.0/22 SERVERPLAN RIPE ASSIGNED PA ● low
46.28.0.0/22 SERVERPLAN RIPE ASSIGNED PA ● low
46.28.4.0/22 SERVERPLAN RIPE ASSIGNED PA ● low
46.30.240.0/22 SERVERPLAN RIPE ASSIGNED PA ● low
46.30.244.0/22 SERVERPLAN RIPE ASSIGNED PA ● low
46.254.32.0/22 SERVERPLAN RIPE ASSIGNED PA ● low
46.254.36.0/22 SERVERPLAN RIPE ASSIGNED PA ● low
93.95.216.0/22 SERVERPLAN RIPE ASSIGNED PA ● low
93.95.220.0/22 SERVERPLAN RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “SERVERPLAN” — 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.
  • Serverplance via Serverplance Bilisim Ve Telekomunikasyon Hizm. Ltd. Sti. sub-allocation

Network trust

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

NIC Handles

DUMY-RIPE DUMY-RIPE SERVERPLAN-MNT