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 07:27:43 UTC
| Metric | Tenderly | NodeReal | Merkle |
|---|---|---|---|
| Rank | 2 | 4 | 6 |
| Score | 98.5 | 79.9 | 70.0 |
| Status | Excellent | Good | Degraded |
| Availability | 100.00% | 100.00% | 100.00% |
| p50 latency | 18.4 ms | 87.4 ms | 105.1 ms |
| p95 latency | 32.0 ms | 105.2 ms | 193.2 ms |
| p99 latency | 68.3 ms | 141.9 ms | 268.8 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.35 blocks | 0.59 blocks |
| Rate limited | 0 | 0 | 1,395 |
| Unsupported | 0 | 0 | 15 |
| Samples | 8,840 | 8,718 | 1,970 |
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
+18.7points
- Latency+18.8
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +18.7, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+28.5points
- Latency+28.4
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +28.5, exactly — the score is a weighted sum, so it comes apart.