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
- Tenderly
- PublicNode
- dRPC
- NodeReal
- Blast API
- MEV Blocker
- Merkle
- Cloudflare
- 1RPC
Side by side
1h window · 60 minutes observed · generated 2026-08-28 09:07:38 UTC
| Metric | Tenderly | Blast API | Cloudflare |
|---|---|---|---|
| Rank | 1 | 5 | 8 |
| Score | 99.4 | 78.3 | 47.3 |
| Status | Excellent | Good | Poor |
| Availability | 99.94% | 99.87% | 23.24% |
| p50 latency | 18.4 ms | 104.9 ms | 13.5 ms |
| p95 latency | 32.9 ms | 120.0 ms | 91.8 ms |
| p99 latency | 61.5 ms | 132.3 ms | 135.1 ms |
| Correctness | 99.94% | 99.93% | 100.00% |
| Head lag | 0.45 blocks | 0.39 blocks | no cohort |
| Rate limited | 0 | 57 | 0 |
| Unsupported | 0 | 0 | 47 |
| Samples | 1,612 | 1,621 | 1,599 |
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.
TenderlyvsBlast API
+21.1points
- Latency+21.1
- 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.
TenderlyvsCloudflare
+52.1points
- Availability+29.6
- Latency+15.2
- Head freshness*+9.5
- Correctness−2.2
The parts add to +52.1, exactly — the score is a weighted sum, so it comes apart. Components marked * were measured for only one of the two; the other’s weight is spread across what it does have, which is why the two sides can carry different weights for the same row.