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 15:27:08 UTC
| Metric | Tenderly | NodeReal | Merkle |
|---|---|---|---|
| Rank | 1 | 4 | 6 |
| Score | 99.4 | 82.9 | 70.9 |
| Status | Excellent | Good | Degraded |
| Availability | 99.98% | 100.00% | 100.00% |
| p50 latency | 20.2 ms | 87.6 ms | 110.0 ms |
| p95 latency | 33.8 ms | 99.3 ms | 191.4 ms |
| p99 latency | 64.8 ms | 126.3 ms | 290.6 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.33 blocks | 0.45 blocks |
| Rate limited | 0 | 0 | 1,387 |
| Unsupported | 0 | 0 | 15 |
| Samples | 8,850 | 8,682 | 2,056 |
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
+16.5points
- Latency+16.7
- Head freshness−0.2
- Availability−0.0
- Correctness+0.0
The parts add to +16.5, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+28.5points
- Latency+28.5
- Head freshness−0.0
- Availability−0.0
- Correctness+0.0
The parts add to +28.5, exactly — the score is a weighted sum, so it comes apart.