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
30d window · 2.3 days observed · generated 2026-08-27 02:54:41 UTC
| Metric | Tenderly | NodeReal | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 4 | 6 | 8 |
| Score | 94.0 | 88.9 | 79.1 | 62.6 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.96% | 99.79% | 99.98% | 85.50% |
| p50 latency | 19.9 ms | 87.3 ms | 106.6 ms | 225.7 ms |
| p95 latency | 69.6 ms | 99.9 ms | 195.9 ms | 4391.3 ms |
| p99 latency | 869.3 ms | 123.5 ms | 243.1 ms | 7602.5 ms |
| Correctness | 99.99% | 99.99% | 100.00% | 97.48% |
| Head lag | 0.51 blocks | 0.35 blocks | 0.46 blocks | 0.91 blocks |
| Rate limited | 0 | 0 | 14,170 | 15,075 |
| Unsupported | 0 | 0 | 174 | 0 |
| Samples | 87,897 | 86,395 | 20,378 | 18,677 |
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
+5.1points
- Latency+5.2
- Head freshness−0.2
- Availability+0.1
- Correctness−0.0
The parts add to +5.1, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+14.9points
- Latency+15.0
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +14.9, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+31.4points
- Latency+24.6
- Availability+5.8
- Correctness+0.5
- Head freshness+0.5
The parts add to +31.4, exactly — the score is a weighted sum, so it comes apart.