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
- Tenderly
- PublicNode
- dRPC
- NodeReal
- Blast API
- Merkle
- MEV Blocker
- Cloudflare
- 1RPC
Side by side
6h window · 6.0 hours observed · generated 2026-08-27 22:24:52 UTC
| Metric | Tenderly | Blast API | Merkle | MEV Blocker |
|---|---|---|---|---|
| Rank | 1 | 5 | 6 | 7 |
| Score | 99.4 | 78.4 | 70.8 | 69.5 |
| Status | Excellent | Good | Degraded | Degraded |
| Availability | 100.00% | 99.92% | 100.00% | 99.94% |
| p50 latency | 18.9 ms | 107.8 ms | 109.1 ms | 124.2 ms |
| p95 latency | 32.5 ms | 125.4 ms | 190.5 ms | 216.4 ms |
| p99 latency | 55.5 ms | 152.4 ms | 231.1 ms | 239.4 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 99.98% |
| Head lag | 0.47 blocks | 0.41 blocks | 0.57 blocks | 0.39 blocks |
| Rate limited | 0 | 44 | 1,395 | 0 |
| Unsupported | 0 | 0 | 14 | 0 |
| Samples | 8,771 | 8,765 | 2,084 | 8,764 |
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
+21.1points
- Latency+21.1
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +21.1, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+28.6points
- Latency+28.5
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +28.6, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMEV Blocker
+29.9points
- Latency+30.0
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +29.9, exactly — the score is a weighted sum, so it comes apart.