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
6h window · 6.0 hours observed · generated 2026-08-27 03:15:19 UTC
| Metric | dRPC | Blast API | MEV Blocker | 1RPC |
|---|---|---|---|---|
| Rank | 3 | 5 | 7 | 8 |
| Score | 90.6 | 84.2 | 77.2 | 58.7 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.94% | 99.99% | 99.95% | 76.33% |
| p50 latency | 33.2 ms | 103.4 ms | 117.8 ms | 2024.4 ms |
| p95 latency | 69.7 ms | 117.3 ms | 209.1 ms | 6590.4 ms |
| p99 latency | 167.2 ms | 145.0 ms | 228.9 ms | 9196.2 ms |
| Correctness | 99.99% | 100.00% | 100.00% | 96.63% |
| Head lag | 0.38 blocks | 0.41 blocks | 0.39 blocks | 0.95 blocks |
| Rate limited | 27 | 71 | 2 | 1,438 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 8,381 | 8,457 | 8,494 | 2,008 |
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
+6.3points
- Latency+6.3
- Head freshness+0.0
- Availability−0.0
- Correctness−0.0
The parts add to +6.3, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMEV Blocker
+13.3points
- Latency+13.3
- Head freshness+0.0
- Availability−0.0
- Correctness−0.0
The parts add to +13.3, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+31.8points
- Latency+21.1
- Availability+9.4
- Correctness+0.7
- Head freshness+0.7
The parts add to +31.8, exactly — the score is a weighted sum, so it comes apart.