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-28 04:13:21 UTC
| Metric | dRPC | NodeReal | MEV Blocker |
|---|---|---|---|
| Rank | 3 | 4 | 7 |
| Score | 91.2 | 85.7 | 76.8 |
| Status | Excellent | Good | Good |
| Availability | 99.98% | 99.60% | 99.93% |
| p50 latency | 32.4 ms | 87.6 ms | 120.3 ms |
| p95 latency | 62.4 ms | 98.8 ms | 213.4 ms |
| p99 latency | 162.9 ms | 114.1 ms | 228.2 ms |
| Correctness | 99.98% | 100.00% | 99.99% |
| Head lag | 0.38 blocks | 0.35 blocks | 0.38 blocks |
| Rate limited | 8 | 0 | 0 |
| Unsupported | 0 | 0 | 0 |
| Samples | 8,312 | 8,304 | 8,461 |
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.5points
- Latency+5.4
- Availability+0.1
- Head freshness−0.0
- Correctness−0.0
The parts add to +5.5, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMEV Blocker
+14.4points
- Latency+14.4
- Availability+0.0
- Head freshness+0.0
- Correctness−0.0
The parts add to +14.4, exactly — the score is a weighted sum, so it comes apart.