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
1h window · 60 minutes observed · generated 2026-08-28 00:03:28 UTC
| Metric | PublicNode | MEV Blocker | 1RPC |
|---|---|---|---|
| Rank | 1 | 7 | 9 |
| Score | 99.4 | 76.7 | 45.3 |
| Status | Excellent | Good | Poor |
| Availability | 100.00% | 100.00% | 41.18% |
| p50 latency | 17.7 ms | 120.4 ms | 4375.0 ms |
| p95 latency | 29.3 ms | 213.5 ms | 8458.8 ms |
| p99 latency | 52.3 ms | 225.4 ms | 8458.8 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.36 blocks | 1.00 blocks |
| Rate limited | 0 | 0 | 263 |
| Unsupported | 0 | 0 | 0 |
| Samples | 1,619 | 1,603 | 320 |
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.
PublicNodevsMEV Blocker
+22.7points
- Latency+22.9
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +22.7, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+54.1points
- Latency+30.0
- Availability+23.5
- Head freshness+0.6
- Correctness+0.0
The parts add to +54.1, exactly — the score is a weighted sum, so it comes apart.