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.7 days observed · generated 2026-08-27 12:28:57 UTC
| Metric | Tenderly | NodeReal | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 4 | 6 | 8 |
| Score | 95.7 | 87.9 | 78.5 | 62.5 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.96% | 99.82% | 99.98% | 85.16% |
| p50 latency | 19.8 ms | 87.4 ms | 106.5 ms | 225.7 ms |
| p95 latency | 55.8 ms | 100.0 ms | 196.3 ms | 4391.3 ms |
| p99 latency | 791.9 ms | 125.7 ms | 243.4 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 | 16,624 | 17,749 |
| Unsupported | 0 | 0 | 201 | 0 |
| Samples | 103,399 | 101,661 | 23,940 | 21,741 |
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
+7.9points
- Latency+8.0
- Head freshness−0.2
- Availability+0.1
- Correctness−0.0
The parts add to +7.9, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+17.2points
- Latency+17.2
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +17.2, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+33.2points
- Latency+26.4
- Availability+5.9
- Correctness+0.5
- Head freshness+0.5
The parts add to +33.2, exactly — the score is a weighted sum, so it comes apart.