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
Side by side
24h window · 24 hours observed · generated 2026-08-27 00:28:06 UTC
| Metric | PublicNode | dRPC | MEV Blocker |
|---|---|---|---|
| Rank | 1 | 3 | 7 |
| Score | 99.4 | 91.3 | 77.1 |
| Status | Excellent | Excellent | Good |
| Availability | 99.98% | 99.92% | 99.89% |
| p50 latency | 18.4 ms | 34.1 ms | 119.1 ms |
| p95 latency | 35.0 ms | 68.6 ms | 210.5 ms |
| p99 latency | 73.4 ms | 169.0 ms | 233.5 ms |
| Correctness | 100.00% | 99.99% | 99.99% |
| Head lag | 0.49 blocks | 0.37 blocks | 0.39 blocks |
| Rate limited | 0 | 125 | 1 |
| Unsupported | 0 | 0 | 0 |
| Samples | 38,316 | 37,407 | 37,959 |
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 PublicNode, the highest scorer of those selected.
PublicNodevsdRPC
+8.1points
- Latency+8.2
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +8.1, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMEV Blocker
+22.3points
- Latency+22.3
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +22.3, exactly — the score is a weighted sum, so it comes apart.