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:33:38 UTC
| Metric | dRPC | Blast API | MEV Blocker | 1RPC |
|---|---|---|---|---|
| Rank | 3 | 5 | 7 | 8 |
| Score | 91.1 | 83.9 | 76.9 | 57.8 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.94% | 99.99% | 99.93% | 73.97% |
| p50 latency | 33.8 ms | 106.1 ms | 121.2 ms | 2024.4 ms |
| p95 latency | 70.1 ms | 122.7 ms | 212.4 ms | 6590.4 ms |
| p99 latency | 171.1 ms | 149.8 ms | 235.4 ms | 9196.2 ms |
| Correctness | 99.99% | 100.00% | 100.00% | 96.63% |
| Head lag | 0.37 blocks | 0.42 blocks | 0.40 blocks | 0.95 blocks |
| Rate limited | 136 | 323 | 3 | 6,551 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 37,534 | 38,000 | 38,097 | 7,866 |
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.2points
- Latency+7.2
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +7.2, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMEV Blocker
+14.2points
- Latency+14.2
- Head freshness+0.0
- Correctness−0.0
- Availability+0.0
The parts add to +14.2, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+33.3points
- Latency+21.6
- Availability+10.4
- Correctness+0.7
- Head freshness+0.7
The parts add to +33.3, exactly — the score is a weighted sum, so it comes apart.