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
24h window · 24 hours observed · generated 2026-08-27 14:56:32 UTC
| Metric | Tenderly | NodeReal | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 1 | 4 | 5 | 6 |
| Score | 99.4 | 86.5 | 83.8 | 77.9 |
| Status | Excellent | Good | Good | Good |
| Availability | 99.98% | 100.00% | 99.99% | 100.00% |
| p50 latency | 19.3 ms | 87.3 ms | 105.8 ms | 107.2 ms |
| p95 latency | 34.1 ms | 100.1 ms | 122.2 ms | 193.3 ms |
| p99 latency | 77.1 ms | 129.6 ms | 148.7 ms | 234.3 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.34 blocks | 0.41 blocks | 0.49 blocks |
| Rate limited | 0 | 0 | 344 | 6,117 |
| Unsupported | 0 | 0 | 0 | 72 |
| Samples | 38,738 | 38,144 | 38,554 | 8,826 |
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
+12.9points
- Latency+13.1
- Head freshness−0.2
- Availability−0.0
- Correctness+0.0
The parts add to +12.9, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+15.6points
- Latency+15.7
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +15.6, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+21.5points
- Latency+21.5
- Availability−0.0
- Head freshness+0.0
- Correctness+0.0
The parts add to +21.5, exactly — the score is a weighted sum, so it comes apart.