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
7d window · 2.7 days observed · generated 2026-08-27 14:20:14 UTC
| Metric | Tenderly | Blast API | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 5 | 6 | 8 |
| Score | 96.1 | 85.0 | 78.5 | 62.4 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.96% | 99.98% | 99.98% | 84.99% |
| p50 latency | 19.8 ms | 104.9 ms | 106.6 ms | 225.7 ms |
| p95 latency | 53.7 ms | 122.3 ms | 196.1 ms | 4391.3 ms |
| p99 latency | 774.7 ms | 146.3 ms | 243.1 ms | 7602.5 ms |
| Correctness | 99.99% | 99.99% | 100.00% | 97.48% |
| Head lag | 0.50 blocks | 0.42 blocks | 0.48 blocks | 0.91 blocks |
| Rate limited | 0 | 1,154 | 17,099 | 18,265 |
| Unsupported | 0 | 0 | 207 | 0 |
| Samples | 106,413 | 105,842 | 24,643 | 22,334 |
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
+11.1points
- Latency+11.2
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +11.1, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+17.6points
- Latency+17.6
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +17.6, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+33.7points
- Latency+26.7
- Availability+6.0
- Correctness+0.5
- Head freshness+0.5
The parts add to +33.7, exactly — the score is a weighted sum, so it comes apart.