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
6h window · 6.0 hours observed · generated 2026-08-27 04:12:40 UTC
| Metric | Tenderly | PublicNode | NodeReal | 1RPC |
|---|---|---|---|---|
| Rank | 1 | 2 | 4 | 8 |
| Score | 99.4 | 99.2 | 86.1 | 59.0 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 100.00% | 99.99% | 99.99% | 76.94% |
| p50 latency | 18.6 ms | 17.4 ms | 86.8 ms | 2024.4 ms |
| p95 latency | 32.2 ms | 33.2 ms | 98.4 ms | 6590.4 ms |
| p99 latency | 68.0 ms | 80.7 ms | 116.9 ms | 9196.2 ms |
| Correctness | 100.00% | 100.00% | 99.99% | 96.63% |
| Head lag | 0.48 blocks | 0.49 blocks | 0.33 blocks | 0.95 blocks |
| Rate limited | 0 | 0 | 0 | 1,424 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 8,419 | 8,515 | 8,323 | 1,990 |
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.
TenderlyvsPublicNode
+0.2points
- Latency+0.2
- Head freshness+0.0
- Availability+0.0
- Correctness+0.0
The parts add to +0.2, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsNodeReal
+13.3points
- Latency+13.5
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +13.3, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+40.4points
- Latency+30.0
- Availability+9.2
- Correctness+0.7
- Head freshness+0.5
The parts add to +40.4, exactly — the score is a weighted sum, so it comes apart.