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-28 18:15:28 UTC
| Metric | dRPC | Blast API | Cloudflare |
|---|---|---|---|
| Rank | 3 | 5 | 9 |
| Score | 89.2 | 83.5 | 53.3 |
| Status | Good | Good | Degraded |
| Availability | 99.98% | 99.98% | 23.12% |
| p50 latency | 33.6 ms | 105.3 ms | 13.3 ms |
| p95 latency | 77.3 ms | 121.9 ms | 83.4 ms |
| p99 latency | 189.7 ms | 144.5 ms | 144.7 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.37 blocks | 0.41 blocks | no cohort |
| Rate limited | 99 | 328 | 21 |
| Unsupported | 0 | 0 | 1,107 |
| Samples | 37,061 | 37,693 | 37,715 |
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
+5.7points
- Latency+5.7
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +5.7, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+35.9points
- Availability+29.7
- Head freshness*+9.6
- Correctness−2.2
- Latency−1.1
The parts add to +35.9, 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.