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 17:20:58 UTC
| Metric | Tenderly | Blast API | Cloudflare |
|---|---|---|---|
| Rank | 1 | 5 | 8 |
| Score | 99.4 | 78.3 | 46.1 |
| Status | Excellent | Good | Poor |
| Availability | 99.98% | 99.99% | 23.08% |
| p50 latency | 20.2 ms | 109.0 ms | 17.6 ms |
| p95 latency | 33.5 ms | 127.5 ms | 105.0 ms |
| p99 latency | 66.3 ms | 154.6 ms | 262.0 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.41 blocks | no cohort |
| Rate limited | 0 | 39 | 0 |
| Unsupported | 0 | 0 | 257 |
| Samples | 8,677 | 8,656 | 8,678 |
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 Tenderly, the highest scorer of those selected.
TenderlyvsBlast API
+21.1points
- Latency+21.2
- Head freshness−0.1
- Availability−0.0
- Correctness−0.0
The parts add to +21.1, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsCloudflare
+53.3points
- Availability+29.7
- Latency+16.4
- Head freshness*+9.4
- Correctness−2.2
The parts add to +53.3, 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.