ERPC Adds Amsterdam to Its Solana SWQoS Endpoint — the Second Region After Frankfurt, the Most Requested City, Now Assignable From the Dashboard

ELSOUL LABO B.V. (Headquarters: Amsterdam, Netherlands; CEO: Fumitake Kawasaki) and Validators DAO, which operate ERPC, are pleased to announce that ERPC has added a new Amsterdam (AMS) region to its Solana SWQoS Endpoint, which lets you use Solana's stake-weighted priority lane (SWQoS / Stake-Weighted QoS). It is the second region after Frankfurt (FRA), and it can be assigned and used right away from the ERPC Dashboard.

Amsterdam was the most requested region addition from our customers. It offers stake and leader slots on par with Frankfurt, while being less congested than Frankfurt — a more headroom-rich environment to run in.

ERPC Official Site: https://erpc.global/en ERPC Dashboard: https://dashboard.erpc.global/en

SWQoS (Stake-Weighted Quality of Service) is a mechanism that Solana provides officially. Under high-load TPU ingress processing, a leader allocates about 80% of its priority capacity to staked connections in proportion to their stake, while unstaked connections compete for the remaining ~20% of non-priority capacity. This 80 / 20 split is set by Solana's leaders, not by ERPC.

During moments when the ingress side gets crowded — memecoin launches, high-load blocks — packets in the 20% lane are the first to be dropped, while stake-backed connections are more likely to be prioritized on the leader's ingress side. Firing a transaction straight at the leader may feel like the fast move. But without stake, that route is also the crowded 20% lane. Under load, your transaction may not be sufficiently accepted by the leader, and as a result is less likely to make it into the block.

ERPC runs a top-tier staked validator in its Shinobi Performance Pool, wired into high-quality RPC lines and hardware placed right next to Solana. Transactions through the SWQoS Endpoint are handled in the leader's TPU ingress priority region in proportion to the stake behind them — and this takes effect on the ingress path that comes before Priority fee enters the picture. This is why the certainty of getting through under load changes substantially.

SWQoS is not a replacement for Priority fee; it is a path that raises the likelihood of reaching the leader's ingress side first, before Priority fee is evaluated. In real-world operation, it is important to combine the deliverability that SWQoS provides with appropriate Priority fee settings.

For more on how SWQoS works, see the SWQoS section on the ERPC official site.

Amsterdam was the most requested region addition. The reason is clear: what matters for SWQoS is how much stake and how many leaders are present in the region you connect to, and on this point Amsterdam meets conditions on par with Frankfurt. Amsterdam is a region with stake and leader slots equivalent to Frankfurt.

On top of that, Amsterdam is less congested than Frankfurt. With the same stake and leader conditions, you can run in a more headroom-rich environment. This — getting the same priority-lane conditions in a less crowded environment — is why Amsterdam is favored. For customers who had concentrated on Frankfurt, a new option has been added that lets them distribute without giving up those conditions.

The new Amsterdam SWQoS Endpoint can be assigned right away from the ERPC Dashboard. Just select Amsterdam as the region on the dashboard and assign the endpoint to start using it. New usage, of course, as well as switching from or running alongside an existing setup such as Frankfurt, can all be done from the same dashboard.

For plan and pricing details and usage conditions, please check the ERPC Dashboard and the pricing page.

ERPC Dashboard: https://dashboard.erpc.global/en

ERPC lets you combine Solana RPC, WebSocket, Solana Geyser gRPC, Solana Shredstream, Direct UDP Stream (Raw Shreds), VPS, bare-metal servers, dedicated RPC, SWQoS, a Pyth-enabled Price API, and Jet Analytics & Indexed RPC on a single platform.

The ERPC Dashboard supports 16 languages, letting you handle plan selection, region selection, stock checks, adding to cart, credit top-ups, checkout, reviewing API keys and endpoints, checking usage, and creating support tickets — all from the same screen.

Behind ERPC is the research and development of Solana-specific infrastructure that ELSOUL LABO continues to pursue. ELSOUL LABO has been approved for five consecutive years since 2022 under WBSO, the Netherlands' government R&D support program. It continues R&D on Solana RPC infrastructure, validator operations, real-time data delivery, and AI-agent-assisted operations and development, and those results are reflected across services including ERPC, SLV, SLV AI, and the AS200261 Solana-specific data center.

Today's Amsterdam region addition is not a one-off adjustment either, but a result that follows from this continuous research and development and from global expansion in response to customer requests. ERPC will continue to broaden the arrival quality and the supported regions of its Solana-specific infrastructure, including SWQoS.

For help with using the Amsterdam SWQoS Endpoint, selecting and assigning regions, switching from an existing configuration, or questions about SWQoS, please create a support ticket on the official Validators DAO Discord. We also always welcome requests for regions you would like added, and your feedback, on the same Discord. ERPC and Validators DAO have continued to improve and expand based on your requests.

ERPC Dashboard: https://dashboard.erpc.global/en ERPC Official Site: https://erpc.global/en Validators DAO Official Discord: https://discord.gg/C7ZQSrCkYR

We sincerely thank all of our users for their continued use of ERPC. We will keep expanding globally while responding to your requests.