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-28 10:41:02 UTC
| Metric | Tenderly | NodeReal | Merkle |
|---|---|---|---|
| Rank | 2 | 3 | 6 |
| Score | 99.4 | 79.0 | 69.7 |
| Status | Excellent | Good | Degraded |
| Availability | 99.99% | 100.00% | 100.00% |
| p50 latency | 18.4 ms | 87.5 ms | 106.1 ms |
| p95 latency | 32.3 ms | 114.8 ms | 199.8 ms |
| p99 latency | 55.0 ms | 160.8 ms | 250.3 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.47 blocks | 0.34 blocks | 0.55 blocks |
| Rate limited | 0 | 0 | 1,495 |
| Unsupported | 0 | 0 | 19 |
| Samples | 9,208 | 9,050 | 2,135 |
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
+20.4points
- Latency+20.6
- Head freshness−0.2
- Availability−0.0
- Correctness−0.0
The parts add to +20.4, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+29.7points
- Latency+29.6
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +29.7, exactly — the score is a weighted sum, so it comes apart.