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 02:39:14 UTC
| Metric | PublicNode | Blast API | Cloudflare |
|---|---|---|---|
| Rank | 2 | 5 | 9 |
| Score | 98.8 | 83.9 | 55.3 |
| Status | Excellent | Good | Degraded |
| Availability | 99.99% | 99.99% | 23.16% |
| p50 latency | 17.2 ms | 103.9 ms | 12.9 ms |
| p95 latency | 35.2 ms | 118.1 ms | 72.1 ms |
| p99 latency | 92.0 ms | 139.2 ms | 260.9 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.42 blocks | no cohort |
| Rate limited | 0 | 71 | 6 |
| Unsupported | 0 | 0 | 266 |
| Samples | 9,243 | 9,097 | 9,166 |
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 PublicNode, the highest scorer of those selected.
PublicNodevsBlast API
+14.9points
- Latency+15.0
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +14.9, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+43.5points
- Availability+29.7
- Head freshness*+9.4
- Latency+6.6
- Correctness−2.2
The parts add to +43.5, 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.