Full API Node Update - 18/5/2020

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

2020-05-17T20:00:53 - 2020-05-18T20:00:41 (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://steemd.minnowsupportproject.org	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://api.justyy.com	0.08	0.22.8888	False
https://anyx.io	0.32	0.23.0	True
http://anyx.io	0.42	0.23.0	True
https://api.steemit.com	0.65	0.22.1	False
https://api.hive.blog	0.66	0.23.0	True
https://api.openhive.network	0.90	0.23.0	True
https://rpc.ausbit.dev	1.01	0.23.0	True
https://rpc.esteem.app	1.20	0.23.0	True
https://api.hivekings.com	1.30	0.23.0	True
https://techcoderx.com	1.62	0.23.0	True
https://api.pharesim.me	1.67	0.23.0	True
https://hived.privex.io	1.85	0.23.0	True
https://steem.bts.tw	3.20	0.22.5	False
https://steem.61bts.com	6.30	0.22.5	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.justyy.com	31.6 - 48.6	43.5
https://api.pharesim.me	20.9 - 33.1	27.4
https://rpc.ausbit.dev	14.3 - 17.1	15.7
https://api.openhive.network	11.3 - 11.6	11.4
https://hived.privex.io	4.4 - 12.2	11.1
https://api.steemit.com	6.9 - 8.0	7.7
https://rpc.esteem.app	4.0 - 7.8	7.4
https://api.hive.blog	5.6 - 8.2	7.1
https://api.hivekings.com	5.4 - 6.2	5.9
https://anyx.io	3.3 - 5.6	4.6
http://anyx.io	3.0 - 6.0	4.6
https://techcoderx.com	4.1 - 4.5	4.3
https://steem.bts.tw	0.1 - 2.9	2.0
https://steem.61bts.com	0.1 - 0.8	0.5

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	50.40 - 77.30	57.672
https://rpc.ausbit.dev	46.63 - 79.65	60.429
https://api.pharesim.me	47.34 - 81.18	60.713
https://api.justyy.com	49.63 - 76.02	60.877
https://api.hive.blog	49.58 - 74.92	61.005
https://api.openhive.network	50.31 - 75.29	63.141
https://api.steemit.com	49.68 - 75.27	63.780
https://hived.privex.io	46.15 - 72.37	65.645
https://steem.61bts.com	50.07 - 81.43	68.145
https://steem.bts.tw	54.06 - 110.92	71.970
https://anyx.io	50.42 - 74.72	74.575
https://techcoderx.com	52.31 - 74.81	95.489
http://anyx.io	53.15 - 70.88	96.253
https://rpc.esteem.app	58.62 - 77.19	110.919

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	584.7 - 2228.8	1937.5
https://rpc.ausbit.dev	1211.0 - 1416.1	1296.5
https://hived.privex.io	376.6 - 1011.4	931.7
https://api.steemit.com	598.5 - 791.4	751.3
https://api.justyy.com	509.0 - 721.5	653.7
https://api.hive.blog	309.2 - 729.6	632.9
https://api.openhive.network	559.3 - 719.1	622.2
https://anyx.io	464.0 - 522.5	502.2
http://anyx.io	481.7 - 516.8	499.5
https://rpc.esteem.app	439.2 - 493.1	468.0
https://api.hivekings.com	354.8 - 400.1	386.2
https://techcoderx.com	301.5 - 326.7	316.6
https://steem.61bts.com	4.7 - 63.4	32.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.justyy.com	0.09 - 0.24	0.128
https://api.steemit.com	0.18 - 0.35	0.224
https://api.pharesim.me	0.04 - 0.05	3.788
https://rpc.esteem.app	0.04 - 0.16	3.839
https://rpc.ausbit.dev	0.09 - 0.13	3.839
https://hived.privex.io	0.11 - 0.51	3.883
https://api.hive.blog	0.17 - 0.58	3.947
http://anyx.io	0.20 - 1.25	4.006
https://steem.61bts.com	1.26 - 10.21	4.044
https://anyx.io	0.26 - 0.60	4.057
https://api.hivekings.com	0.31 - 1.36	4.077
https://techcoderx.com	0.31 - 1.32	4.091
https://api.openhive.network	0.18 - 1.49	4.166

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.justyy.com	1 - 4 - 12 - 2	78.6	False
https://rpc.ausbit.dev	3 - 2 - 10 - 6	67.1	True
https://api.pharesim.me	2 - 3 - 9 - 4	65.7	True
https://api.hive.blog	8 - 5 - 4 - 8	64.3	True
https://api.steemit.com	6 - 7 - 11 - 3	62.9	False
https://api.hivekings.com	9 - 1 - 3 - 12	58.6	True
https://anyx.io	10 - 11 - 1 - 11	57.1	True
https://api.openhive.network	4 - 6 - 5 - 14	57.1	True
http://anyx.io	11 - 13 - 2 - 9	52.9	True
https://hived.privex.io	5 - 8 - 8 - 7	50.0	True
https://rpc.esteem.app	7 - 14 - 7 - 5	48.6	True
https://steem.bts.tw	13 - 10 - 14 - 1	34.3	False
https://techcoderx.com	12 - 12 - 6 - 13	31.4	True
https://steem.61bts.com	14 - 9 - 13 - 10	21.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.justyy.com', 'https://api.steemit.com', 'https://steem.bts.tw', 'https://steem.61bts.com']"

steempy

steempy set nodes https://api.justyy.com,https://api.steemit.com,https://steem.bts.tw,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