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-27 06:54:48 UTC
| Metric | NodeReal | 1RPC | Cloudflare |
|---|---|---|---|
| Rank | 4 | 8 | 9 |
| Score | 86.4 | 58.2 | 52.4 |
| Status | Good | Degraded | Degraded |
| Availability | 100.00% | 74.93% | 23.13% |
| p50 latency | 87.2 ms | 2024.4 ms | 16.0 ms |
| p95 latency | 100.4 ms | 6590.4 ms | 91.9 ms |
| p99 latency | 129.5 ms | 9196.2 ms | 243.9 ms |
| Correctness | 100.00% | 96.63% | 100.00% |
| Head lag | 0.34 blocks | 0.95 blocks | no cohort |
| Rate limited | 0 | 6,638 | 36 |
| Unsupported | 0 | 0 | 1,142 |
| Samples | 38,112 | 7,964 | 38,670 |
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
+28.2points
- Latency+16.8
- Availability+10.0
- Head freshness+0.7
- Correctness+0.7
The parts add to +28.2, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsCloudflare
+34.0points
- Availability+29.7
- Head freshness*+9.6
- Latency−3.1
- Correctness−2.2
The parts add to +34.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.