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 · 2.2 days observed · generated 2026-08-27 02:35:53 UTC
| Metric | NodeReal | 1RPC | Cloudflare |
|---|---|---|---|
| Rank | 4 | 8 | 9 |
| Score | 88.9 | 62.6 | 55.9 |
| Status | Good | Degraded | Degraded |
| Availability | 99.79% | 85.50% | 23.10% |
| p50 latency | 87.3 ms | 225.7 ms | 15.3 ms |
| p95 latency | 99.9 ms | 4391.3 ms | 89.0 ms |
| p99 latency | 123.5 ms | 7602.5 ms | 254.5 ms |
| Correctness | 99.99% | 97.48% | 100.00% |
| Head lag | 0.35 blocks | 0.91 blocks | no cohort |
| Rate limited | 0 | 14,990 | 77 |
| Unsupported | 0 | 0 | 2,566 |
| Samples | 85,893 | 18,580 | 87,198 |
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.
NodeRealvs1RPC
+26.3points
- Latency+19.4
- Availability+5.7
- Head freshness+0.7
- Correctness+0.5
The parts add to +26.3, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsCloudflare
+33.0points
- Availability+29.6
- Head freshness*+9.6
- Latency−4.0
- Correctness−2.2
The parts add to +33.0, exactly — the score is a weighted sum, so it comes apart. Components marked * were measured for only one of the two; the other’s weight is spread across what it does have, which is why the two sides can carry different weights for the same row.