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
- Tenderly
- PublicNode
- dRPC
- NodeReal
- Blast API
- Merkle
- MEV Blocker
- 1RPC
- Cloudflare
Side by side
24h window · 24 hours observed · generated 2026-08-28 14:09:10 UTC
| Metric | PublicNode | Blast API | Cloudflare |
|---|---|---|---|
| Rank | 2 | 5 | 9 |
| Score | 98.3 | 83.6 | 52.9 |
| Status | Excellent | Good | Degraded |
| Availability | 99.98% | 99.97% | 23.12% |
| p50 latency | 21.5 ms | 105.8 ms | 13.8 ms |
| p95 latency | 37.3 ms | 121.7 ms | 86.7 ms |
| p99 latency | 82.4 ms | 147.2 ms | 166.4 ms |
| Correctness | 99.98% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.41 blocks | no cohort |
| Rate limited | 0 | 378 | 21 |
| Unsupported | 0 | 0 | 1,102 |
| Samples | 37,838 | 37,510 | 37,519 |
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.7points
- Latency+14.8
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +14.7, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+45.4points
- Availability+29.7
- Head freshness*+9.4
- Latency+8.5
- Correctness−2.2
The parts add to +45.4, 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.