What are the best Solana public RPC endpoints for development and production?
Key Takeaways
- Solana provides free public RPC endpoints for mainnet, devnet, and testnet, but they are rate-limited and not suitable for production.
- Public endpoints are shared infrastructure; heavy usage can lead to throttling or dropped connections.
- For production dApps, a dedicated RPC provider offers higher rate limits, better uptime, and lower latency.
- OnFinality provides Solana RPC endpoints with scalable infrastructure and global coverage.
- Always use a local validator (solana-test-validator) during early development to avoid unnecessary public RPC calls.
- Cache expensive RPC calls like getProgramAccounts to reduce load and improve performance.
- Choose an RPC provider based on your throughput needs, geographic requirements, and budget.
Official Solana Public RPC Endpoints
Solana provides public RPC endpoints for each cluster. These are free to use but come with significant limitations.
The official endpoints are:
- Mainnet: https://api.mainnet.solana.com
- Devnet: https://api.devnet.solana.com
- Testnet: https://api.testnet.solana.com
| Criterion | What to check | Why it matters |
|---|---|---|
| Cluster | Endpoint | Use the correct endpoint for your target network. |
| Mainnet | https://api.mainnet.solana.com | Production network with real SOL. |
| Devnet | https://api.devnet.solana.com | Development network with free test SOL. |
| Testnet | https://api.testnet.solana.com | Validator testing network. |
Limitations of Public RPC Endpoints
Public endpoints are shared among all users, which introduces several constraints:
Rate limits are enforced to prevent abuse, typically around 100 requests per 10 seconds per IP. Exceeding this results in HTTP 429 errors.
No uptime guarantee: the endpoints may become unavailable during high traffic or maintenance.
Latency can be higher and inconsistent due to shared infrastructure.
Not suitable for production applications that require reliability and performance.
- Rate limiting: ~100 req/10s per IP
- No SLA or uptime guarantee
- Higher and variable latency
- Potential for IP-based throttling
When to Upgrade to a Dedicated RPC Provider
If your application serves real users, processes high transaction volumes, or requires low latency, you should consider a dedicated RPC provider.
Signs you need to upgrade:
You consistently hit rate limits on public endpoints.
Your users experience slow transaction confirmation times.
You need access to archival data or advanced APIs like getProgramAccounts with filters.
You require a geographically distributed infrastructure for global users.
- Production dApps with real users
- High-frequency trading or DeFi bots
- Applications needing archival data
- Projects with global user base requiring low latency
How OnFinality Solves Public RPC Limitations
OnFinality offers Solana RPC endpoints designed for production workloads. Our infrastructure provides higher rate limits, dedicated node options, and global coverage.
Key benefits include:
Higher rate limits: Scale your requests without hitting caps.
Dedicated nodes: Isolated resources for consistent performance.
Global endpoints: Reduce latency for users worldwide.
SLA-backed uptime: Reliable infrastructure for mission-critical apps.
Easy integration: Compatible with standard Solana JSON-RPC methods.
- Higher rate limits than public endpoints
- Dedicated node options for maximum performance
- Global endpoint distribution
- SLA-backed uptime guarantee
- Full compatibility with Solana RPC methods
Best Practices for Using Solana RPC
Whether you use public or private endpoints, following best practices can improve performance and reduce costs.
Cache expensive calls: Methods like getProgramAccounts and getSignaturesForAddress should be cached and served from your backend.
Use WebSocket subscriptions for real-time updates instead of polling.
Batch requests when possible to reduce overhead.
During development, use solana-test-validator locally to avoid hitting public endpoints.
Monitor your RPC usage and set up alerts for rate limiting or errors.
- Cache getProgramAccounts and getSignaturesForAddress
- Use WebSocket subscriptions over polling
- Batch multiple requests in one call
- Use local validator for development
- Monitor RPC usage and errors
Comparing Public vs Private RPC for Solana
The table below summarizes key differences between public and private RPC options.
| Criterion | What to check | Why it matters |
|---|---|---|
| Rate Limits | Public: ~100 req/10s | Private: Custom limits based on plan |
| Uptime SLA | Public: None | Private: Typically 99.9%+ SLA |
| Latency | Public: Variable | Private: Consistent, low latency |
| Cost | Public: Free | Private: Pay-as-you-go or subscription |
| Dedicated Resources | Public: Shared | Private: Optional dedicated nodes |
Getting Started with OnFinality Solana RPC
To start using OnFinality's Solana RPC endpoints, follow these steps:
1. Sign up for a free account at OnFinality.
2. Navigate to the API Services section and select Solana.
3. Choose your plan (shared or dedicated) based on your needs.
4. Copy your API endpoint and use it in your application.
OnFinality supports all standard Solana RPC methods, including getBalance, getTransaction, sendTransaction, and more.
- Free tier available for testing
- Simple API key authentication
- Full JSON-RPC compatibility
- 24/7 support for paid plans
Frequently Asked Questions
What is the Solana public RPC endpoint?
The official Solana public RPC endpoint for mainnet is https://api.mainnet.solana.com. For devnet, use https://api.devnet.solana.com, and for testnet, https://api.testnet.solana.com.
Are Solana public RPC endpoints free?
Yes, they are free to use but come with rate limits and no uptime guarantees. They are suitable for development and light usage only.
What are the rate limits for Solana public RPC?
The public endpoints typically allow around 100 requests per 10 seconds per IP address. Exceeding this results in HTTP 429 (Too Many Requests) errors.
Can I use public RPC for production?
It is not recommended. Public RPC endpoints lack reliability, have low rate limits, and can become unavailable. For production, use a dedicated RPC provider like OnFinality.
How do I get a Solana RPC endpoint from OnFinality?
Sign up at OnFinality, go to API Services, select Solana, and choose a plan. You'll receive an API endpoint with higher rate limits and better reliability.
Ethereum
Solana
Polygon
Base
Arbitrum
BNB Chain
Polkadot
Optimism
