SUI Node Checker

Even though your node is synced or syncing blocks fine, having TPS to 0 is fine.

The tool only checks for the last few seconds, and it’s quite possible in that time window there were no blocks.

This error occurs when the checker is unable to reach your node. This is because the RPC port (9000) should be open to the public so the checker can run the required RPC checks.

To debug it further run the following command on your local terminal to verify whether the port is open:

Using Netcat

nc -vz <NODE IP/DNS> <RPC PORT>
# Example
nc -vz 10.0.1.1 9000

# Output if port is open
Connection to 10.0.1.1 port 9000 [tcp/cslistener] succeeded!
# Output if port is not open
nc: connectx to 10.0.1.1 port 9000 (tcp) failed: Connection refused

You can also use telnet to check

telnet <NODE IP/DNS> <RPC PORT>

Or run any of the following curl commands

curl --location --request POST '<NODE IP/DNS>:<RPC PORT>' --header 'Content-Type: application/json' --data-raw '{"jsonrpc":"2.0", "id":1,"method":"sui_getLatestCheckpointSequenceNumber"}'
# Example
curl --location --request POST 'https://fullnode.testnet.sui.io:443/' --header 'Content-Type: application/json' --data-raw '{"jsonrpc":"2.0", "id":1,"method":"sui_getLatestCheckpointSequenceNumber"}'

# OR if you have enabled metrics
curl <NODE IP/DNS>:9184/metrics

If non of the commands respond, which means there is some issue with your sui node process or you have not opened the port.

No action is required.

Just make sure the block tip number is always increasing indicating your node is healthy and syncing blocks fine. You verify that you can run the checker every few minutes.

If you don’t want to do the manual checks every time, you can onboard your node to Scale3 Autopilot and monitor the node’s block height and TPS trend.

This can be due to the following reasons:

• SUI network is generating blocks slowly, in this case, you don’t need to do anything.
• Your node specifications are below the recommended specifications, this will lead to your node falling behind the network. If that’s the case, you should increase resources for your node.

As per the official doc, these are the server specs

• CPUs: 10 core
• RAM: 32 GB
• Storage (SSD): 2 TB

If you want to analyze your server trends over a period of time, you can check out Scale3 Autopilot to gain more insights.

To check if you have SUI node running, ssh to the server and make an RPC curl request to verify

curl --location --request POST '<NODE IP/DNS>:<RPC PORT>' --header 'Content-Type: application/json' --data-raw '{"jsonrpc":"2.0", "id":1,"method":"sui_getLatestCheckpointSequenceNumber"}'

If it’s a docker/k8s setup, you can check if the pod or container is up and running fine.

If its systemd setup, check if the sui-node service is up

systemctl status sui-node

We would highly recommend onboarding your node to Scale3 Autopilot and set up monitoring and alerts so you can easily debug when in need.

The checker checks for your node block tip with the tip of the network, if it’s too off, probably it can be due to two reasons:

1. You have selected the wrong network when checking your node on Node Checker.
2. There was a network reset or you are in an unsupported network.

To fix your node, you can wipe your DB directories and restart the node.

The sui-node version does not match the sui-node version used by the checker.

You can update your sui-node to the right version by checking releases.

This is due to the SUI community node being down or under maintenance.

If you are running SUI node with systemd

you can check the sui command in service file. There you will find an argument rpc-client-url which has port.

If service has --config-file argument, check the config file contents, json-rpc-address should have RPC port.

If non present, assume default is 9000.

If you are running docker

run docker ps and you will see the port mapping.

Yes! You can whitelist the following IPs for your RPC port. Though we do not guarantee it would always work, you can still try.

• 34.168.21.71
• 34.82.137.54
• 35.199.188.63