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 04:38:49 UTC
| Metric | Tenderly | NodeReal | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 1 | 4 | 5 | 6 |
| Score | 99.4 | 86.1 | 84.1 | 77.8 |
| Status | Excellent | Good | Good | Good |
| Availability | 100.00% | 99.99% | 99.99% | 100.00% |
| p50 latency | 18.5 ms | 86.9 ms | 103.1 ms | 104.4 ms |
| p95 latency | 32.1 ms | 98.3 ms | 115.4 ms | 193.0 ms |
| p99 latency | 66.8 ms | 116.2 ms | 140.5 ms | 229.0 ms |
| Correctness | 100.00% | 99.99% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.34 blocks | 0.42 blocks | 0.44 blocks |
| Rate limited | 0 | 0 | 80 | 1,414 |
| Unsupported | 0 | 0 | 0 | 20 |
| Samples | 9,123 | 9,020 | 9,093 | 2,006 |
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.5
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +13.3, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+15.4points
- Latency+15.4
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +15.4, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+21.6points
- Latency+21.7
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +21.6, exactly — the score is a weighted sum, so it comes apart.