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 03:53:02 UTC
| Metric | PublicNode | NodeReal | MEV Blocker |
|---|---|---|---|
| Rank | 1 | 4 | 7 |
| Score | 99.4 | 86.5 | 77.0 |
| Status | Excellent | Good | Good |
| Availability | 99.98% | 100.00% | 99.90% |
| p50 latency | 18.3 ms | 87.2 ms | 119.5 ms |
| p95 latency | 35.1 ms | 99.9 ms | 210.7 ms |
| p99 latency | 74.1 ms | 124.3 ms | 234.2 ms |
| Correctness | 100.00% | 100.00% | 99.99% |
| Head lag | 0.49 blocks | 0.34 blocks | 0.39 blocks |
| Rate limited | 0 | 0 | 2 |
| Unsupported | 0 | 0 | 0 |
| Samples | 38,988 | 38,048 | 38,629 |
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
+12.9points
- Latency+13.0
- Head freshness−0.2
- Availability−0.0
- Correctness+0.0
The parts add to +12.9, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMEV Blocker
+22.4points
- Latency+22.5
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +22.4, exactly — the score is a weighted sum, so it comes apart.