# Commercial P2P Repeater Service for EU Validators — Datavex Infrastructure

**URL:** <https://forum.algorand.co/t/commercial-p2p-repeater-service-for-eu-validators-datavex-infrastructure/15217>\
**Category:** General\
**Tags:** mainnet, noderunner\
**Created:** [March 17, 2026, 9:31am UTC](https://forum.algorand.co/t/commercial-p2p-repeater-service-for-eu-validators-datavex-infrastructure/15217 "2026-03-17T09:31:57Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![datavex](https://avatars.discourse-cdn.com/v4/letter/d/5f8ce5/32.png) [@datavex](https://forum.algorand.co/u/datavex)\
**Post date:** [March 17, 2026, 9:31am UTC](https://forum.algorand.co/t/commercial-p2p-repeater-service-for-eu-validators-datavex-infrastructure/15217/1 "2026-03-17T09:31:57Z")

</div>

_Hi Algorand community,_  
My name is Marcin and I run **Datavex** , an infrastructure company based in Poland. I want to introduce a service we have just launched and get feedback from the node runner community.  
What we built  
We operate dedicated P2P repeater nodes for **Algorand** validators. Our first node is live in Warsaw, Poland, with more European locations coming. The service is aimed at validators running in P2P Hybrid or pure P2P mode who want a guaranteed, low-latency, private path to the network instead of relying on random DHT-discovered peers.  
Why we built it  
When a validator runs in Hybrid mode it auto-discovers repeaters via Bootstrap DNS and Kademlia DHT. That works, but you have no control over where you land. You could connect to an overloaded node, a node on another continent, or a community node with no monitoring and no SLA. For validators with serious stake that is a real risk — latency directly affects consensus vote timing.  
We wanted to offer something the free alternatives cannot: a dedicated slot, a known location, a fallback node, and someone accountable if something goes wrong.  
What the service includes

Dedicated P2P repeater access with IP whitelisting — your validator IP is the only one on your slot  
Fallback node in the same location — if the primary goes down your validator automatically switches to standby with zero config change  
Central European location (Warsaw live now, more EU locations expanding)  
Native libp2p — fully compatible with current Hybrid mode and the Q3 2026 full P2P transition  
99.9% uptime SLA with 24/7 monitoring  
Setup in under 60 seconds — one line added to config.json

**Plans**

Starter €19.99/mo — single node, 1 validator IP  
Standard €34.99/mo — primary + fallback node, 1 validator IP

**Test before you buy**  
You can run our latency check directly from your validator server — no registration or port access needed:

bash: `curl -s ``https://status.datavex.tech/check-latency.sh`` | bash`

This pings our Warsaw node 10 times from your machine and gives you a clear latency result so you know exactly what to expect before subscribing.  
A question for the community  
We want to make sure we are operating in the spirit of what the Foundation and community expect from P2P repeater infrastructure. A few things we would genuinely like input on:

Are there technical guidelines or recommended configurations for commercial repeater operators we should be following beyond the official docs?  
Is the Foundation planning any kind of registry or visibility channel for community and commercial repeater operators as the P2P transition progresses?  
Are there other EU-based node runners who would find value in this service or want to collaborate on expanding coverage?

Happy to answer any questions, share technical details about the setup, or discuss the service further. This is a new space and we want to build it the right way.

Thanks for reading.

Marcin  
Datavex  
office@datavex.eu  
website: [DataVex - Node & Server Hosting | Built for Blockchain](https://datavex.eu/services/)  
node status: [https://status.datavex.tech](https://status.datavex.tech)
