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 08:35:03 UTC
| Metric | Tenderly | NodeReal | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 2 | 4 | 5 | 6 |
| Score | 98.8 | 80.1 | 78.0 | 70.0 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.98% | 100.00% | 99.99% | 100.00% |
| p50 latency | 18.4 ms | 87.7 ms | 104.3 ms | 104.7 ms |
| p95 latency | 32.2 ms | 105.0 ms | 119.1 ms | 192.8 ms |
| p99 latency | 82.4 ms | 139.7 ms | 145.5 ms | 251.0 ms |
| Correctness | 100.00% | 100.00% | 99.99% | 100.00% |
| Head lag | 0.48 blocks | 0.36 blocks | 0.41 blocks | 0.62 blocks |
| Rate limited | 0 | 0 | 107 | 1,417 |
| Unsupported | 0 | 0 | 0 | 15 |
| Samples | 9,031 | 8,914 | 9,033 | 2,026 |
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
+18.7points
- Latency+18.9
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +18.7, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+20.8points
- Latency+20.9
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +20.8, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+28.7points
- Latency+28.6
- Head freshness+0.2
- Availability−0.0
- Correctness+0.0
The parts add to +28.7, exactly — the score is a weighted sum, so it comes apart.