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
24h window · 24 hours observed · generated 2026-08-26 14:55:05 UTC
| Metric | Tenderly | Blast API | 1RPC |
|---|---|---|---|
| Rank | 3 | 5 | 8 |
| Score | 93.1 | 86.0 | 64.7 |
| Status | Excellent | Good | Degraded |
| Availability | 99.95% | 99.97% | 90.50% |
| p50 latency | 20.4 ms | 104.3 ms | 259.6 ms |
| p95 latency | 73.4 ms | 121.6 ms | 2579.7 ms |
| p99 latency | 892.5 ms | 142.0 ms | 4625.5 ms |
| Correctness | 99.97% | 99.97% | 98.18% |
| Head lag | 0.51 blocks | 0.42 blocks | 0.94 blocks |
| Rate limited | 0 | 309 | 6,656 |
| Unsupported | 0 | 0 | 0 |
| Samples | 38,811 | 38,718 | 7,955 |
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
+7.1points
- Latency+7.2
- Head freshness−0.1
- Availability−0.0
- Correctness−0.0
The parts add to +7.1, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+28.3points
- Latency+23.7
- Availability+3.8
- Head freshness+0.5
- Correctness+0.4
The parts add to +28.3, exactly — the score is a weighted sum, so it comes apart.