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
30d window · 2.3 days observed · generated 2026-08-27 02:51:54 UTC
| Metric | NodeReal | MEV Blocker | 1RPC |
|---|---|---|---|
| Rank | 4 | 7 | 8 |
| Score | 88.9 | 78.1 | 62.6 |
| Status | Good | Good | Degraded |
| Availability | 99.79% | 99.88% | 85.50% |
| p50 latency | 87.3 ms | 118.5 ms | 225.7 ms |
| p95 latency | 99.9 ms | 209.4 ms | 4391.3 ms |
| p99 latency | 123.5 ms | 233.2 ms | 7602.5 ms |
| Correctness | 99.99% | 99.99% | 97.48% |
| Head lag | 0.35 blocks | 0.40 blocks | 0.91 blocks |
| Rate limited | 0 | 2 | 15,063 |
| Unsupported | 0 | 0 | 0 |
| Samples | 86,319 | 87,667 | 18,664 |
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 NodeReal, the highest scorer of those selected.
NodeRealvsMEV Blocker
+10.8points
- Latency+10.7
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +10.8, exactly — the score is a weighted sum, so it comes apart.
NodeRealvs1RPC
+26.3points
- Latency+19.4
- Availability+5.7
- Head freshness+0.7
- Correctness+0.5
The parts add to +26.3, exactly — the score is a weighted sum, so it comes apart.