Hi All –
Gateway statistics for February 2025 are here:
https://pad.carback.us/drive/#/2/drive/view/-OmT+xmwm78g8P07ss9NLwXe2ZRHjZrxWlu1AvLm0k8/
You need to only be worried about the latency.grpc and latency.websocket columns. The value -1 means your gateway failed the test. Any positive number means it passed.
The highest score achievable is 80. You should ignore this metric for now as it is used for internal consistency check and is not relevant criteria at this time.
Main takeaways:
- There are nodes who are not exposing the proper ports to the internet via the test machine we used, located in the US.
- A large number of nodes are accessible, but do not have websocket certificates either manually set up or via the automated foundation-run zerossl system. This means they are inaccessible to haven and other webclients except via the built-in node proxying.
- Most nodes have pretty good stats otherwise.
We are looking at a solution to collate this data from different test machines across the internet to eliminate #1 above.
If you are in category 1 AND not in a country that blocks all US machines then you have a problem that needs to be resolved now. Your node’s gateway is not accessible via an open machine on the internet.
You can check your connectivity with the following command:
openssl s_client -alpn h2 -showcerts -connect "[gateway ip address]:22840"
Where [gateway ip address] is the gateway ip address or dns hostname and 22840 is the port number hosting the gateway service.
To run this command, you will need to have openssl installed. If you are running a mac or a linux machine, it should be installed already. Otherwise, ask a search engine to get instructions. When you run this command, you should see something like:
% openssl s_client -alpn h2 -showcerts -connect "[gateway ip address]:22840"
Connecting to 194.163.163.77
CONNECTED(00000003)
Can't use SSL_get_servername
depth=0 C=PT, ST=PT, L=Porto, O=xxnetwork, OU=nodes, CN=xx.network, [email protected]
verify error:num=18:self-signed certificate
verify return:1
depth=0 C=PT, ST=PT, L=Porto, O=xxnetwork, OU=nodes, CN=xx.network, [email protected]
verify return:1
---
...
If the command produces no output after 5 seconds, your configuration is broken. Most likely you have installed a firewall or are not forwarding ports properly to and from the internet. Please ask for support in the forum or discord.
If you are in category 1, the foundation will no longer be allowing your node to use the staking tool starting in Q2. The foundation expects to warn nodes for which we have contact information by the end of Q1 and to start banning nodes in Q2. We will also be raising this issue of low-performing and low-connectivity nodes in council to decide what else can be done (slashing, banning, etc).
If you are in category 2 then you do not need to do anything at this time. We will post more information on how to fix this at a later date once we have analyzed the root cause of why some nodes are not working.
For developers, you can download and run the node stats tool yourself here:
NOTE: Non-developers should not bother attempting to run this tool. Download the csv or preview it directly and search for your gateway’s ip or dns name.
