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
24h window · 24 hours observed · generated 2026-08-28 07:47:22 UTC
| Metric | NodeReal | Blast API | 1RPC |
|---|---|---|---|
| Rank | 4 | 5 | 8 |
| Score | 86.5 | 83.9 | 59.0 |
| Status | Good | Good | Degraded |
| Availability | 99.90% | 99.98% | 76.74% |
| p50 latency | 87.5 ms | 106.4 ms | 1326.0 ms |
| p95 latency | 100.2 ms | 122.9 ms | 7406.7 ms |
| p99 latency | 136.0 ms | 150.4 ms | 9776.0 ms |
| Correctness | 99.99% | 100.00% | 96.96% |
| Head lag | 0.34 blocks | 0.41 blocks | 0.94 blocks |
| Rate limited | 0 | 264 | 6,611 |
| Unsupported | 0 | 0 | 0 |
| Samples | 37,874 | 38,544 | 7,927 |
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.7points
- Latency+2.6
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +2.7, exactly — the score is a weighted sum, so it comes apart.
NodeRealvs1RPC
+27.5points
- Latency+17.0
- Availability+9.3
- Head freshness+0.7
- Correctness+0.6
The parts add to +27.5, exactly — the score is a weighted sum, so it comes apart.