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
- Merkle
- MEV Blocker
- 1RPC
- Cloudflare
Side by side
24h window · 24 hours observed · generated 2026-08-27 17:25:18 UTC
| Metric | dRPC | Blast API | Cloudflare |
|---|---|---|---|
| Rank | 3 | 5 | 9 |
| Score | 91.1 | 83.9 | 53.5 |
| Status | Excellent | Good | Degraded |
| Availability | 99.94% | 99.99% | 23.15% |
| p50 latency | 33.8 ms | 106.1 ms | 15.0 ms |
| p95 latency | 70.1 ms | 122.6 ms | 86.5 ms |
| p99 latency | 171.0 ms | 149.8 ms | 240.8 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.37 blocks | 0.42 blocks | no cohort |
| Rate limited | 135 | 323 | 36 |
| Unsupported | 0 | 0 | 1,116 |
| Samples | 37,310 | 37,785 | 37,964 |
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.2points
- Latency+7.2
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +7.2, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+37.6points
- Availability+29.7
- Head freshness*+9.5
- Correctness−2.2
- Latency+0.6
The parts add to +37.6, 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.