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 · 44 hours observed · generated 2026-08-26 16:23:34 UTC
| Metric | dRPC | NodeReal | MEV Blocker |
|---|---|---|---|
| Rank | 2 | 3 | 7 |
| Score | 93.5 | 88.5 | 77.5 |
| Status | Excellent | Good | Good |
| Availability | 99.94% | 99.74% | 99.87% |
| p50 latency | 33.8 ms | 87.5 ms | 118.1 ms |
| p95 latency | 72.0 ms | 100.0 ms | 208.7 ms |
| p99 latency | 166.4 ms | 123.7 ms | 233.0 ms |
| Correctness | 99.99% | 99.99% | 99.98% |
| Head lag | 0.35 blocks | 0.35 blocks | 0.39 blocks |
| Rate limited | 503 | 0 | 0 |
| Unsupported | 0 | 0 | 0 |
| Samples | 69,682 | 69,645 | 70,724 |
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
+5.0points
- Latency+4.9
- Availability+0.1
- Head freshness−0.0
- Correctness+0.0
The parts add to +5.0, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMEV Blocker
+16.0points
- Latency+15.9
- Head freshness+0.0
- Availability+0.0
- Correctness+0.0
The parts add to +16.0, exactly — the score is a weighted sum, so it comes apart.