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
6h window · 6.0 hours observed · generated 2026-10-08 16:36:49 UTC
| Metric | Tenderly | PublicNode | NodeReal | Blast API |
|---|---|---|---|---|
| Rank | 1 | 2 | 3 | 4 |
| Score | 99.5 | 98.0 | 86.7 | 81.9 |
| Status | Excellent | Excellent | Good | Good |
| Availability | 99.99% | 100.00% | 99.99% | 99.98% |
| p50 latency | 25.5 ms | 25.6 ms | 87.4 ms | 109.0 ms |
| p95 latency | 49.2 ms | 55.7 ms | 99.7 ms | 127.3 ms |
| p99 latency | 72.3 ms | 250.5 ms | 132.1 ms | 165.9 ms |
| Correctness | 99.99% | 100.00% | 100.00% | 99.99% |
| Head lag | 0.43 blocks | 0.46 blocks | 0.35 blocks | 0.41 blocks |
| Rate limited | 0 | 0 | 0 | 21 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 9,115 | 9,151 | 8,939 | 9,097 |
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
+1.4points
- Latency+1.4
- Head freshness+0.0
- Availability−0.0
- Correctness−0.0
The parts add to +1.4, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsNodeReal
+12.7points
- Latency+12.8
- Head freshness−0.1
- Correctness−0.0
- Availability+0.0
The parts add to +12.7, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+17.6points
- Latency+17.6
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +17.6, exactly — the score is a weighted sum, so it comes apart.