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
24h window · 24 hours observed · generated 2026-08-26 22:14:26 UTC
| Metric | NodeReal | Blast API | MEV Blocker |
|---|---|---|---|
| Rank | 4 | 5 | 7 |
| Score | 86.6 | 84.2 | 77.2 |
| Status | Good | Good | Good |
| Availability | 100.00% | 99.98% | 99.87% |
| p50 latency | 87.4 ms | 104.1 ms | 119.1 ms |
| p95 latency | 100.2 ms | 120.9 ms | 210.6 ms |
| p99 latency | 124.7 ms | 140.5 ms | 232.9 ms |
| Correctness | 100.00% | 99.98% | 99.99% |
| Head lag | 0.35 blocks | 0.42 blocks | 0.39 blocks |
| Rate limited | 0 | 356 | 0 |
| Unsupported | 0 | 0 | 0 |
| Samples | 37,016 | 37,484 | 37,582 |
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.
NodeRealvsBlast API
+2.5points
- Latency+2.4
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +2.5, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsMEV Blocker
+9.4points
- Latency+9.3
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +9.4, exactly — the score is a weighted sum, so it comes apart.