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 03:57:54 UTC
| Metric | Tenderly | NodeReal | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 1 | 4 | 6 | 8 |
| Score | 99.4 | 86.6 | 77.7 | 58.7 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 100.00% | 99.99% | 100.00% | 76.33% |
| p50 latency | 18.9 ms | 86.8 ms | 105.0 ms | 2024.4 ms |
| p95 latency | 32.6 ms | 98.7 ms | 205.0 ms | 6590.4 ms |
| p99 latency | 69.6 ms | 117.4 ms | 263.5 ms | 9196.2 ms |
| Correctness | 100.00% | 99.99% | 100.00% | 96.63% |
| Head lag | 0.48 blocks | 0.33 blocks | 0.44 blocks | 0.95 blocks |
| Rate limited | 0 | 0 | 1,529 | 1,634 |
| Unsupported | 0 | 0 | 22 | 0 |
| Samples | 9,636 | 9,527 | 2,156 | 2,232 |
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.9points
- Latency+13.0
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +12.9, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+21.7points
- Latency+21.7
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +21.7, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+40.7points
- Latency+30.0
- Availability+9.5
- Correctness+0.7
- Head freshness+0.5
The parts add to +40.7, exactly — the score is a weighted sum, so it comes apart.