Full API Node Update - 18/5/2020

in #full-nodes • 5 years ago

image.png

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.

nodehours with failurepercentage
https://api.openhive.network1/244.2 %
https://steemd.minnowsupportproject.org24/24100.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

nodemean time [s]versionHIVE
https://api.justyy.com0.080.22.8888False
https://anyx.io0.320.23.0True
http://anyx.io0.420.23.0True
https://api.steemit.com0.650.22.1False
https://api.hive.blog0.660.23.0True
https://api.openhive.network0.900.23.0True
https://rpc.ausbit.dev1.010.23.0True
https://rpc.esteem.app1.200.23.0True
https://api.hivekings.com1.300.23.0True
https://techcoderx.com1.620.23.0True
https://api.pharesim.me1.670.23.0True
https://hived.privex.io1.850.23.0True
https://steem.bts.tw3.200.22.5False
https://steem.61bts.com6.300.22.5False

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

nodeblock/smean block/s
https://api.justyy.com31.6 - 48.643.5
https://api.pharesim.me20.9 - 33.127.4
https://rpc.ausbit.dev14.3 - 17.115.7
https://api.openhive.network11.3 - 11.611.4
https://hived.privex.io4.4 - 12.211.1
https://api.steemit.com6.9 - 8.07.7
https://rpc.esteem.app4.0 - 7.87.4
https://api.hive.blog5.6 - 8.27.1
https://api.hivekings.com5.4 - 6.25.9
https://anyx.io3.3 - 5.64.6
http://anyx.io3.0 - 6.04.6
https://techcoderx.com4.1 - 4.54.3
https://steem.bts.tw0.1 - 2.92.0
https://steem.61bts.com0.1 - 0.80.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.

nodeblock delaymean delay
https://api.hivekings.com50.40 - 77.3057.672
https://rpc.ausbit.dev46.63 - 79.6560.429
https://api.pharesim.me47.34 - 81.1860.713
https://api.justyy.com49.63 - 76.0260.877
https://api.hive.blog49.58 - 74.9261.005
https://api.openhive.network50.31 - 75.2963.141
https://api.steemit.com49.68 - 75.2763.780
https://hived.privex.io46.15 - 72.3765.645
https://steem.61bts.com50.07 - 81.4368.145
https://steem.bts.tw54.06 - 110.9271.970
https://anyx.io50.42 - 74.7274.575
https://techcoderx.com52.31 - 74.8195.489
http://anyx.io53.15 - 70.8896.253
https://rpc.esteem.app58.62 - 77.19110.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

nodehist/smean hist/s
https://api.pharesim.me584.7 - 2228.81937.5
https://rpc.ausbit.dev1211.0 - 1416.11296.5
https://hived.privex.io376.6 - 1011.4931.7
https://api.steemit.com598.5 - 791.4751.3
https://api.justyy.com509.0 - 721.5653.7
https://api.hive.blog309.2 - 729.6632.9
https://api.openhive.network559.3 - 719.1622.2
https://anyx.io464.0 - 522.5502.2
http://anyx.io481.7 - 516.8499.5
https://rpc.esteem.app439.2 - 493.1468.0
https://api.hivekings.com354.8 - 400.1386.2
https://techcoderx.com301.5 - 326.7316.6
https://steem.61bts.com4.7 - 63.432.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

nodetime [s]mean time [s]
https://api.justyy.com0.09 - 0.240.128
https://api.steemit.com0.18 - 0.350.224
https://api.pharesim.me0.04 - 0.053.788
https://rpc.esteem.app0.04 - 0.163.839
https://rpc.ausbit.dev0.09 - 0.133.839
https://hived.privex.io0.11 - 0.513.883
https://api.hive.blog0.17 - 0.583.947
http://anyx.io0.20 - 1.254.006
https://steem.61bts.com1.26 - 10.214.044
https://anyx.io0.26 - 0.604.057
https://api.hivekings.com0.31 - 1.364.077
https://techcoderx.com0.31 - 1.324.091
https://api.openhive.network0.18 - 1.494.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

noderanksscoreHIVE
https://api.justyy.com1 - 4 - 12 - 278.6False
https://rpc.ausbit.dev3 - 2 - 10 - 667.1True
https://api.pharesim.me2 - 3 - 9 - 465.7True
https://api.hive.blog8 - 5 - 4 - 864.3True
https://api.steemit.com6 - 7 - 11 - 362.9False
https://api.hivekings.com9 - 1 - 3 - 1258.6True
https://anyx.io10 - 11 - 1 - 1157.1True
https://api.openhive.network4 - 6 - 5 - 1457.1True
http://anyx.io11 - 13 - 2 - 952.9True
https://hived.privex.io5 - 8 - 8 - 750.0True
https://rpc.esteem.app7 - 14 - 7 - 548.6True
https://steem.bts.tw13 - 10 - 14 - 134.3False
https://techcoderx.com12 - 12 - 6 - 1331.4True
https://steem.61bts.com14 - 9 - 13 - 1021.4False

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

#steem #steemdev #steemit #dev
5 years ago in #full-nodes by
$0.69
  • Past Payouts $0.69, 0.00 TRX
  • - Author $0.35, 0.00 TRX
  • - Curators $0.35, 0.00 TRX
17 votes
Reply 0