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.8 days observed · generated 2026-08-27 16:59:41 UTC
| Metric | Tenderly | NodeReal | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 4 | 6 | 8 |
| Score | 96.5 | 87.7 | 78.5 | 62.4 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.96% | 99.83% | 99.98% | 84.99% |
| p50 latency | 19.8 ms | 87.4 ms | 106.8 ms | 225.7 ms |
| p95 latency | 51.7 ms | 100.0 ms | 195.7 ms | 4391.3 ms |
| p99 latency | 750.8 ms | 126.2 ms | 243.3 ms | 7602.5 ms |
| Correctness | 99.99% | 99.99% | 100.00% | 97.48% |
| Head lag | 0.50 blocks | 0.35 blocks | 0.48 blocks | 0.91 blocks |
| Rate limited | 0 | 0 | 17,792 | 19,015 |
| Unsupported | 0 | 0 | 219 | 0 |
| Samples | 110,716 | 108,846 | 25,658 | 23,190 |
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
+8.8points
- Latency+8.9
- Head freshness−0.2
- Availability+0.1
- Correctness−0.0
The parts add to +8.8, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+18.0points
- Latency+18.0
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +18.0, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+34.1points
- Latency+27.1
- Availability+6.0
- Correctness+0.5
- Head freshness+0.5
The parts add to +34.1, exactly — the score is a weighted sum, so it comes apart.