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 05:46:00 UTC
| Metric | NodeReal | Blast API | 1RPC |
|---|---|---|---|
| Rank | 4 | 5 | 8 |
| Score | 86.1 | 84.0 | 58.7 |
| Status | Good | Good | Degraded |
| Availability | 99.99% | 99.99% | 76.13% |
| p50 latency | 87.1 ms | 103.1 ms | 2024.4 ms |
| p95 latency | 98.1 ms | 115.5 ms | 6590.4 ms |
| p99 latency | 115.8 ms | 142.4 ms | 9196.2 ms |
| Correctness | 99.99% | 100.00% | 96.63% |
| Head lag | 0.34 blocks | 0.42 blocks | 0.95 blocks |
| Rate limited | 0 | 78 | 1,580 |
| Unsupported | 0 | 0 | 0 |
| Samples | 9,210 | 9,335 | 2,172 |
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
- Correctness−0.0
- Availability+0.0
The parts add to +2.1, exactly — the score is a weighted sum, so it comes apart.
NodeRealvs1RPC
+27.4points
- Latency+16.5
- Availability+9.5
- Head freshness+0.7
- Correctness+0.7
The parts add to +27.4, exactly — the score is a weighted sum, so it comes apart.