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.5 days observed · generated 2026-08-27 07:56:40 UTC
| Metric | PublicNode | Blast API | Cloudflare |
|---|---|---|---|
| Rank | 1 | 5 | 9 |
| Score | 99.4 | 85.3 | 55.3 |
| Status | Excellent | Good | Degraded |
| Availability | 99.97% | 99.98% | 23.11% |
| p50 latency | 18.2 ms | 104.5 ms | 15.0 ms |
| p95 latency | 33.5 ms | 122.0 ms | 87.1 ms |
| p99 latency | 69.7 ms | 144.6 ms | 252.5 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.42 blocks | no cohort |
| Rate limited | 0 | 1,076 | 77 |
| Unsupported | 0 | 0 | 2,826 |
| Samples | 96,776 | 95,483 | 95,864 |
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.1points
- Latency+14.1
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +14.1, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+44.1points
- Availability+29.7
- Head freshness*+9.4
- Latency+7.2
- Correctness−2.2
The parts add to +44.1, 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.