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 · 3.0 days observed · generated 2026-08-27 19:46:55 UTC
| Metric | Tenderly | NodeReal | Merkle |
|---|---|---|---|
| Rank | 2 | 4 | 6 |
| Score | 97.0 | 87.5 | 78.4 |
| Status | Excellent | Good | Good |
| Availability | 99.97% | 99.84% | 99.98% |
| p50 latency | 19.8 ms | 87.4 ms | 106.9 ms |
| p95 latency | 49.0 ms | 100.0 ms | 195.5 ms |
| p99 latency | 725.1 ms | 125.8 ms | 242.2 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.50 blocks | 0.35 blocks | 0.49 blocks |
| Rate limited | 0 | 0 | 18,483 |
| Unsupported | 0 | 0 | 225 |
| Samples | 115,231 | 113,287 | 26,686 |
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
+9.5points
- Latency+9.6
- Head freshness−0.2
- Availability+0.1
- Correctness−0.0
The parts add to +9.5, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+18.6points
- Latency+18.6
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +18.6, exactly — the score is a weighted sum, so it comes apart.