Solana infrastructure in the EU
Run outside the usual European clusters.
Nearly half of all Solana mainnet stake sits in just two metros – Frankfurt and Amsterdam. We place nodes in Tallinn, Estonia: a distinct location on our own AS214132 network, under Estonian and EU law.
A different point on the map
Physical and network distance from the crowded FRA/AMS core for operators who want their placement decoupled from dominant clusters.
EU-sovereign jurisdiction
Infrastructure operated under Estonian and EU law. No US CLOUD Act exposure or hyperscaler dependency.
Our own network, AS214132
You sit behind 3NV's own autonomous system with 2 × 25 Gbps uplinks on listed configurations.
Solana stake by location
Metros aggregated across ASNs. Source: validators.app, Solana mainnet.
≈47%
of stake in Frankfurt + Amsterdam
12.4%
in a single Frankfurt data center
0.1%
of the network is in Estonia
A placement option for concentration limits.
The Solana Foundation Delegation Program evaluates validators against infrastructure concentration thresholds. A distinct Tallinn location on AS214132 sits outside the crowded metros – you remain responsible for verifying current eligibility.
Official criteria≤15%
Data center concentration
Stake at a data center provider must remain within the program threshold.
≤25%
ASN/company concentration
Stake on an ASN or hosting provider must remain within the program threshold.
Solana-ready bare metal.
The machines we recommend for Solana workloads, whether you are running a validator, an RPC node, or an indexer: EPYC cores, DDR5 RAM, local NVMe, and 100 TB traffic.
AMD EPYC 9254
A solid starting point for new validators getting their first node voting.
- Cores
- 24c / 48t
- Clock
- 2.9 / 4.15 GHz
- RAM
- 384 GB DDR5
- NVMe
- 2 × 1 TB + 2 × 4 TB
- Traffic
- 100 TB
- Uplink
- 2 × 25 Gbps
AMD EPYC 9274F
High-frequency cores for established validators pushing for a higher score.
- Cores
- 24c / 48t
- Clock
- 4.1 / 4.3 GHz
- RAM
- 384 GB DDR5
- NVMe
- 2 × 1 TB + 2 × 4 TB
- Traffic
- 100 TB
- Uplink
- 2 × 25 Gbps
Running RPC or indexing? Those workloads want more than the default 384 GB of memory – talk to an engineer about an upgraded configuration, and we will validate the shape before you commit.
What fits on this infrastructure.
One hardware profile covers the Solana stack. Anything that needs consistent CPU, fast local storage, and predictable traffic costs runs here.
Validators
Run Agave or Jito-Solana with full root access, local NVMe for the ledger and accounts DB, and IPMI/KVM on request.
RPC nodes
Serve high-traffic Solana RPC on dedicated hardware, best paired with a memory upgrade beyond the default 384 GB.
Yellowstone Geyser
Use local NVMe and private networking for Geyser plugin pipelines, downstream consumers, and low-jitter data paths.
Indexers & archive
Keep indexers, archive nodes, and replay-heavy workloads close to fast local NVMe, with no shared I/O queues in the path.
Web3 teams already build on 3NV.
Blockchain and on-chain data companies run production infrastructure with us today. Solana validators join an environment already tuned for demanding Web3 workloads.
Swyke
Blockchain infrastructure.
indexing.co
On-chain data indexing at scale.
Why dedicated servers for Solana?
Solana nodes are demanding and unforgiving of shared infrastructure. Dedicated hardware removes the variables you cannot control on a multi-tenant cloud.
Solana infrastructure FAQ
Direct answers for Solana teams evaluating 3NV.