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-26 13:57:06 UTC
| Metric | PublicNode | NodeReal | MEV Blocker |
|---|---|---|---|
| Rank | 1 | 4 | 7 |
| Score | 99.4 | 88.6 | 77.6 |
| Status | Excellent | Good | Good |
| Availability | 99.97% | 99.98% | 99.85% |
| p50 latency | 19.1 ms | 87.6 ms | 118.7 ms |
| p95 latency | 32.3 ms | 100.0 ms | 210.0 ms |
| p99 latency | 71.5 ms | 124.5 ms | 236.2 ms |
| Correctness | 99.97% | 99.98% | 99.98% |
| Head lag | 0.49 blocks | 0.35 blocks | 0.39 blocks |
| Rate limited | 0 | 0 | 0 |
| Unsupported | 0 | 0 | 0 |
| Samples | 39,115 | 38,199 | 38,734 |
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.
PublicNodevsNodeReal
+10.8points
- Latency+10.9
- Head freshness−0.2
- Availability−0.0
- Correctness−0.0
The parts add to +10.8, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMEV Blocker
+21.8points
- Latency+21.8
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +21.8, exactly — the score is a weighted sum, so it comes apart.