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— showing the top 4 by score. Click to change.
Side by side
1h window · 60 minutes observed · generated 2026-10-08 16:35:19 UTC
| Metric | Tenderly | PublicNode | NodeReal | Blast API |
|---|---|---|---|---|
| Rank | 1 | 2 | 3 | 4 |
| Score | 99.5 | 97.4 | 82.4 | 77.1 |
| Status | Excellent | Excellent | Good | Good |
| Availability | 100.00% | 100.00% | 100.00% | 100.00% |
| p50 latency | 26.1 ms | 25.6 ms | 86.9 ms | 109.5 ms |
| p95 latency | 45.6 ms | 52.4 ms | 100.6 ms | 126.0 ms |
| p99 latency | 61.5 ms | 228.8 ms | 124.9 ms | 157.5 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 100.00% |
| Head lag | 0.45 blocks | 0.47 blocks | 0.36 blocks | 0.42 blocks |
| Rate limited | 0 | 0 | 0 | 0 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 1,605 | 1,612 | 1,568 | 1,597 |
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
+2.1points
- Latency+2.1
- Head freshness+0.0
- Availability+0.0
- Correctness+0.0
The parts add to +2.1, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsNodeReal
+17.0points
- Latency+17.1
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +17.0, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+22.3points
- Latency+22.4
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +22.3, exactly — the score is a weighted sum, so it comes apart.