Connecting to RPC nodes
I'm having issues connecting to the RPC node
Answer: First, make sure that your account is funded. You can check this on the Dashboard.
Second, make sure that you are connecting to the node using the IP address you've configured in the dashboard:
If you're on a remote server, you can run curl api.ipify.org to see the IP address you're connecting to the internet from.
If you're on a local machine (e.g. your laptop or PC), you can visit api.ipify.org to see your IP address.
If you enter your IP address and still have issues connecting, your VPS may use IPv6 for connecting to external services.
To fix this, get your current IPv6 address by running curl https://api6.ipify.org on your server (or visiting api6.ipify.org if you are trying to connect locally) and configuring that IP address in your Dashboard.
Note: the https://api6.ipify.org URL will ONLY work if you are on IPv6. If you are unsure whether your VPS is using IPv4 or IPv6, this is a great way to check!
Next, check the connection details for the node you're trying to connect to. All o7 Nodes require secure connections (HTTPS and WSS). If your connection URL includes http (not https) or ws (not wss), you will not be able to connect.
If you have done all the above things, and think something may be wrong with the node itself, check out the Status page to see if there are any known issues.
If you are still unable to connect, join our Discord channel using the link below.
How do I connect to the node from [insert service here]?
You can connect to our RPC nodes using the HTTPS endpoint and WSS (websocket) endpoint URLs.
For instance, here is how to connect to the node using the solana-web3.js library:
const connection = new solanaWeb3.Connection(
'https://node-address',
'wss://node-address'
);
If you're using a trading bot or other service, you will need to consult the documentation for that service to see how to connect to a Solana RPC node. Generally, you would provide these URLs in a configuration file, such as config.ini or .env:
RPC_ENDPOINT=https://node-address
RPC_WEBSOCKET_ENDPOINT=wss://node-address
If you're having trouble connecting, consider joining our Discord (link above) and ask the community!
How many transactions per second (TPS) can I make to the node?
We do not limit the number of transactions per second you can make with o7 Node.
How many requests per second (RPS) can I make to the node?
o7 Node enforces reasonable request limits for both HTTP and WebSocket connections. These limits are designed to keep transaction confirmation rates high for all users, reduce abuse of the node, as well as bad faith requests on the Solana network itself.
Currently, our rate limit is 400 requests per second. This rate limit can and will change over time as we adjust to traffic patterns.
Additional measures are deployed on our nodes to mitigate against spammer/DDOS traffic.
How do you ensure that transactions have the best chance to succeed?
Congestion on the Solana network can lead to failed transactions and high average response times. The Solana Explorer website shows the average ping time for transactions on the Solana network.
You may also be able to increase the priority fee for your transactions to increase the success rate.
What is the one-location-per-connection policy?
Starting May 1st, 2025, each account will be limited to connecting to RPC nodes in a single region (either Virginia or Frankfurt). This ensures optimal performance and helps us maintain high availability for all users.
Why are you implementing a one-location-per-connection policy?
This change helps us:
Ensure optimal performance by directing users to their closest node
Reduce network congestion and infrastructure strain
Maintain high availability and reliability for all users
Better allocate resources based on regional demand
How will the one-location-per-connection policy affect my applications?
If you're already connecting to only one region, there will be no impact. If you're currently connecting to both Virginia and Frankfurt nodes, you'll need to choose one region and update your connection configurations accordingly.
When does the one-location-per-connection policy take effect?
The timeline for the one-location-per-connection policy is as follows:
April 16, 2025: Initial announcement
April 23, 2025: Automatic region assignment based on IP address
May 1, 2025: Full enforcement begins
How will my default region be determined?
On April 23rd, 2025, we'll automatically assign a region to your account based on your most frequently used IP address location. You'll receive an email confirmation of this assignment.
How do I change my assigned region?
To change your region:
Log in to your o7 account dashboard
Go to Settings > Node Access
Select your preferred region (Virginia or Frankfurt)
Save changes
You can change your region once every 24 hours.
What are the connection strings for each region?
You can visit the Shared Nodes page at any time to see the most up-to-date list of RPC nodes and connection strings.
I have applications deployed in both regions. What should I do?
Users with legitimate multi-region requirements should consider:
Moving applications to a single region
Creating separate accounts for each region (not recommended for production workloads)
Please contact our support team if you need assistance with this transition.