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-26 22:11:46 UTC
| Metric | PublicNode | NodeReal | MEV Blocker |
|---|---|---|---|
| Rank | 2 | 4 | 7 |
| Score | 98.4 | 82.3 | 69.5 |
| Status | Excellent | Good | Degraded |
| Availability | 99.92% | 100.00% | 99.94% |
| p50 latency | 18.6 ms | 87.3 ms | 123.6 ms |
| p95 latency | 38.9 ms | 99.5 ms | 214.1 ms |
| p99 latency | 88.1 ms | 125.8 ms | 239.3 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.34 blocks | 0.41 blocks |
| Rate limited | 0 | 0 | 0 |
| Unsupported | 0 | 0 | 0 |
| Samples | 8,497 | 8,248 | 8,411 |
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
+16.1points
- Latency+16.3
- Head freshness−0.2
- Availability−0.0
- Correctness+0.0
The parts add to +16.1, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMEV Blocker
+28.9points
- Latency+29.0
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +28.9, exactly — the score is a weighted sum, so it comes apart.