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
7d window · 2.3 days observed · generated 2026-08-27 04:29:57 UTC
| Metric | dRPC | Blast API | MEV Blocker | 1RPC |
|---|---|---|---|---|
| Rank | 3 | 5 | 7 | 8 |
| Score | 93.2 | 85.7 | 78.0 | 62.6 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.93% | 99.98% | 99.89% | 85.50% |
| p50 latency | 34.0 ms | 104.5 ms | 118.5 ms | 225.7 ms |
| p95 latency | 72.4 ms | 122.1 ms | 209.3 ms | 4391.3 ms |
| p99 latency | 168.8 ms | 144.2 ms | 233.0 ms | 7602.5 ms |
| Correctness | 99.99% | 99.99% | 99.99% | 97.48% |
| Head lag | 0.36 blocks | 0.42 blocks | 0.40 blocks | 0.91 blocks |
| Rate limited | 577 | 993 | 2 | 15,522 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 88,974 | 89,918 | 90,297 | 19,188 |
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.5points
- Latency+7.5
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +7.5, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMEV Blocker
+15.2points
- Latency+15.1
- Head freshness+0.0
- Availability+0.0
- Correctness+0.0
The parts add to +15.2, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+30.6points
- Latency+23.7
- Availability+5.8
- Head freshness+0.6
- Correctness+0.5
The parts add to +30.6, exactly — the score is a weighted sum, so it comes apart.