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
24h window · 24 hours observed · generated 2026-08-26 22:54:10 UTC
| Metric | Tenderly | NodeReal | Merkle |
|---|---|---|---|
| Rank | 2 | 4 | 6 |
| Score | 98.8 | 86.6 | 78.0 |
| Status | Excellent | Good | Good |
| Availability | 99.97% | 100.00% | 100.00% |
| p50 latency | 19.8 ms | 87.4 ms | 107.0 ms |
| p95 latency | 37.4 ms | 100.1 ms | 196.1 ms |
| p99 latency | 256.8 ms | 124.6 ms | 241.2 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.35 blocks | 0.46 blocks |
| Rate limited | 0 | 0 | 6,228 |
| Unsupported | 0 | 0 | 81 |
| Samples | 38,751 | 38,070 | 8,993 |
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
+12.2points
- Latency+12.4
- Head freshness−0.2
- Availability−0.0
- Correctness−0.0
The parts add to +12.2, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+20.8points
- Latency+20.9
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +20.8, exactly — the score is a weighted sum, so it comes apart.