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 · 2.4 days observed · generated 2026-08-27 05:57:04 UTC
| Metric | NodeReal | Blast API | MEV Blocker |
|---|---|---|---|
| Rank | 4 | 5 | 7 |
| Score | 88.4 | 85.5 | 77.9 |
| Status | Good | Good | Good |
| Availability | 99.80% | 99.98% | 99.89% |
| p50 latency | 87.3 ms | 104.4 ms | 118.4 ms |
| p95 latency | 99.8 ms | 122.0 ms | 209.2 ms |
| p99 latency | 123.2 ms | 144.2 ms | 232.8 ms |
| Correctness | 99.99% | 99.99% | 99.99% |
| Head lag | 0.35 blocks | 0.42 blocks | 0.40 blocks |
| Rate limited | 0 | 1,022 | 2 |
| Unsupported | 0 | 0 | 0 |
| Samples | 91,253 | 92,263 | 92,647 |
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.8points
- Latency+2.8
- Head freshness+0.1
- Availability−0.1
- Correctness+0.0
The parts add to +2.8, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsMEV Blocker
+10.4points
- Latency+10.4
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +10.4, exactly — the score is a weighted sum, so it comes apart.