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
- Cloudflare
- 1RPC
Side by side
6h window · 6.0 hours observed · generated 2026-08-28 22:16:48 UTC
| Metric | dRPC | Merkle | Cloudflare |
|---|---|---|---|
| Rank | 3 | 6 | 8 |
| Score | 88.4 | 69.9 | 48.9 |
| Status | Good | Degraded | Poor |
| Availability | 99.99% | 100.00% | 23.19% |
| p50 latency | 35.1 ms | 108.2 ms | 13.7 ms |
| p95 latency | 67.1 ms | 201.2 ms | 85.9 ms |
| p99 latency | 175.0 ms | 241.7 ms | 171.3 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.39 blocks | 0.46 blocks | no cohort |
| Rate limited | 13 | 1,363 | 5 |
| Unsupported | 0 | 13 | 258 |
| Samples | 8,408 | 1,986 | 8,560 |
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.
dRPCvsMerkle
+18.5points
- Latency+18.4
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +18.5, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+39.5points
- Availability+29.7
- Head freshness*+9.5
- Latency+2.5
- Correctness−2.2
The parts add to +39.5, 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.