ERPC Upgrades Its Solana RPC, WebSocket, and Geyser gRPC Infrastructure at Scale — Live Application Performance Improves Significantly in Real-World Comparison with a Major External RPC Service
ERPC Upgrades Its Solana RPC, WebSocket, and Geyser gRPC Infrastructure at Scale — Live Application Performance Improves Significantly in Real-World Comparison with a Major External RPC Service
ELSOUL LABO B.V. (Headquarters: Amsterdam, the Netherlands; Representative Director and CEO: Fumitake Kawasaki) and Validators DAO, the operators of ERPC, are pleased to announce a major upgrade across ERPC’s Solana RPC, WebSocket, and Solana Geyser gRPC infrastructure.
This upgrade adds a top-tier high-capacity node and improves Solana RPC, WebSocket, Geyser gRPC, internal gateway, real-time data delivery adapters, network software, and server configuration as a unified system. Based on accumulated data from load patterns, subscription behavior, method-level usage, and latency factors frequently observed in live applications, ERPC has improved performance along paths that are close to real production usage.
In a real-world comparison from the same Frankfurt client environment against a major external RPC service, ERPC showed strong performance across multiple metrics that matter for live applications, including median HTTP getSlot latency, WebSocket connection time, initial notification time for WebSocket transactionSubscribe-compatible functionality, slot freshness, and errors.
This improvement is not limited to a specific new plan. It will be rolled out progressively across ERPC’s Solana RPC and Solana Geyser gRPC-related plans. The impact is especially significant for Solana RPC and Geyser gRPC usage, and ERPC is applying the improvements confirmed in Frankfurt to other regions step by step.
ERPC Dashboard: https://dashboard.erpc.global/en
ERPC Website: https://erpc.global/en
Real-world comparison with a major external RPC service shows significant improvement for live applications
This comparison was conducted from the same Frankfurt client environment, measuring ERPC and a major external RPC service under the same conditions. The test focused on paths that directly affect live application experience, including HTTP getSlot, WebSocket slotSubscribe, and WebSocket transactionSubscribe-compatible functionality.
In representative results, median HTTP getSlot latency was 23.4ms on ERPC and 39.9ms on the major external RPC service, making ERPC approximately 1.7 times faster. WebSocket connection time was 87ms on ERPC and 157ms on the major external RPC service, making ERPC approximately 1.8 times faster. For the initial notification of WebSocket transactionSubscribe-compatible functionality, ERPC recorded 240ms, while the major external RPC service recorded 556ms, making ERPC approximately 2.3 times faster.
For live Solana applications, simple average latency is not enough. Connection establishment, initial notification time, real-time subscription stability, slot freshness, and the absence of errors are all important. In particular, for on-chain event detection, trading applications, monitoring systems, alert delivery, analytics infrastructure, bots, and backend APIs, how quickly the first notification arrives and how consistently data can be received after a subscription starts directly affect when downstream processing can begin.
In this comparison, ERPC and the major external RPC service observed the same slot for processed and confirmed getSlot freshness. In WebSocket slotSubscribe as well, both services observed the same slot at the same time. ERPC showed an advantage in connection speed while maintaining the same slot freshness. The number of errors was 0 on both sides.
Improving HTTP, WebSocket, and Geyser gRPC as one integrated system
This upgrade is not merely the result of adding another server. ERPC reviewed and improved the HTTP path for Solana RPC, the WebSocket path, the Geyser event path, internal gateway, real-time data conversion adapters, delivery processes, and network software as one integrated system.
In production Solana applications, fast HTTP RPC alone is not sufficient. The actual application experience can change significantly when WebSocket connections are slow, initial notifications are delayed, real-time subscription throughput does not scale, latency appears during conversion from Geyser gRPC to WebSocket-compatible layers, or backend processing becomes congested under high load.
ERPC does not treat HTTP, WebSocket, and Geyser gRPC as isolated features. Instead, ERPC improves them as a continuous path that receives, processes, delivers, and exposes Solana data to applications. The large node addition, network software improvements, gateway improvements, WebSocket adapter improvements, and Geyser gRPC path optimization in this upgrade are based on that integrated approach.
Geyser gRPC path and WebSocket adapter improvements strengthen initial notification performance
One area where this upgrade showed especially strong results is the combination of the Geyser gRPC path and WebSocket adapter. ERPC provides real-time data received as Geyser events in a form that is also easier to use through a WebSocket-compatible layer.
In the Frankfurt same-client comparison of transactionSubscribe-compatible functionality, ERPC recorded an initial notification time of 240ms with 0 errors. The major external RPC service recorded an initial notification time of 556ms with 0 errors. ERPC was approximately 2.3 times faster in initial notification time, while continuous delivery performance was also confirmed to be at an equal or higher level.
This result cannot be explained by network distance alone. In Solana real-time data delivery, final arrival performance is determined by the combination of node performance, Geyser gRPC handling, gateway processing, WebSocket conversion, queue handling, fanout architecture, and network software efficiency. ERPC continues to improve these components based on daily load trends and real measurement results.
Faster connection and initial notification while maintaining slot freshness
When improving speed, it is also important to confirm that a service is not simply returning stale data more quickly. In this comparison, ERPC and the major external RPC service observed the same slot for processed and confirmed getSlot freshness, which are the levels primarily used by live applications.
In WebSocket slotSubscribe as well, both services observed the same slot at the same time. ERPC showed an advantage in connection speed while maintaining the same slot freshness. WebSocket slotSubscribe connection time was 87ms on ERPC and 157ms on the major external RPC service, making ERPC approximately 1.8 times faster to connect.
At the same time, RPC and WebSocket performance can vary depending on region, time of day, client location, subscription conditions, and load conditions. ERPC separately tracks median, p95, maximum values, initial notification time, throughput, slot freshness, and error rate, and continuously improves the metrics that matter in real-world usage. This upgrade is a major step forward, but ERPC will continue improving across regions, methods, and workloads instead of treating a single result as the endpoint.
Expanded coverage for WebSocket / RPC-compatible layers, including Burst
In addition to performance improvements, this upgrade also expands method coverage in the WebSocket / RPC-compatible layers around Geyser gRPC-related endpoints, including Burst.
As examples, support has been added for standard confirmation and status methods such as getVersion, getSlot, getBlockHeight, getLatestBlockhash, and isBlockhashValid. This makes the environment easier to use not only for real-time subscriptions, but also for surrounding status checks and auxiliary requests.
ERPC is not a static service that only offers a fixed feature table. ERPC continuously expands coverage based on the methods, subscription conditions, queries, and application requirements that users actually need. If you encounter an issue with a specific method, request, subscription condition, WebSocket-compatible feature, or Geyser gRPC usage pattern, please create a support ticket through the Validators DAO Official Discord. By sharing the specific request, expected behavior, error details, and usage context, you can help inform future compatibility expansion and improvements.
Progressive rollout across Solana RPC and Geyser gRPC-related plans
This improvement is not limited to a specific dedicated configuration. ERPC will progressively apply it across all regions for Solana RPC, WebSocket, and Solana Geyser gRPC-related plans.
In Frankfurt, ERPC has already confirmed major improvements in the real-world comparison with a major external RPC service. From here, ERPC will apply these improvements to all regions step by step, while continuing to tune each region based on usage patterns, load trends, network paths, and server configuration.
ERPC’s strength is not limited to one-off feature additions. It lies in continuously improving existing plan performance, method coverage, delivery paths, and server configurations based on data obtained from real production usage. In Solana production environments, network conditions, traffic, method usage, subscription volume, and regional demand are constantly changing. ERPC continues to evolve as a Solana-specialized platform that improves alongside these changes.
Applying same-client measurements to continuous improvement
ERPC also uses measurements obtained from external service comparisons as input for continuous improvement. In this test, ERPC separately measured HTTP getSlot, WebSocket connection time, initial notification time for WebSocket transactionSubscribe-compatible functionality, slot freshness, and errors from the same Frankfurt client environment.
Solana RPC and WebSocket performance can vary depending on region, client location, subscription conditions, methods, time of day, load conditions, and backend configuration. For this reason, ERPC focuses not only on a single average value, but also on metrics that affect when real application processing can begin, including connection establishment, initial notification time, slot freshness, and error rate.
What matters for users is whether the data required by their application arrives with the required speed and stability. ERPC continues to improve practical performance by operating Solana RPC, WebSocket, Geyser gRPC, Shredstream, VPS, and bare metal servers on the same Solana-specialized platform.
Free trials for eligible plans and testing with real workloads
Free trials are currently available for eligible plans. Users can check eligible plans from the ERPC Dashboard and test the improvements to Solana RPC, WebSocket, and Geyser gRPC infrastructure under conditions close to their actual workloads.
For Solana applications, benchmark numbers alone are not enough. The optimal configuration depends on which methods the application uses, which region the client connects from, how much subscription volume is required, whether initial notification time is the priority, whether throughput is the priority, and how important slot freshness is for the workload.
From the ERPC Dashboard, users can review plans including Solana RPC, WebSocket, and Solana Geyser gRPC, and adopt the configuration that matches their current needs. Existing ERPC users can also verify response speed, subscription performance, and supported methods in their current workloads after the improvements are reflected in their environment.
ERPC Dashboard: https://dashboard.erpc.global/en
Continuous improvement as Solana-specialized infrastructure
ERPC does not provide Solana RPC as a simple API endpoint alone. ERPC improves it as infrastructure that supports the execution quality of Solana applications. In Solana, HTTP RPC, WebSocket, Geyser gRPC, Shredstream, SWQoS, server placement, validator quality, network paths, and processing node performance directly affect application speed and stability.
ELSOUL LABO has been approved for the Dutch government’s WBSO research and development support program for five consecutive years since 2022. The company continues research and development related to Solana RPC infrastructure, validator operations, real-time data delivery, and AI agent-based development and operations support. The results are reflected across ERPC, SLV, SLV AI, the AS200261 Solana-specialized data center, and related services.
This major upgrade is also part of that continuous research and development. Through the addition of high-performance large nodes, network software improvements, gateway improvements, WebSocket adapter improvements, Geyser gRPC path improvements, and expanded method coverage, ERPC is further strengthening the infrastructure performance required by live Solana applications.
ERPC will continue improving Solana-specialized infrastructure across Solana RPC, WebSocket, Solana Geyser gRPC, Solana Shredstream, VPS, and bare metal servers. ERPC will continue providing an environment where users can handle more Solana data, faster and more reliably, and where developers can focus on application development and production operations.
Contact
For inquiries about Solana RPC, WebSocket, Solana Geyser gRPC, Burst, supported methods, free trials, existing plans, regions, benchmarks, or configuration consultation, please create a support ticket through the Validators DAO Official Discord.
If you encounter an issue with a specific method, subscription condition, query, WebSocket-compatible feature, or Geyser gRPC usage pattern, please include the specific request and expected behavior when contacting us. ERPC continues to improve coverage and performance based on real user requirements.
ERPC Dashboard: https://dashboard.erpc.global/en
ERPC Website: https://erpc.global/en
Validators DAO Official Discord: https://discord.gg/C7ZQSrCkYR
News
