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 01:54:21 UTC
| Metric | Tenderly | NodeReal | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 1 | 4 | 5 | 6 |
| Score | 99.4 | 86.1 | 83.7 | 77.6 |
| Status | Excellent | Good | Good | Good |
| Availability | 99.99% | 99.99% | 99.99% | 100.00% |
| p50 latency | 18.9 ms | 87.0 ms | 105.0 ms | 105.9 ms |
| p95 latency | 32.2 ms | 99.3 ms | 120.0 ms | 193.1 ms |
| p99 latency | 71.6 ms | 122.1 ms | 141.9 ms | 220.4 ms |
| Correctness | 100.00% | 99.99% | 100.00% | 100.00% |
| Head lag | 0.50 blocks | 0.33 blocks | 0.42 blocks | 0.50 blocks |
| Rate limited | 0 | 0 | 53 | 1,490 |
| Unsupported | 0 | 0 | 0 | 18 |
| Samples | 9,532 | 9,405 | 9,481 | 2,141 |
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
+13.3points
- Latency+13.4
- Head freshness−0.2
- Correctness+0.0
- Availability+0.0
The parts add to +13.3, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+15.7points
- Latency+15.8
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +15.7, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+21.8points
- Latency+21.8
- Head freshness+0.0
- Availability−0.0
- Correctness+0.0
The parts add to +21.8, exactly — the score is a weighted sum, so it comes apart.