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
7d window · 2.2 days observed · generated 2026-08-27 01:54:24 UTC
| Metric | Tenderly | NodeReal | Merkle |
|---|---|---|---|
| Rank | 3 | 4 | 6 |
| Score | 93.7 | 89.1 | 79.2 |
| Status | Excellent | Good | Good |
| Availability | 99.96% | 99.78% | 99.98% |
| p50 latency | 19.9 ms | 87.4 ms | 106.6 ms |
| p95 latency | 72.0 ms | 99.9 ms | 195.9 ms |
| p99 latency | 878.0 ms | 123.6 ms | 243.1 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.51 blocks | 0.35 blocks | 0.46 blocks |
| Rate limited | 0 | 0 | 13,894 |
| Unsupported | 0 | 0 | 170 |
| Samples | 86,276 | 84,794 | 20,007 |
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
+4.7points
- Latency+4.8
- Head freshness−0.2
- Availability+0.1
- Correctness−0.0
The parts add to +4.7, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+14.6points
- Latency+14.7
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +14.6, exactly — the score is a weighted sum, so it comes apart.