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
6h window · 6.0 hours observed · generated 2026-08-27 09:12:46 UTC
| Metric | PublicNode | dRPC | Merkle |
|---|---|---|---|
| Rank | 1 | 3 | 6 |
| Score | 99.4 | 88.3 | 70.0 |
| Status | Excellent | Good | Degraded |
| Availability | 99.99% | 99.94% | 100.00% |
| p50 latency | 19.0 ms | 31.4 ms | 105.3 ms |
| p95 latency | 31.7 ms | 64.1 ms | 194.3 ms |
| p99 latency | 66.3 ms | 158.2 ms | 228.0 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.36 blocks | 0.61 blocks |
| Rate limited | 0 | 36 | 1,326 |
| Unsupported | 0 | 0 | 14 |
| Samples | 8,505 | 8,299 | 1,924 |
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 PublicNode, the highest scorer of those selected.
PublicNodevsdRPC
+11.1points
- Latency+11.3
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +11.1, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+29.4points
- Latency+29.2
- Head freshness+0.2
- Availability−0.0
- Correctness+0.0
The parts add to +29.4, exactly — the score is a weighted sum, so it comes apart.