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 · 2.4 days observed · generated 2026-08-27 06:17:38 UTC
| Metric | Tenderly | NodeReal | Merkle |
|---|---|---|---|
| Rank | 2 | 4 | 6 |
| Score | 94.8 | 88.3 | 78.8 |
| Status | Excellent | Good | Good |
| Availability | 99.97% | 99.80% | 99.98% |
| p50 latency | 19.8 ms | 87.3 ms | 106.5 ms |
| p95 latency | 62.4 ms | 99.9 ms | 195.7 ms |
| p99 latency | 837.4 ms | 124.3 ms | 244.4 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.50 blocks | 0.35 blocks | 0.47 blocks |
| Rate limited | 0 | 0 | 15,014 |
| Unsupported | 0 | 0 | 183 |
| Samples | 93,370 | 91,793 | 21,587 |
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 Tenderly, the highest scorer of those selected.
TenderlyvsNodeReal
+6.5points
- Latency+6.6
- Head freshness−0.2
- Availability+0.1
- Correctness−0.0
The parts add to +6.5, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+16.0points
- Latency+16.1
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +16.0, exactly — the score is a weighted sum, so it comes apart.