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 14:56:35 UTC
| Metric | Tenderly | NodeReal | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 1 | 4 | 5 | 6 |
| Score | 99.4 | 82.9 | 78.4 | 70.8 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.95% | 100.00% | 99.99% | 100.00% |
| p50 latency | 20.1 ms | 87.7 ms | 108.3 ms | 108.2 ms |
| p95 latency | 34.5 ms | 99.4 ms | 126.2 ms | 191.4 ms |
| p99 latency | 77.6 ms | 126.6 ms | 153.5 ms | 231.3 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.33 blocks | 0.41 blocks | 0.46 blocks |
| Rate limited | 0 | 0 | 71 | 1,498 |
| Unsupported | 0 | 0 | 0 | 18 |
| Samples | 9,641 | 9,461 | 9,628 | 2,235 |
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.5points
- Latency+16.7
- Head freshness−0.2
- Availability−0.0
- Correctness+0.0
The parts add to +16.5, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+21.0points
- Latency+21.1
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +21.0, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+28.6points
- Latency+28.6
- Head freshness−0.0
- Availability−0.0
- Correctness+0.0
The parts add to +28.6, exactly — the score is a weighted sum, so it comes apart.