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 13:42:10 UTC
| Metric | Tenderly | NodeReal | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 1 | 4 | 5 | 6 |
| Score | 99.4 | 82.8 | 78.7 | 70.2 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.95% | 100.00% | 99.99% | 100.00% |
| p50 latency | 20.1 ms | 87.8 ms | 107.7 ms | 108.8 ms |
| p95 latency | 34.9 ms | 99.6 ms | 124.8 ms | 200.3 ms |
| p99 latency | 96.9 ms | 123.7 ms | 153.3 ms | 230.9 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.34 blocks | 0.41 blocks | 0.48 blocks |
| Rate limited | 0 | 0 | 78 | 1,452 |
| Unsupported | 0 | 0 | 0 | 18 |
| Samples | 9,240 | 9,086 | 9,241 | 2,172 |
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
+16.6points
- Latency+16.8
- Head freshness−0.2
- Availability−0.0
- Correctness+0.0
The parts add to +16.6, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+20.7points
- Latency+20.8
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +20.7, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+29.2points
- Latency+29.2
- Availability−0.0
- Head freshness−0.0
- Correctness+0.0
The parts add to +29.2, exactly — the score is a weighted sum, so it comes apart.