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
1h window · 60 minutes observed · generated 2026-08-27 19:55:54 UTC
| Metric | Tenderly | Blast API | 1RPC |
|---|---|---|---|
| Rank | 1 | 5 | 9 |
| Score | 99.4 | 77.4 | 0.0 |
| Status | Excellent | Good | Poor |
| Availability | 100.00% | 99.81% | 0.00% |
| p50 latency | 17.8 ms | 108.9 ms | 0.0 ms |
| p95 latency | 31.9 ms | 127.5 ms | 0.0 ms |
| p99 latency | 56.8 ms | 154.4 ms | 0.0 ms |
| Correctness | 100.00% | 100.00% | not measured |
| Head lag | 0.50 blocks | 0.42 blocks | no cohort |
| Rate limited | 0 | 8 | 265 |
| Unsupported | 0 | 0 | 0 |
| Samples | 1,606 | 1,610 | 315 |
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
+22.0points
- Latency+22.0
- Head freshness−0.1
- Availability+0.1
- Correctness+0.0
The parts add to +22.0, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+99.4points
- Availability+40.0
- Latency*+30.0
- Correctness*+20.0
- Head freshness*+9.4
The parts add to +99.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.