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 08:57:43 UTC
| Metric | dRPC | Blast API | Cloudflare |
|---|---|---|---|
| Rank | 3 | 5 | 8 |
| Score | 85.4 | 78.4 | 47.2 |
| Status | Good | Good | Poor |
| Availability | 99.87% | 99.87% | 23.03% |
| p50 latency | 32.2 ms | 104.4 ms | 13.3 ms |
| p95 latency | 77.8 ms | 119.4 ms | 91.8 ms |
| p99 latency | 182.9 ms | 132.1 ms | 134.6 ms |
| Correctness | 99.94% | 99.93% | 100.00% |
| Head lag | 0.41 blocks | 0.39 blocks | no cohort |
| Rate limited | 7 | 79 | 0 |
| Unsupported | 0 | 0 | 47 |
| Samples | 1,587 | 1,619 | 1,603 |
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 dRPC, the highest scorer of those selected.
dRPCvsBlast API
+7.0points
- Latency+7.1
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +7.0, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+38.2points
- Availability+29.7
- Head freshness*+9.5
- Correctness−2.2
- Latency+1.3
The parts add to +38.2, 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.