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
- PublicNode
- Tenderly
- dRPC
- NodeReal
- Blast API
- Merkle
- MEV Blocker
- 1RPC
- Cloudflare
Side by side
30d window · 3.6 days observed · generated 2026-08-28 10:19:05 UTC
| Metric | dRPC | Blast API | Cloudflare |
|---|---|---|---|
| Rank | 3 | 5 | 9 |
| Score | 91.1 | 84.3 | 53.8 |
| Status | Excellent | Good | Degraded |
| Availability | 99.94% | 99.98% | 23.11% |
| p50 latency | 33.6 ms | 105.1 ms | 14.8 ms |
| p95 latency | 72.6 ms | 122.1 ms | 87.0 ms |
| p99 latency | 174.8 ms | 147.1 ms | 249.9 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.36 blocks | 0.42 blocks | no cohort |
| Rate limited | 701 | 1,491 | 117 |
| Unsupported | 0 | 0 | 4,076 |
| Samples | 136,521 | 138,220 | 138,620 |
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
+6.8points
- Latency+6.8
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +6.8, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+37.3points
- Availability+29.7
- Head freshness*+9.6
- Correctness−2.2
- Latency+0.2
The parts add to +37.3, 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.