Composite score
68.8
Rank 10 of 12
1,403 samples
Providers
The Solana Foundation's public mainnet-beta endpoint. Documented as rate limited and explicitly not intended for production use.
public · rank 10 of 12
Website (opens in a new tab)Documentation (opens in a new tab)
1h window · 60 minutes observed · 1 chain
68.8
Rank 10 of 12
1,403 samples
98.15%
Rate limits and unsupported methods excluded
540.4ms
p50 33.4 · p99 967.5
100.00%
1,376 responses judged
12 providers scored against each other.
| Component | Weight | Measured | Score |
|---|---|---|---|
| Availability | 40% | 98.15 % | 98.1 |
| Latency | 30% | 540.40 ms | 0.0 |
| Correctness | 20% | 100.00 % | 100.0 |
| Head freshness | 10% | 0.38 blocks behind | 95.4 |
Failures are classified rather than collapsed into one count. Our own failures are shown for transparency but are never counted against the provider.
| Outcome | Count | Share |
|---|---|---|
| Successful | 1,376 | 98.08% |
| Provider failure | 0 | 0.00% |
| Network failure | 26 | 1.85% |
| Rate limited | 0 | 0.00% |
| Unsupported method | 0 | 0.00% |
| Agent error | 0 | 0.00% |
| Measurement error | 1 | 0.07% |
The only figures on this site that are not measurements. A limit is a claim the operator makes, so it is quoted with the page it came from and the day it was read — never inferred from a refused request, which would put a number against a company that never stated it.
New connectionson Solana40 / 10s
per IP address
“Maximum connection rate per 10 seconds per IP: 40”
Concurrent connectionson Solana40
per IP address
“Maximum concurrent connections per IP: 40”
Data transferredon Solana100 MB / 30s
per IP address
“Maximum amount of data per 30 seconds: 100 MB”
Requestson Solana100 / 10s
per IP address
“Maximum number of requests per 10 seconds per IP: 100”
Requests to one methodon Solana40 / 10s
per IP address
“Maximum number of requests per 10 seconds per IP for a single RPC: 40”
Quoted, not measured. Read 2026-08-15 from solana.com— a provider can change this without telling anybody, so the date is part of the figure.
The status page judges every provider against an objective this site publishes. That is not an SLA, and a provider that misses it has not broken a promise — so what it actually promised, where it promised anything, belongs here in its own words. The objective
“The public RPC endpoints are not intended for production applications. Please use dedicated/private RPC servers when you launch your application, drop NFTs, etc.”
Quoted, not measured. Read 2026-08-15 from solana.com
An availability percentage has no shape. This is the shape: what departed from this provider’s own normal behaviour, and what its normal behaviour already is. How an incident is decided
None. Every call measured on Solana Foundation succeeded often enough, often enough of the time, not to qualify.
The same measurements, grouped by the vantage point they were taken from. Latency is a property of a network path, so a provider fast from one region is not necessarily fast from another — and the composite score above is an average across whichever regions are reporting.
Percentiles are over successful responses only. A request that timed out is not a latency sample; it is counted against availability instead.
A live badge for Solana Foundation on Solana, free to use. It renders from the current measurement each time it loads, so it cannot be frozen at a good day — which is what makes it worth putting in a README. Every badge and parameter
The composite score, coloured by band.
Markdown
[](https://rpcnode.io/providers/solana-foundation)HTML
<a href="https://rpcnode.io/providers/solana-foundation"><img src="https://rpcnode.io/badge/provider/solana-foundation.svg?chain=solana" alt="Solana Foundation on RPCNode.IO"></a>