Full API node update - (20/1/2019)
2019-01-19T20:10:02 - 2019-01-20T20:10:02 (UTC)
@fullnodeupdate provides daily updates about the state of all available full API node server.
More information about full nodes and a complete RPC node list can be fund in this post.
List of failing nodes
This table includes a list of all nodes which were not able to answer to a
get_config api call within 30 seconds.
|node||hours with failure||percentage|
List of working nodes (At least once in the last 24h)
This table includes all nodes which were able to a
get_config call in 30 seconds.The achieved mean duration values are shown. The returned version is also shown.When a node failes, its mean value is increased as it is counted as 30 seconds
|node||mean time [s]||version|
In this test, it is measured how many blocks a node can stream in 30 seconds.
List of working nodes - block streaming
This table includes all nodes which were able to stream at least one block within 30 seconds.The achieved minimum, maximum and mean blocks per seconds values are shown. When a node failes, its mean value is reduced as it is counted as 0 blocks per seconds
|https://steemd.minnowsupportproject.org||28.1 - 35.4||31.5|
|https://rpc.steemviz.com||18.8 - 19.8||19.4|
|https://api.steemitdev.com||7.9 - 9.2||8.4|
|https://api.steemit.com||6.6 - 9.0||7.9|
|https://anyx.io||2.0 - 2.7||2.5|
|https://appbasetest.timcliff.com||0.9 - 0.9||0.9|
|https://steemd.privex.io||0.9 - 0.9||0.9|
Measuring irreversible block delays
In this test, the time delay of the irreversible block to the current time is measured.
List of working nodes - block delays
This table includes all nodes which were able to stream at least one block within 30 seconds.The achieved minimum, maximum and mean irreversible block delay times in seconds are shown. When a node failes, its mean value is reduced as it is counted as 120 seconds.
|node||block delay||mean delay|
|https://api.steemitdev.com||47.64 - 71.51||58.216|
|https://rpc.steemviz.com||50.47 - 68.79||59.410|
|https://api.steemit.com||49.71 - 72.77||60.300|
|https://appbasetest.timcliff.com||52.41 - 71.75||61.310|
|https://steemd.minnowsupportproject.org||45.58 - 76.05||62.414|
|https://anyx.io||52.18 - 75.84||62.678|
|https://steemd.privex.io||54.87 - 71.03||63.161|
In this test, it is measured how many account operation a node can stream.
List of working nodes - account history
This table includes all nodes which were able to stream at least one account history operation within 15 seconds.The achieved minimum, maximum and mean account transaction per seconds values are shown. When a node failes, its mean value is reduced as it is counted as 0 history operation per seconds
|https://steemd.minnowsupportproject.org||2329.8 - 2880.0||2579.7|
|https://api.steemitdev.com||726.8 - 874.2||785.2|
|https://api.steemit.com||584.3 - 857.4||779.4|
|https://anyx.io||462.2 - 501.7||486.5|
|https://steemd.privex.io||85.4 - 91.3||87.6|
|https://appbasetest.timcliff.com||87.5 - 87.5||87.5|
Receiving a vote, a comment, and an account
In this test, the mean duration to receive an account, a comment, and a vote is measured.
List of working nodes - api calls
This table includes all nodes which were able to answer all three api calls within 30 seconds.The achieved minimum, maximum and mean time durations are shown. When a node failes, its mean value is increased as it is counted as 30 seconds
|node||time [s]||mean time [s]|
|https://steemd.minnowsupportproject.org||0.06 - 0.24||0.105|
|https://rpc.steemviz.com||0.18 - 0.20||0.187|
|https://anyx.io||0.41 - 0.89||0.593|
|https://appbasetest.timcliff.com||3.67 - 3.86||3.688|
|https://steemd.privex.io||3.67 - 3.95||3.760|
Summary of working nodes
A node is working, when it could fullfil at least once in the last 24h the following conditions:
- returned data within 30 seconds,
- blocks could be streamed,
- account history was possible,
- votes, a comment, an account could successfully be fetched and were not empty.
The nodes in the following table are ranked by the mean rank of all three node tables shown above.
This table includes only nodes which were passing all three tests sucessfully.
The shown ranks are:
block rank -
block_diff rank -
history rank -
|https://steemd.minnowsupportproject.org||1 - 5 - 1 - 3||82.9|
|https://rpc.steemviz.com||2 - 2 - 2 - 4||80.0|
|https://api.steemitdev.com||3 - 1 - 4 - 1||74.3|
|https://api.steemit.com||4 - 3 - 5 - 2||62.9|
|https://anyx.io||5 - 6 - 3 - 5||51.4|
|https://appbasetest.timcliff.com||6 - 4 - 6 - 6||34.3|
|https://steemd.privex.io||7 - 7 - 7 - 7||14.3|
Set fully working nodes with beempy / steempy
beempy set nodes "['https://steemd.minnowsupportproject.org', 'https://rpc.steemviz.com', 'https://api.steemit.com', 'https://anyx.io', 'https://appbasetest.timcliff.com', 'https://steemd.privex.io']"
steempy set nodes https://steemd.minnowsupportproject.org,https://rpc.steemviz.com,https://api.steemit.com,https://anyx.io,https://appbasetest.timcliff.com,https://steemd.privex.io
Receive fully working nodes from
json_metadata of the @fullnodeupdate account
The nodes are also stored in the
json_metadata variable of the @fullnodeupdate account.
The nodes inside the account metadata are updated every hour.
The json_metadata includes the following data:
nodes- list of nodes that passed all tests.
failing_nodes- list of nodes that did not answer the
report- test results.
beemand test parameter.
Example code for python:
from beem.account import Account import json acc = Account("fullnodeupdate") nodes = json.loads(acc["json_metadata"])["nodes"] acc.steem.set_default_nodes(nodes)
If you like what I'm doing, please consider @holger80 as one of your witnesses. You can use steemconnect.com for approve your vote or go to https://steemit.com/~witnesses and enter my name into the vote field:
This post was created with beem, my python library for steem.