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-26 20:19:00 UTC
| Metric | Blast API | Merkle | 1RPC |
|---|---|---|---|
| Rank | 5 | 6 | 9 |
| Score | 78.4 | 70.7 | 0.0 |
| Status | Good | Degraded | Poor |
| Availability | 100.00% | 100.00% | 0.00% |
| p50 latency | 106.7 ms | 109.5 ms | 0.0 ms |
| p95 latency | 123.7 ms | 193.6 ms | 0.0 ms |
| p99 latency | 143.6 ms | 234.4 ms | 0.0 ms |
| Correctness | 100.00% | 100.00% | not measured |
| Head lag | 0.41 blocks | 0.40 blocks | no cohort |
| Rate limited | 92 | 1,349 | 1,481 |
| Unsupported | 0 | 15 | 0 |
| Samples | 8,453 | 1,938 | 1,698 |
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 Blast API, the highest scorer of those selected.
Blast APIvsMerkle
+7.8points
- Latency+7.8
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +7.8, exactly — the score is a weighted sum, so it comes apart.
Blast APIvs1RPC
+78.4points
- Availability+40.0
- Correctness*+20.0
- Head freshness*+9.5
- Latency*+8.9
The parts add to +78.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.