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 · 2.2 days observed · generated 2026-08-27 02:34:16 UTC
| Metric | dRPC | Blast API | Merkle | MEV Blocker |
|---|---|---|---|---|
| Rank | 3 | 5 | 6 | 7 |
| Score | 93.6 | 86.0 | 79.1 | 78.1 |
| Status | Excellent | Good | Good | Good |
| Availability | 99.93% | 99.98% | 99.98% | 99.88% |
| p50 latency | 34.0 ms | 104.6 ms | 106.6 ms | 118.5 ms |
| p95 latency | 72.6 ms | 122.2 ms | 195.7 ms | 209.5 ms |
| p99 latency | 169.2 ms | 144.1 ms | 243.1 ms | 233.2 ms |
| Correctness | 99.99% | 99.99% | 100.00% | 99.99% |
| Head lag | 0.36 blocks | 0.42 blocks | 0.46 blocks | 0.40 blocks |
| Rate limited | 565 | 985 | 14,087 | 2 |
| Unsupported | 0 | 0 | 173 | 0 |
| Samples | 85,905 | 86,790 | 20,258 | 87,193 |
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
+7.6points
- Latency+7.6
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +7.6, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+14.5points
- Latency+14.4
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +14.5, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMEV Blocker
+15.5points
- Latency+15.4
- Head freshness+0.0
- Availability+0.0
- Correctness+0.0
The parts add to +15.5, exactly — the score is a weighted sum, so it comes apart.