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-27 12:29:48 UTC
| Metric | PublicNode | NodeReal | MEV Blocker |
|---|---|---|---|
| Rank | 2 | 4 | 7 |
| Score | 96.0 | 83.1 | 69.5 |
| Status | Excellent | Good | Degraded |
| Availability | 99.94% | 100.00% | 99.88% |
| p50 latency | 24.8 ms | 87.4 ms | 124.5 ms |
| p95 latency | 47.0 ms | 98.8 ms | 217.6 ms |
| p99 latency | 101.1 ms | 120.9 ms | 235.7 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.47 blocks | 0.32 blocks | 0.41 blocks |
| Rate limited | 0 | 0 | 0 |
| Unsupported | 0 | 0 | 0 |
| Samples | 1,621 | 1,584 | 1,607 |
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.1
- 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
+26.5points
- Latency+26.6
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +26.5, exactly — the score is a weighted sum, so it comes apart.