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
30d window · 2.9 days observed · generated 2026-08-27 18:38:50 UTC
| Metric | Tenderly | Blast API | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 5 | 6 | 8 |
| Score | 96.8 | 84.8 | 78.4 | 62.4 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.96% | 99.98% | 99.98% | 84.99% |
| p50 latency | 19.8 ms | 105.1 ms | 106.9 ms | 225.7 ms |
| p95 latency | 49.8 ms | 122.6 ms | 195.5 ms | 4391.3 ms |
| p99 latency | 733.8 ms | 147.6 ms | 242.1 ms | 7602.5 ms |
| Correctness | 99.99% | 99.99% | 100.00% | 97.48% |
| Head lag | 0.50 blocks | 0.42 blocks | 0.49 blocks | 0.91 blocks |
| Rate limited | 0 | 1,214 | 18,211 | 19,479 |
| Unsupported | 0 | 0 | 223 | 0 |
| Samples | 113,395 | 112,811 | 26,289 | 23,721 |
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
+12.1points
- Latency+12.2
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +12.1, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+18.4points
- Latency+18.5
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +18.4, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+34.4points
- Latency+27.5
- Availability+6.0
- Correctness+0.5
- Head freshness+0.5
The parts add to +34.4, exactly — the score is a weighted sum, so it comes apart.