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
24h window · 24 hours observed · generated 2026-08-26 22:14:26 UTC
| Metric | dRPC | Blast API | Merkle | MEV Blocker |
|---|---|---|---|---|
| Rank | 3 | 5 | 6 | 7 |
| Score | 91.4 | 84.2 | 78.0 | 77.2 |
| Status | Excellent | Good | Good | Good |
| Availability | 99.93% | 99.98% | 100.00% | 99.87% |
| p50 latency | 34.1 ms | 104.1 ms | 107.1 ms | 119.1 ms |
| p95 latency | 68.4 ms | 120.9 ms | 196.8 ms | 210.6 ms |
| p99 latency | 167.9 ms | 140.5 ms | 241.2 ms | 232.9 ms |
| Correctness | 99.99% | 99.98% | 100.00% | 99.99% |
| Head lag | 0.37 blocks | 0.42 blocks | 0.46 blocks | 0.39 blocks |
| Rate limited | 120 | 356 | 6,064 | 0 |
| Unsupported | 0 | 0 | 79 | 0 |
| Samples | 37,054 | 37,484 | 8,753 | 37,582 |
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.
dRPCvsMerkle
+13.4points
- Latency+13.3
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +13.4, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMEV Blocker
+14.2points
- Latency+14.1
- Head freshness+0.0
- Availability+0.0
- Correctness−0.0
The parts add to +14.2, exactly — the score is a weighted sum, so it comes apart.