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
30d window · 46 hours observed · generated 2026-08-26 18:54:47 UTC
| Metric | NodeReal | Tenderly | Merkle |
|---|---|---|---|
| Rank | 3 | 4 | 6 |
| Score | 88.6 | 87.8 | 78.4 |
| Status | Good | Good | Good |
| Availability | 99.75% | 99.96% | 99.97% |
| p50 latency | 87.4 ms | 20.0 ms | 106.6 ms |
| p95 latency | 100.0 ms | 104.5 ms | 196.1 ms |
| p99 latency | 123.6 ms | 952.4 ms | 244.4 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.35 blocks | 0.51 blocks | 0.46 blocks |
| Rate limited | 0 | 0 | 12,143 |
| Unsupported | 0 | 0 | 148 |
| Samples | 73,658 | 74,972 | 17,487 |
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 NodeReal, the highest scorer of those selected.
NodeRealvsTenderly
+0.8points
- Latency+0.7
- Head freshness+0.2
- Availability−0.1
- Correctness+0.0
The parts add to +0.8, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsMerkle
+10.2points
- Latency+10.2
- Head freshness+0.1
- Availability−0.1
- Correctness−0.0
The parts add to +10.2, exactly — the score is a weighted sum, so it comes apart.