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 08:01:01 UTC
| Metric | dRPC | Merkle | Cloudflare |
|---|---|---|---|
| Rank | 3 | 6 | 9 |
| Score | 91.4 | 78.0 | 53.4 |
| Status | Excellent | Good | Degraded |
| Availability | 99.97% | 100.00% | 23.12% |
| p50 latency | 33.1 ms | 107.3 ms | 14.7 ms |
| p95 latency | 68.4 ms | 192.4 ms | 86.6 ms |
| p99 latency | 189.0 ms | 256.1 ms | 216.3 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.37 blocks | 0.52 blocks | no cohort |
| Rate limited | 81 | 5,984 | 27 |
| Unsupported | 0 | 76 | 1,089 |
| Samples | 36,696 | 8,786 | 37,310 |
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
+13.4points
- Latency+13.2
- Head freshness+0.2
- Availability−0.0
- Correctness−0.0
The parts add to +13.4, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+38.0points
- Availability+29.7
- Head freshness*+9.6
- Correctness−2.2
- Latency+0.9
The parts add to +38.0, 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.