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
1h window · 60 minutes observed · generated 2026-08-28 09:11:26 UTC
| Metric | Tenderly | NodeReal | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 1 | 3 | 5 | 7 |
| Score | 99.4 | 81.6 | 78.3 | 69.3 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.94% | 100.00% | 99.87% | 100.00% |
| p50 latency | 18.7 ms | 86.3 ms | 105.4 ms | 109.1 ms |
| p95 latency | 33.2 ms | 99.3 ms | 120.4 ms | 205.5 ms |
| p99 latency | 59.8 ms | 124.7 ms | 132.3 ms | 250.3 ms |
| Correctness | 99.94% | 100.00% | 99.93% | 100.00% |
| Head lag | 0.45 blocks | 0.34 blocks | 0.38 blocks | 0.57 blocks |
| Rate limited | 0 | 0 | 50 | 258 |
| Unsupported | 0 | 0 | 0 | 3 |
| Samples | 1,607 | 1,582 | 1,613 | 374 |
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
+17.8points
- Latency+18.0
- Head freshness−0.1
- Availability−0.0
- Correctness−0.0
The parts add to +17.8, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+21.1points
- Latency+21.2
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +21.1, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+30.1points
- Latency+30.0
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +30.1, exactly — the score is a weighted sum, so it comes apart.