Full API node statistics with beem - April 10th 2018
Complete node list
There are several lists of public nodes, but none of them is complete:
- steem.io (8 nodes)
- steem.center (10 nodes)
- steemistry.com (10 nodes)
- geo.steem.pl (13 nodes)
I have a list of 15 nodes. Please let me know if something is wrong or missing. All nodes have support for https://. For nodes with websocket support (WSS is yes), wss:// has to put in front.
| Server | WSS | Ran By | Version |
|---|---|---|---|
| steemd.privex.io | yes | 0.19.2 | |
| steemd.pevo.science | yes | 0.19.2 | |
| rpc.steemliberator.com | yes | 0.19.2 | |
| rpc.buildteam.io | yes | 0.19.2 | |
| gtg.steem.house:8090 | yes | 0.19.2 | |
| rpc.steemviz.com | yes | 0.19.2 | |
| seed.bitcoiner.me | yes | 0.19.2 | |
| steemd.steemgigs.org | yes | 0.19.2 | |
| steemd.minnowsupportproject.org | yes | 0.19.2 | |
| rpc.curiesteem.com | no | 0.19.2 | |
| api.steem.house | no | 0.19.4 | |
| appbasetest.timcliff.com | yes | 0.19.4 | |
| api.steemit.com | no | Steemit Inc. | 0.19.4 |
| steemd.steemitstage.com | no | Steemit Inc. | 0.19.4 |
| steemd.steemitdev.com | no | Steemit Inc. | 0.19.4 |
Working node
A node is listed, when:
- blocks can be streamed
- account history is possible
- votes, a comment and an account can successfully be fetched.
It is measured how many blocks and how many account operation can be streamed in 15 seconds. The third parameter is the mean duration in seconds for the rpc calls to fetch account, comment and votes data.
The following statistics were gained with beem. nodes which are supporting websockets are tested with wss:// and https://. When a node with websocket connection passed all tests, he is listed with an x in WSS. When a node with https:// connection passed all tests, he ist listed without x in WSS.
Statistics
| Server | WSS | blocks in 15 s | account op in 15 s | duration for rpc call in s |
|---|---|---|---|---|
| steemd.privex.io | x | 182 | 29030 | 0.02 |
| steemd.pevo.science | x | 202 | 39040 | 0.13 |
| rpc.buildteam.io | x | 196 | 53054 | 0.04 |
| rpc.steemviz.com | x | 202 | 55056 | 0.03 |
| steemd.minnowsupportproject.org | x | 202 | 49050 | 0.02 |
| rpc.buildteam.io | 34 | 6007 | 0.16 | |
| steemd.minnowsupportproject.org | 14 | 4005 | 0.70 | |
| steemd.pevo.science | 9 | 4005 | 0.14 | |
| rpc.steemviz.com | 26 | 5006 | 0.36 | |
| steemd.privex.io | 1 | 1 | 9.45 | |
| api.steem.house | 1 | 1 | 0.38 | |
| api.steemit.com | 24 | 12013 | 0.47 |
At the moment only 7 from 15 available full API nodes are working.
Leave Full API node statistics with beem - April 10th 2018 to:
Read more #steemdev posts
Best Posts From Holger
We have not curated any of holger80's posts yet. But you can encourage our curation team to review posts by visiting them regularly and by referring other readers. Because we give priority to frequently read content.
More Posts From Holger
- BLURT is under heavy spam attack right now
- Beempy post will create a new post, when changing the title in the yaml header, will fix this soon.
- EOS inflates their blocktivity stats by massively sending batched transactions with a value of 0.0001 EOS
- Verify blocktivity numbers for Hive and Blurt
- How to use a coldcard MK3 to derive your new account password from a 24 word seed
- Update for beem: improved account history handling
- How to use beempy in tails (e.g. for changing the account keys)
- update for beem: make beem/beempy ready for tails
- update for beem: changes regarding HF24
- update for beem: compatibility issues with HF24 have been fixed