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
6h window · 6.0 hours observed · generated 2026-08-27 21:06:34 UTC
| Metric | PublicNode | NodeReal | MEV Blocker |
|---|---|---|---|
| Rank | 2 | 4 | 7 |
| Score | 94.3 | 83.1 | 69.5 |
| Status | Excellent | Good | Degraded |
| Availability | 100.00% | 99.98% | 99.94% |
| p50 latency | 25.2 ms | 87.2 ms | 124.9 ms |
| p95 latency | 52.9 ms | 99.0 ms | 216.9 ms |
| p99 latency | 113.2 ms | 120.0 ms | 237.5 ms |
| Correctness | 100.00% | 99.98% | 99.98% |
| Head lag | 0.47 blocks | 0.33 blocks | 0.40 blocks |
| Rate limited | 0 | 0 | 0 |
| Unsupported | 0 | 0 | 0 |
| Samples | 8,353 | 8,133 | 8,275 |
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
+11.2points
- Latency+11.4
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +11.2, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMEV Blocker
+24.8points
- Latency+24.9
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +24.8, exactly — the score is a weighted sum, so it comes apart.