ERPC Implements a Global Update to Shared Solana RPC and gRPC Endpoints

ELSOUL LABO B.V. (Headquarters: Amsterdam, Netherlands; CEO: Fumitake Kawasaki) and Validators DAO have applied a large-scale update across all regions to our shared Solana RPC and gRPC endpoints. We reviewed node data retention and delivery operations so the endpoints now respond faster while holding a wider range of data.

Thank you, as always, for your strong support.

We focused on raising both stability and speed for shared endpoints, advancing a combined redesign of data retention and adjustments to the delivery pipeline. We added operational optimizations that suppress drop-offs during peak hours and reduce unnecessary re-fetches caused by round trips.

This update was rolled out horizontally across all regions. By handling a broader window of historical and latest data with headroom, responsiveness improves. Even if your previous trial did not meet requirements at the time, results change with this update. We encourage you to test again.

Re-fetches decrease. By revising delivery behavior and suppressing redundant retrieval of identical data, total round-trip time shortens. Because responses are served from a wider retained set, the path from query to answer becomes shorter, and there is a clear difference in real-world latency.

Edge-case data loss decreases. With increased retention and tuned operations, drop-offs during peak hours become less likely. As a result, application-side patching and re-sync frequency go down.

Responsiveness improves. Additional headroom combined with a more efficient delivery path shortens latency tails. Even on shared endpoints, processing variance narrows with this update and a wider range of queries is handled reliably. If your workload requires ultra-low latency, we will guide you to dedicated endpoints, but first confirm the results on the latest shared endpoints.

Update Regions:

Frankfurt, Amsterdam, and New York have dense validator populations and high-quality network infrastructure, so this improvement is especially effective there. Because Solana leaders rotate from moment to moment, putting “receive near, send near” into practice changes results for both latency and stability.

This is why regions with many validators are consistently popular.

Rather than fixating on a single competitive city, a multi-region strategy is highly effective. Receiving from the location closest to the current leader and sending from the region of the next leader works well even with shared endpoints. Operating multiple points of presence increases the share of time you are physically close to the leader (for example, by covering Amsterdam, Frankfurt, and New York, you can cover roughly 50% overall). With your own infrastructure, you can bypass additional hops and make proactive handoffs. Because this update strengthened the shared foundation, the multi-region approach is now an even more cost-effective choice.

Our strength is not only providing shared RPC and shared gRPC, but also placing VPS instances on the same network. Simply co-locating your application with the endpoints avoids public-internet jitter and shortens round-trip distance, cutting latency significantly. Our engineering team understands Solana, networking, and cloud design, and supports you end-to-end from requirements to operations.

With this update, shared RPC further improves both stability and response speed. By switching to an operation that retains a wider body of data, you gain headroom to return results even during peak hours. We recommend re-evaluating requirements that previously could not be met with the latest shared RPC.

In Asia, we plan to add nodes in Tokyo, Singapore, and Sydney. Hong Kong is also a candidate, with expansion targeted for this year or next. There are many developers in the region, yet the number of RPC options remains limited and environments are not fully prepared. We will provide RPC infrastructure that developers can rely on in Asia and contribute to the growth of the global Solana ecosystem.

Shared gRPC has been tuned in the same way. By revising retention and operational procedures, we suppress fine-grained jitter inherent to continuous streaming. Reduced re-fetch and fewer data drop-offs raise the stability of long-running processing. When combined with the shared RPC improvements, cumulative latency across the application and re-sync incidence drop further.

VPS instances can be placed on the same network as the endpoints. Because networks are typically much slower than CPU and memory, simply reducing network distance by co-locating the application removes a major bottleneck in total latency. Pairing the improved shared RPC and shared gRPC with nearby VPS yields even lower latency and higher stability. If you are unsure about cloud design, we will propose the shortest path from both network and infrastructure perspectives.

For inquiries and evaluation environments, contact us below. Free trials are available.