Providers
Compare RPC providers on measured data
The top 4 on the chosen chain are compared by default. Pick your own — up to 4 — and the selection moves into the URL, so a comparison can be sent to someone else and they will see exactly what you saw.
Providers on Ethereum
Side by side
24h window · 24 hours observed · generated 2026-08-27 12:00:07 UTC
| Metric | dRPC | NodeReal | Merkle |
|---|---|---|---|
| Rank | 3 | 4 | 6 |
| Score | 90.3 | 86.4 | 77.8 |
| Status | Excellent | Good | Good |
| Availability | 99.92% | 100.00% | 100.00% |
| p50 latency | 34.2 ms | 87.2 ms | 106.9 ms |
| p95 latency | 73.2 ms | 100.2 ms | 193.9 ms |
| p99 latency | 173.2 ms | 128.8 ms | 235.0 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.38 blocks | 0.34 blocks | 0.51 blocks |
| Rate limited | 155 | 0 | 5,945 |
| Unsupported | 0 | 0 | 70 |
| Samples | 36,655 | 36,642 | 8,525 |
9 providers scored against each other.
Where the gap comes from
Two scores side by side say one is higher. This says why: the score is a weighted sum, so it comes apart, and each component’s share of the difference adds back to the difference exactly. Compared against dRPC, the highest scorer of those selected.
dRPCvsNodeReal
+3.9points
- Latency+4.0
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +3.9, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+12.5points
- Latency+12.4
- Head freshness+0.2
- Availability−0.0
- Correctness−0.0
The parts add to +12.5, exactly — the score is a weighted sum, so it comes apart.