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
7d window · 3.6 days observed · generated 2026-08-28 11:38:51 UTC
| Metric | NodeReal | Blast API | 1RPC |
|---|---|---|---|
| Rank | 4 | 5 | 8 |
| Score | 86.8 | 84.2 | 61.7 |
| Status | Good | Good | Degraded |
| Availability | 99.84% | 99.98% | 83.25% |
| p50 latency | 87.4 ms | 105.1 ms | 265.3 ms |
| p95 latency | 100.1 ms | 122.1 ms | 4975.4 ms |
| p99 latency | 128.7 ms | 147.0 ms | 8455.9 ms |
| Correctness | 99.99% | 99.99% | 97.38% |
| Head lag | 0.34 blocks | 0.42 blocks | 0.91 blocks |
| Rate limited | 0 | 1,545 | 24,179 |
| Unsupported | 0 | 0 | 0 |
| Samples | 138,556 | 140,366 | 29,466 |
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.6points
- Latency+2.6
- Head freshness+0.1
- Availability−0.1
- Correctness+0.0
The parts add to +2.6, exactly — the score is a weighted sum, so it comes apart.
NodeRealvs1RPC
+25.1points
- Latency+17.3
- Availability+6.6
- Head freshness+0.7
- Correctness+0.5
The parts add to +25.1, exactly — the score is a weighted sum, so it comes apart.