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
- 1RPC
- Cloudflare
Side by side
24h window · 24 hours observed · generated 2026-08-28 08:14:41 UTC
| Metric | PublicNode | Blast API | 1RPC |
|---|---|---|---|
| Rank | 2 | 5 | 8 |
| Score | 97.7 | 83.9 | 59.0 |
| Status | Excellent | Good | Degraded |
| Availability | 99.98% | 99.98% | 76.74% |
| p50 latency | 22.4 ms | 106.4 ms | 1326.0 ms |
| p95 latency | 41.0 ms | 122.8 ms | 7406.7 ms |
| p99 latency | 93.6 ms | 150.1 ms | 9776.0 ms |
| Correctness | 99.98% | 100.00% | 96.96% |
| Head lag | 0.48 blocks | 0.41 blocks | 0.94 blocks |
| Rate limited | 0 | 303 | 6,453 |
| Unsupported | 0 | 0 | 0 |
| Samples | 38,007 | 37,654 | 7,746 |
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 PublicNode, the highest scorer of those selected.
PublicNodevsBlast API
+13.9points
- Latency+13.9
- Head freshness−0.1
- Correctness−0.0
- Availability+0.0
The parts add to +13.9, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+38.7points
- Latency+28.3
- Availability+9.3
- Correctness+0.6
- Head freshness+0.5
The parts add to +38.7, exactly — the score is a weighted sum, so it comes apart.