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 10:16:51 UTC
| Metric | PublicNode | Merkle |
|---|---|---|
| Rank | 2 | 6 |
| Score | 99.0 | 69.9 |
| Status | Excellent | Degraded |
| Availability | 99.98% | 100.00% |
| p50 latency | 20.1 ms | 106.1 ms |
| p95 latency | 35.5 ms | 197.1 ms |
| p99 latency | 91.1 ms | 228.8 ms |
| Correctness | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.60 blocks |
| Rate limited | 0 | 1,321 |
| Unsupported | 0 | 18 |
| Samples | 8,612 | 1,968 |
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.
PublicNodevsMerkle
+29.0points
- Latency+28.9
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +29.0, exactly — the score is a weighted sum, so it comes apart.