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 13:40:46 UTC
| Metric | PublicNode | dRPC | MEV Blocker |
|---|---|---|---|
| Rank | 2 | 3 | 7 |
| Score | 98.8 | 90.5 | 76.8 |
| Status | Excellent | Excellent | Good |
| Availability | 99.97% | 99.92% | 99.92% |
| p50 latency | 19.4 ms | 34.1 ms | 120.6 ms |
| p95 latency | 37.3 ms | 72.2 ms | 211.4 ms |
| p99 latency | 86.7 ms | 171.6 ms | 232.9 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.37 blocks | 0.40 blocks |
| Rate limited | 0 | 158 | 3 |
| Unsupported | 0 | 0 | 0 |
| Samples | 38,682 | 37,730 | 38,290 |
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.3points
- Latency+8.4
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +8.3, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMEV Blocker
+22.0points
- Latency+22.0
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +22.0, exactly — the score is a weighted sum, so it comes apart.