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 · 3.2 days observed · generated 2026-08-28 02:34:32 UTC
| Metric | dRPC | NodeReal | MEV Blocker |
|---|---|---|---|
| Rank | 3 | 4 | 7 |
| Score | 91.7 | 87.2 | 77.3 |
| Status | Excellent | Good | Good |
| Availability | 99.94% | 99.85% | 99.90% |
| p50 latency | 33.8 ms | 87.4 ms | 119.6 ms |
| p95 latency | 71.2 ms | 99.9 ms | 211.0 ms |
| p99 latency | 170.6 ms | 124.9 ms | 234.0 ms |
| Correctness | 99.99% | 99.99% | 99.99% |
| Head lag | 0.36 blocks | 0.34 blocks | 0.40 blocks |
| Rate limited | 675 | 0 | 3 |
| Unsupported | 0 | 0 | 0 |
| Samples | 124,160 | 124,096 | 126,026 |
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 dRPC, the highest scorer of those selected.
dRPCvsNodeReal
+4.5points
- Latency+4.5
- Availability+0.0
- Head freshness−0.0
- Correctness−0.0
The parts add to +4.5, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMEV Blocker
+14.5points
- Latency+14.4
- Head freshness+0.0
- Availability+0.0
- Correctness+0.0
The parts add to +14.5, exactly — the score is a weighted sum, so it comes apart.