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:53:23 UTC
| Metric | dRPC | NodeReal | Cloudflare |
|---|---|---|---|
| Rank | 3 | 4 | 9 |
| Score | 91.2 | 86.7 | 53.4 |
| Status | Excellent | Good | Degraded |
| Availability | 99.94% | 100.00% | 23.15% |
| p50 latency | 33.8 ms | 87.3 ms | 15.1 ms |
| p95 latency | 70.0 ms | 100.0 ms | 87.1 ms |
| p99 latency | 171.6 ms | 129.8 ms | 243.4 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.37 blocks | 0.34 blocks | no cohort |
| Rate limited | 136 | 0 | 36 |
| Unsupported | 0 | 0 | 1,139 |
| Samples | 38,061 | 38,074 | 38,722 |
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.
dRPCvsNodeReal
+4.5points
- Latency+4.6
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +4.5, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+37.7points
- Availability+29.7
- Head freshness*+9.5
- Correctness−2.2
- Latency+0.7
The parts add to +37.7, 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.