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-26 22:50:06 UTC
| Metric | Tenderly | NodeReal | Merkle |
|---|---|---|---|
| Rank | 1 | 4 | 6 |
| Score | 99.4 | 82.2 | 70.7 |
| Status | Excellent | Good | Degraded |
| Availability | 99.99% | 100.00% | 100.00% |
| p50 latency | 19.5 ms | 87.3 ms | 108.3 ms |
| p95 latency | 35.5 ms | 99.5 ms | 192.3 ms |
| p99 latency | 69.3 ms | 124.8 ms | 234.1 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.50 blocks | 0.33 blocks | 0.41 blocks |
| Rate limited | 0 | 0 | 1,481 |
| Unsupported | 0 | 0 | 15 |
| Samples | 9,429 | 9,270 | 2,123 |
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
+17.2points
- Latency+17.4
- Head freshness−0.2
- Availability−0.0
- Correctness+0.0
The parts add to +17.2, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+28.7points
- Latency+28.8
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +28.7, exactly — the score is a weighted sum, so it comes apart.