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-27 06:53:58 UTC
| Metric | NodeReal | Blast API | MEV Blocker |
|---|---|---|---|
| Rank | 4 | 5 | 7 |
| Score | 80.4 | 78.3 | 69.5 |
| Status | Good | Good | Degraded |
| Availability | 99.99% | 99.98% | 99.93% |
| p50 latency | 87.1 ms | 103.3 ms | 118.7 ms |
| p95 latency | 103.1 ms | 116.7 ms | 207.1 ms |
| p99 latency | 138.2 ms | 144.2 ms | 225.0 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.35 blocks | 0.42 blocks | 0.41 blocks |
| Rate limited | 0 | 79 | 0 |
| Unsupported | 0 | 0 | 0 |
| Samples | 9,415 | 9,548 | 9,524 |
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.1points
- Latency+2.0
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +2.1, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsMEV Blocker
+10.9points
- Latency+10.8
- Head freshness+0.1
- Availability+0.0
- Correctness−0.0
The parts add to +10.9, exactly — the score is a weighted sum, so it comes apart.