Full API Node Update - 29/5/2020

Full API node update - (29/5/2020)

2020-05-28T21:00:11 - 2020-05-29T20:00:07 (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
https://api.openhive.network	1/24	4.2 %
https://api.justyy.com	1/24	4.2 %
https://steemd.minnowsupportproject.org	24/24	100.0 %
https://steem.bts.tw	24/24	100.0 %

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	HIVE
https://anyx.io	0.32	0.23.0	True
http://anyx.io	0.42	0.23.0	True
https://api.steemit.com	0.64	0.23.0	False
https://api.hive.blog	0.73	0.23.0	True
https://api.pharesim.me	0.76	0.23.0	True
https://api.justyy.com	1.08	0.23.0	False
https://hived.privex.io	2.36	0.23.0	True
https://api.openhive.network	2.87	0.23.0	True
https://rpc.esteem.app	2.92	0.23.0	True
https://techcoderx.com	3.05	0.23.0	True
https://rpc.ausbit.dev	3.41	0.23.0	True
https://api.hivekings.com	4.91	0.23.0	True
https://steem.61bts.com	6.26	0.23.1	False

Streaming blocks

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

node	block/s	mean block/s
https://api.pharesim.me	14.0 - 33.4	28.8
https://rpc.ausbit.dev	14.3 - 17.0	16.0
https://hived.privex.io	11.2 - 12.6	12.0
https://api.openhive.network	11.3 - 11.6	11.4
https://api.steemit.com	5.8 - 8.7	8.2
https://rpc.esteem.app	0.4 - 7.8	7.2
https://api.justyy.com	5.1 - 8.0	6.8
https://api.hive.blog	5.2 - 8.0	6.7
https://api.hivekings.com	3.0 - 6.2	5.9
https://techcoderx.com	3.0 - 4.5	4.3
https://anyx.io	2.4 - 5.8	4.2
http://anyx.io	2.5 - 5.8	4.2
https://steem.61bts.com	0.1 - 3.1	1.2

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.hivekings.com	47.50 - 77.33	59.640
https://api.openhive.network	47.57 - 75.04	60.229
https://api.steemit.com	49.41 - 75.34	60.578
https://api.hive.blog	50.91 - 80.82	60.893
https://api.justyy.com	50.56 - 77.69	61.588
https://api.pharesim.me	48.14 - 77.49	61.975
https://rpc.ausbit.dev	48.54 - 79.61	62.049
https://steem.61bts.com	53.98 - 79.86	62.872
https://hived.privex.io	46.21 - 72.37	63.180
https://anyx.io	52.04 - 78.96	78.368
https://techcoderx.com	50.23 - 77.01	84.525
http://anyx.io	53.28 - 80.96	99.101
https://rpc.esteem.app	51.40 - 72.97	102.693

Account history

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

node	hist/s	mean hist/s
https://api.pharesim.me	1791.9 - 2388.8	2066.9
https://rpc.ausbit.dev	1157.4 - 1359.2	1267.8
https://hived.privex.io	932.9 - 1054.4	987.3
https://api.steemit.com	358.9 - 800.8	740.8
https://api.justyy.com	434.0 - 738.3	672.7
https://api.hive.blog	562.3 - 736.8	655.6
https://api.openhive.network	542.9 - 731.6	629.7
http://anyx.io	478.1 - 517.5	500.5
https://anyx.io	460.1 - 524.2	499.4
https://rpc.esteem.app	458.6 - 486.4	475.0
https://api.hivekings.com	286.7 - 401.4	385.2
https://techcoderx.com	312.8 - 333.4	323.6
https://steem.61bts.com	10.1 - 104.4	44.6

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://api.pharesim.me	0.04 - 0.39	0.059
https://rpc.esteem.app	0.05 - 0.17	0.100
https://rpc.ausbit.dev	0.08 - 0.14	0.101
https://hived.privex.io	0.11 - 0.17	0.134
https://api.steemit.com	0.17 - 0.20	0.183
http://anyx.io	0.20 - 0.42	0.229
https://api.openhive.network	0.19 - 0.39	0.233
https://api.justyy.com	0.15 - 1.11	0.267
https://api.hive.blog	0.20 - 2.18	0.298
https://api.hivekings.com	0.31 - 0.33	0.317
https://techcoderx.com	0.30 - 0.34	0.317
https://anyx.io	0.25 - 0.65	0.335
https://steem.61bts.com	1.47 - 4.43	13.917

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 - apicall rank

node	ranks	score	HIVE
https://api.openhive.network	4 - 2 - 1 - 7	73.8	True
https://api.pharesim.me	1 - 6 - 9 - 1	73.8	True
https://api.steemit.com	5 - 3 - 11 - 5	66.2	False
https://api.hive.blog	8 - 4 - 5 - 9	61.5	True
https://hived.privex.io	3 - 9 - 8 - 4	60.0	True
https://rpc.ausbit.dev	2 - 7 - 10 - 3	56.9	True
http://anyx.io	12 - 12 - 3 - 6	53.8	True
https://anyx.io	11 - 10 - 2 - 12	52.3	True
https://api.hivekings.com	9 - 1 - 4 - 10	52.3	True
https://rpc.esteem.app	6 - 13 - 7 - 2	50.8	True
https://api.justyy.com	7 - 5 - 12 - 8	49.2	False
https://techcoderx.com	10 - 11 - 6 - 11	33.8	True
https://steem.61bts.com	13 - 8 - 13 - 13	15.4	False

Set fully working nodes with beempy / steempy

https://api.steemitstage.com, https://api.steemitdev.com and nodes with not working results were excluded.

beempy

beempy set nodes "['https://api.steemit.com', 'https://api.justyy.com', 'https://steem.61bts.com']"

steempy

steempy set nodes https://api.steemit.com,https://api.justyy.com,https://steem.61bts.com

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 get_config call.
• report - test results.
• parameter - used beem and 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)

---

This post was created with beem, my python library for steem.

---

image source