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-28 01:27:17 UTC
| Metric | PublicNode | NodeReal | MEV Blocker |
|---|---|---|---|
| Rank | 2 | 4 | 7 |
| Score | 98.7 | 86.3 | 76.7 |
| Status | Excellent | Good | Good |
| Availability | 99.99% | 99.97% | 99.92% |
| p50 latency | 19.9 ms | 87.2 ms | 121.6 ms |
| p95 latency | 35.3 ms | 98.8 ms | 215.3 ms |
| p99 latency | 76.6 ms | 115.8 ms | 232.0 ms |
| Correctness | 99.99% | 99.97% | 99.97% |
| Head lag | 0.48 blocks | 0.34 blocks | 0.39 blocks |
| Rate limited | 0 | 0 | 0 |
| Unsupported | 0 | 0 | 0 |
| Samples | 8,919 | 8,673 | 8,828 |
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.4points
- Latency+12.6
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +12.4, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMEV Blocker
+22.0points
- Latency+22.1
- 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.