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
1h window · 60 minutes observed · generated 2026-08-28 00:17:29 UTC
| Metric | NodeReal | Blast API | 1RPC |
|---|---|---|---|
| Rank | 4 | 5 | 8 |
| Score | 85.9 | 83.7 | 56.8 |
| Status | Good | Good | Degraded |
| Availability | 100.00% | 100.00% | 70.78% |
| p50 latency | 87.4 ms | 103.3 ms | 2539.5 ms |
| p95 latency | 98.8 ms | 119.3 ms | 8458.8 ms |
| p99 latency | 109.9 ms | 147.2 ms | 9776.0 ms |
| Correctness | 100.00% | 100.00% | 98.20% |
| Head lag | 0.36 blocks | 0.41 blocks | 0.97 blocks |
| Rate limited | 0 | 0 | 199 |
| Unsupported | 0 | 0 | 0 |
| Samples | 1,566 | 1,606 | 386 |
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.2points
- Latency+2.2
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +2.2, exactly — the score is a weighted sum, so it comes apart.
NodeRealvs1RPC
+29.1points
- Latency+16.3
- Availability+11.7
- Head freshness+0.7
- Correctness+0.4
The parts add to +29.1, exactly — the score is a weighted sum, so it comes apart.