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
- MEV Blocker
- Merkle
- Cloudflare
- 1RPC
Side by side
1h window · 60 minutes observed · generated 2026-08-28 14:20:01 UTC
| Metric | PublicNode | Blast API | Cloudflare |
|---|---|---|---|
| Rank | 2 | 5 | 8 |
| Score | 98.3 | 80.5 | 50.4 |
| Status | Excellent | Good | Degraded |
| Availability | 100.00% | 100.00% | 23.28% |
| p50 latency | 22.7 ms | 108.3 ms | 15.6 ms |
| p95 latency | 37.8 ms | 123.7 ms | 88.8 ms |
| p99 latency | 78.0 ms | 137.7 ms | 150.1 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.55 blocks | 0.43 blocks | no cohort |
| Rate limited | 0 | 0 | 0 |
| Unsupported | 0 | 0 | 46 |
| Samples | 1,596 | 1,589 | 1,590 |
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
+17.8points
- Latency+17.9
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +17.8, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+47.9points
- Availability+29.7
- Latency+11.1
- Head freshness*+9.3
- Correctness−2.2
The parts add to +47.9, 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.